Handle the 'string' datatype in ES5 schema validation/migration

Description

In https://hibernate.atlassian.net/browse/HSEARCH-2434#icft=HSEARCH-2434 we made sure that schema generation will work fine with an ES5 cluster, meaning we'll use the text/keyword datatypes instead of string.
But the string is actually still allowed in some conditions (namely, indices migrated from ES2), so our schema validation and migration tools should take this into account and handle the string datatype correctly (whatever that means).

Activity

Show:

Yoann RodièreApril 3, 2017 at 4:54 PM

Users can reindex their data when moving from ES2 to ES5. We have more pressing matters, so we won't fix this.

Yoann RodièreApril 3, 2017 at 3:34 PM

TODO: change the documentation, then close this as "Won't Fix"

Won't Fix

Details

Assignee

Reporter

Priority

Created February 27, 2017 at 10:06 AM
Updated April 3, 2017 at 4:55 PM
Resolved April 3, 2017 at 4:54 PM

Flag notifications