Solr 7(.5.5) -> Solr 8(.8.2) , different non-emptyness query behavior?

I have a unit test that tests the "non-emptyness query". As of updating from 7.5.5 to 8.8.2 this very test fails and returns a document that has an empty string ( i.e. "" ) The "non-emptyness query" is: fieldName:[* TO *] Has the default "behavior" of the above query changed? Does it possibly h

Unique function not working for Solr (Ver: 6.0.1) nested facets

Hello, In our collection there are some documents which have same value for different fields while other have different values. i.e. For document1: status="xyz" and poi="draft", For document2: status="xyz" and poi="draft", For document3: status="abc" and poi="information". We have created facet

Re: Unique function not working for Solr (Ver: 6.0.1) nested facets

I think your facet request syntax is wrong (you have duplicate "facet" keys for all but the "leaf" (poi) facet, which is why you see the "leaf"/poi facet working, but not the others). I wonder whether this should throw a 400 error? In any case could you see whether the following works as expected?:

Re: Solr 7(.5.5) -> Solr 8(.8.2) , different non-emptyness query behavior?

So the backend implementation of the fieldName:[* TO *] query has changed as of 8.5 (SOLR-11746 ). However I'm not sure that is resulting in the change here. Are you using the RemoveBlankFieldUpdateProcessorFactory? - Houston On Mon, May 24, 2021

Re: Solr 7(.5.5) -> Solr 8(.8.2) , different non-emptyness query behavior?

Not explicitly, this being the requestHandler-section : On 2021/05/24 16:15:22, Houston Putman wrote: > So the backend implementation of the fieldName:[* TO *] query has changed> > as of 8.5 (SOLR-11746 ).> > However I'm not sure that is result

Re: Solr 7(.5.5) -> Solr 8(.8.2) , different non-emptyness query behavior?

So I have tested out the logic of stringField:[* TO *], with empty strings in 7.5 and 8.8. They perform identically, returning empty string values, if they exist in the index If I use the update processor chain with the "RemoveBlank" processor, the documents with empty string values don't match. If

Re: Solr 7(.5.5) -> Solr 8(.8.2) , different non-emptyness query behavior?

: So I have tested out the logic of stringField:[* TO *], with empty strings : in 7.5 and 8.8. They perform identically, returning empty string values, if : they exist in the index I remember seeing something like this pop up before ... not sure where ... but i bet Houston's comment above is ba

Re: Date string field not recognized...

Thanks for your answer. It looks like quite complicated to add a custom UpdateRequestProcessor into sample_techproducts_configs type core. Are there tools to help to do this ? Lot of dates  are said invalid by solr but i don't see why. Most of docs are .ods / .odt : msg=Invalid Date String

Re: Date string field not recognized...

I think it is because 'Z' is missing: i thought it was an option, but finaly is mandatory.  So how to tell solr to accept date without 'Z'? Le 24/05/2021 à 22:59, Gaétan QUENTIN@Work a écrit : Thanks for your answer. It looks like quite complicated to add a custom UpdateRequestProcessor into

Re: Date string field not recognized...

You could write an update request processor script to add a ‘Z’ to the end of that field. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On May 24, 2021, at 2:15 PM, Gaétan QUENTIN@Work > wrote: > > I think it is because 'Z' is missing: i thought it

Re: Solr 7(.5.5) -> Solr 8(.8.2) , different non-emptyness query behavior?

> if there is a default updateRequestProcessorChain I'd say no. The update-handler entry looks alike: and there ist no updateRequestProcessorChain > clemensdev is talking about a query against a TextField my test indeed makes use of a TextField On 2021/05/24 19:40:26, Chris Hostetter wrote: