Re: [hibernate-dev] [Hibernate Search] DocValues and Sorting API -> new mapping annotations ?
On 7 August 2015 at 13:31, Gustavo Fernandes <gustavo(a)infinispan.org> wrote:
On Fri, Aug 7, 2015 at 1:14 PM, Sanne Grinovero
<sanne(a)hibernate.org> wrote:
>
> A quick update on some more exploration on this:
> it turns out sorting on a NumericField when this field is also using
> an "indexNullAs" token gets the UninvertingReader approach to throw an
> exception.
> My two conclusions:
> - we need to move away from supporting those tokens in NumericField,
> especially as stricter schema is coming in next gen Lucene
> - yet another reason to clearly separate fields meant for searching vs
> sorting
One possible workaround is to enforce the indexNullAs value to match the
underlying field type, at the
moment it is always a string.
Interesting idea, but the user would need to provide which "value"
he's ok to give up, as he would need to pick a number to be treated as
NaN.
Since the indexNullAs parameter requires a string, would we expect
people to write a number in there?
Another possibility is to model "null" as field not present
in the lucene
document, instead of a marker token.
Thanks! I've run some tests with this and have a patch working based
on this idea; I was sceptical initially because of scoring, but it
seems it's doable without needing to score all documents on this
negation. I'll send a PR soon; basically with this approach the
indexNullAs attribute will be ignored, but it's ok I think as this
solution is better and there's no drawback (nor needing any user
configuration).
Sanne