Thinking of these roles as labels, I think sysProps and envVars are the two
universal methods, and nothing wrong with that.
I keep trying to think cloud native and container, so having excellent 1st
class support for env.vars for such configs is a priority to me.
Most tools, CI-environments etc
Agree better to something other than sysprops. an arg in the start script
would be friendlier than -D props which generally are irritatingly verbose
and expose too much implementation.
We lack a config file per level. solr.xml does double duty as global and
per-node depending on how it's used (zk
OK, can you let me know when it's merged?
On Fri, Nov 5, 2021 at 2:23 PM Mike Drob wrote:
> After additional discussion on
> https://issues.apache.org/jira/browse/SOLR-15762 I think there is a small
> patch that would be nice to include for 8.11 if there is still time. Thanks
>
> On Fri, Nov 5,
Once I get the core-container split out into it's own
provider/service/whatever started by a context listener, we should do v3 as
a servlet giving us a clean slate, and easy access to verbs. I suspect v2
was made much more difficult by the fact that it had to co-exist with a lot
of other code insid
After additional discussion on
https://issues.apache.org/jira/browse/SOLR-15762 I think there is a small
patch that would be nice to include for 8.11 if there is still time. Thanks
On Fri, Nov 5, 2021 at 5:05 AM Adrien Grand wrote:
> All blockers are now addressed, I'll proceed with building a r
All blockers are now addressed, I'll proceed with building a release
candidate.
On Thu, Nov 4, 2021 at 6:51 PM Adrien Grand wrote:
> Thanks Jan!
>
> On Thu, Nov 4, 2021 at 2:32 PM Jan Høydahl wrote:
>
>> I added a PR https://github.com/apache/lucene-solr/pull/2603 for
>> SOLR-14438, that I had
+1 to experimental
If we want to be more standards-based, embrace OpenAPI and perhaps more
standardized RBAC frameworks, then I believe there will be a v3 API based on
JAX-RS or something, with more active use of http verbs.
While v2 is harder for devs to use and remember, it has somewhat better
I can live with “experimental” ;-)
> On Nov 4, 2021, at 6:42 PM, Shawn Heisey wrote:
>
> On 11/4/21 1:20 PM, Jason Gerlowski wrote:
>> With that in mind, I think the next steps here should probably be to:
>>
>> 1. decide what label or term we want to go with ("evolving"?
>> "experimental"? "bet