Hi Mike,
I'm sorry, the problem all the time is inside related to a
word-delimiter filter factory. This is embarrassing but I have to
admit publicly and self-flagellate.
A word-delimiter filter is used to split tokens, these then are used
to find multi-token synonyms (hence the connection). In
It _finally_ occurred to me to ask why we have the restriction that the
destination of a copyField must have stored=false. I understand what currently
happens when that’s the case, you get repeats.
What I wondered is why we can’t detect that a field is the destination of a
copyField and _not_
Thank you Cassandra,
I quickly looked into config. Sems easy all together. I can possibly also set
this up for Javadocs.
The good thing with Javadocs is that we can better configure linking between
Solr and Lucene, so this is a good thing.
I will try to set something up, if I have some time.
Follow-up on this - we fixed the Solr Ref Guide builds last week, but there was
an outstanding issue which was the Content Security Policy on Cloudbees is too
stringent to display the Ref Guide’s CSS and JS. It blocked all the content
basically, rendering them unreadable.
Infra helped us
Hello fellow committers,
I'd like to organize another virtual Lucene/Solr committer meeting this
month. I created a meeting notes page in confluence here:
https://cwiki.apache.org/confluence/display/LUCENE/2020-08+Committer+meeting
It has some topics I'd like to talk about, some copied from last
