I can take another look at this. Changed the implementation for matching
glob patterns to avoid a third party dependency, but it seems like we may
just want to use the original implementation from Apache Commons to avoid
the performance degradation. Is the best practice here to do a PR with the
ori
Since the change was released, please create a new Jira. That way future
software archaeologists can track which version has the degradation and
which version has the fix.
On Mon, Feb 26, 2024 at 7:41 AM Justin Sweeney
wrote:
> I can take another look at this. Changed the implementation for matc
https://issues.apache.org/jira/projects/SOLR/issues/SOLR-17179
On 2024/02/26 13:40:06 Justin Sweeney wrote:
> I can take another look at this. Changed the implementation for matching
> glob patterns to avoid a third party dependency, but it seems like we may
> just want to use the original impleme
That makes sense, thank you.
On Fri, Feb 23, 2024 at 6:59 PM Chris Hostetter
wrote:
>
> The obvious answer that comes to mind is that your collection has 3 shards
> and you have one replica for each shard on the node where you see this
> listern triggering 3 times on collection reload. (or some
Hi Solr Users,
Could you please help me with an example query syntax that uses more than
one query parser in the same query?
I tried the following, edismax to search against the description field and
lucene parser to search against the keywords field, but it does not work.
What is wrong?
host
Floating this once again in case anyone has any thoughts.
Thanks,
Rahul
On Sun, Feb 25, 2024 at 11:51 PM Rahul Goswami
wrote:
> Hello,
> I am running Solr 8.11.1 and running into an issue with stream api. Looks
> like searches break when the data contains the backtick character( ` ).
> Eg:
>
>
Hi Rajani
This may help. I'm thinking you might want to do some query alias
substitution kind of thing? plus the first 'OR' might force your query into
lucene query parser mode overall?
I like Hoss' breakdown in this presentation for query substitution
syntax... :)
the Lucene/Solr Revolution 20
Hi,
IIRC eDismax allows some advanced q ops syntax. Also JSON query DSL may be
convenient for structuring queries.
With regards to old local params syntax, it struggles with defining the end
of substring to be processed, eg if we put space in the beginning of the
string, dismax takes only 'white'
