Hi Hoss
I feel so stupid right now, thank you so much!
Of course this makes much more sense. Why should we want to have different
Timezones for different facets. Hopefully I don't come across as being
sarcastic, I really think that it makes more sense that it's a global modifier.
After reading t
Hi all,
just a reminder that the first Community Over Code European conference is
approaching!
There will be various Search-related talks on both Apache Lucene and Solr,
probably also a Birds of a Feather session (that we found extremely useful
in the most recent community over code and ApacheCon)
Hi Vishal,
When searching Chinese, you have to use a proper parser to parse the Chinese
characters to be space seperated, for example in the case you mentioned:
Original query text: (第二期)
Parsed query text: ( 第 二 期 )
In English for better understood:
Original query text: (TheSecondTerm)
Parsed
: I feel so stupid right now, thank you so much! Of course this makes much
: more sense. Why should we want to have different Timezones for different
: facets. Hopefully I don't come across as being sarcastic, I really think
: that it makes more sense that it's a global modifier.
It's not jus
This codec format was completley removed from Lucene in 9.0...
https://issues.apache.org/jira/browse/LUCENE-8917
...I'm not enough of a codec expert to be able to explain why, but it's no
longer an option in Solr at all.
-Hoss
http://www.lucidworks.com/
Hello Hoss,
Thank you very much for having taken time to answer, at least it
explains why docValuesFormat="Direct" is not usable with lucene9 with
Solr 9.x.
Would this option be usable with Solr 9.6.0 if I re-create my
collections with 8.11.3 ?
My goal is to check if the performance issues (most
