Search 6 groundwork - Completely forbid sortable analyzed fields
Description
depends on
duplicates
Activity
Show:
Yoann Rodière October 16, 2018 at 2:51 PM
Closing as duplicate of HSEARCH-3115, which fixed this issue.
Relevant test: org.hibernate.search.integrationtest.backend.tck.DocumentModelDslIT#analyzerOnSortableField
Duplicate
Details
Details
Assignee
Yoann Rodière
Yoann RodièreReporter
Yoann Rodière
Yoann RodièrePriority
MajorCreated April 11, 2018 at 6:25 AM
Updated October 16, 2018 at 2:52 PM
Resolved October 16, 2018 at 2:51 PM
We currently allow analyzed fields to be marked as sortable, essentially because analyzed fields were easier to test than normalized fields in ES (there is a default analyzer, but there isn’t any default normalizer on ES).
Once we have implemented normalizer definitions, we should rework our tests, and then we should consistently throw an exception when trying to define analyzed sortable fields, and tell the user to use normalizers instead.
See
org.hibernate.search.v6poc.backend.lucene.document.model.impl.IndexSchemaFieldStringContext#contributein particular.