Hi,
I noticed that lucene has introduced a new two-phase iteration API since 5,
but could not get a good understanding of how it works. Are there any
detail documentation or examples? Does the two-phase iteration result in
better query performance? Appreciate your help.
Thanks,
Wei
Thanks, that pointed me in the right direction! The problem was an ancient ICU
library in the distributed code.
-Tod
On Dec 15, 2017, at 5:15 PM, Erick Erickson
mailto:erickerick...@gmail.com>> wrote:
My guess is this isn't a Solr issue at all; you are somehow using an old Java.
RBBIDataWrapp
About the docs. Recently we've changed the documents to be asciidoc format
One of the ways to contribute is to raise a JIRA and submit a
documentation patch.
See: https://wiki.apache.org/solr/HowToContribute
It's valuable to have people reading docs and trying to understand
them help update them
Thanks Emir,
It seems that stored="false" docValues="true" is the default in Solr's
github and the recommended way to go.
grep "docValues=\"true\""
./server/solr/configsets/_default/conf/managed-schema
Point fields don't support FieldCache, so they must have
docValues="
Your questions are already more or less answered:
> 1) If the docValues are that good, can we git rid of the stored values
> altogether?
You can if you want - just configure your field with stored=“false” and
docValues=“true”. Note that you can do that only if:
* field is not analyzed (you cannot
Very interesting discussion SG and Erick.
I wish these details were part of the official Solr documentation as well.
And yes, "columnar format" did not give any useful information to me either.
"A good explanation increases contributions to the project as more people
become empowered to improvise
Hello Walter, Steve,
That is not going to be that easy, we have many Germanic languages in the
index, all with support for splitting compound words.
I also do not like the idea of adding all inflections to the synonyms file, and
blows up our queries N fold, they are very big already due to sear
Am 22.12.2017 um 11:57 schrieb Selvam Raman:
> 1) how can i disable leading wildcard search
Do it on the client side. Just don't allow leading asterisks or question
marks in your query term.
> 2) why leading wildcard search takes so much of time to give the response.
>
Because Lucene can't just
Hi,
Solr version - 6.4
Parser - Edismax
Leading wildcard search is allowed in edismax.
1) how can i disable leading wildcard search
2) why leading wildcard search takes so much of time to give the response.
--
Selvam Raman
"லஞ்சம் தவிர்த்து நெஞ்சம் நிமிர்த்து"
