Waldemar Kłaczyński (
https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%...
) *commented* on HSEARCH-3839 (
https://hibernate.atlassian.net/browse/HSEARCH-3839?atlOrigin=eyJpIjoiNGI...
)
Re: Sorting by numeric value has an exception "(expected=NUMERIC). Use
UninvertingReader or index with docvalues" (
https://hibernate.atlassian.net/browse/HSEARCH-3839?atlOrigin=eyJpIjoiNGI...
)
Elasticsearch's has already solved this problem. It would be a shame not to use it.
Many changes are necessary, but many can be accelerated by adopting their solutions.
It's even better here because you can then ensure backward compatibility with
Elasticsearch.
It tests it and the solution works. I can choose how to choose the value. There is a min
and max search fix, Elasticsearch's was a bug in these functions when it comes to
Storage.FLATTENED, I corrected that these functions would work the same as for
Storage.NESTED. But the solution turns out to be effective and solves my problem.
This can be supplemented with the option of defining a comparator when using native
LuceneSearch sort predicates. Extend native instructions with the ability to download a
multi value comparator.
(
https://hibernate.atlassian.net/browse/HSEARCH-3839#add-comment?atlOrigin...
) Add Comment (
https://hibernate.atlassian.net/browse/HSEARCH-3839#add-comment?atlOrigin...
)
Get Jira notifications on your phone! Download the Jira Cloud app for Android (
https://play.google.com/store/apps/details?id=com.atlassian.android.jira....
) or iOS (
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=Em...
) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100121- sha1:cefda43 )