> My proposal is that ALL roles are always ALLOW if not specified
explicitly.
As explained several times before, this is a problem for new roles
introduced in future. Those roles will get turned on on all nodes after an
upgrade, whether a user wants or not. A user explicitly mentions which
roles h
agreed! thanks for stepping up to be the RM Jan ;-)
On Tue, Dec 7, 2021 at 6:05 PM Jan Høydahl wrote:
>
> Hi,
>
> Solr has 13 bug fixes lined up in branch_8_11 already. Lucene has no changes.
> Now that Lucene 9.0 is out the door (congrats!), let's do the 8.11.1 release.
>
> I volunteer as RM and
Hi,
Solr has 13 bug fixes lined up in branch_8_11 already. Lucene has no changes.
Now that Lucene 9.0 is out the door (congrats!), let's do the 8.11.1 release.
I volunteer as RM and propose a first RC on Monday 13th. That should allow some
time to merge any last bug fixes both for Lucene and Sol
There is no complexity here. You just think something is complex because
you haven't spent any time to understand this. A role is a tag for a node.
Period.
How complex is that?
We just added standard mechanism to declare and discover the nodes. There
is no extra cost or complexity
On Wed, De
>
> Another user with a 100 node cluster who today have three overseer nodes that
> they have shielded from having data by specifying createNodeSet manually or
> by other means, can choose to adopt rhe role system, and define tree
> dedicated nodes with the overseer role but without the data ro
Two cents from the peanut gallery:
I’ve looked at this before. My opinion:
Our stuff was a just terrible, take your pick on the api version. Reasons
are numerous.
Custom end points is an anti feature. Even worse for cloud.
JAX-RS looked ridiculously sensible.
--
- MRM
some thoughts inline...
On Mon, Dec 6, 2021 at 2:04 PM Noble Paul wrote:
> I'm +1 for modernization
> I just wanted to highlight the hurdles we need to overcome to reach there
>
> SolrRequestHandler is the current framework that serves all requests in
> Solr. This also has associated ways to
>
>