Hey everyone,
Aside from simply disabling coord for an entire query, I was wondering if
there was a good way to disable coord for a BooleanClause within a query
such that the max coord value, and the overlap value, simply ignore that
clause?
For example, I have the following query:
(apple OR
Hey everyone,
Tokenization seems inherently fuzzy and imprecise, yet Lucene does not
appear to provide an easy mechanism to account for this fuzziness.
Let's take an example, where the document I'm indexing is v1.1.0 mr. jones
da...@gmail.com
I may want to tokenize this as follows: [v1.1.0,
Hey everyone,
I have a question about Lucene/Solr scoring in general. It really feels like
a wobbly house of cards that falls down whenever I make the slightest tweak.
There are many factors at play in Lucene scoring: they're all fighting with
each other, and very often one will completely
[
https://issues.apache.org/jira/browse/LUCENE-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607415#action_12607415
]
Tavi Nathanson commented on LUCENE-794:
---
Hi,
I'm new to Lucene and the highlighter
[
https://issues.apache.org/jira/browse/LUCENE-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12611453#action_12611453
]
Tavi Nathanson commented on LUCENE-794:
---
Hey everyone,
I'm having some trouble