Skip to content

Conversation

@haarg
Copy link
Member

@haarg haarg commented May 2, 2025

Elasticsearch 5 and newer has separate types for text and keywords rather than using the string type. Update our mappings to use these types, and add a compatibility shim to return the older style mappings when running 2.x.

@haarg haarg force-pushed the haarg/es7-compat branch 4 times, most recently from 0f800c8 to 89401e9 Compare May 2, 2025 20:45
@haarg haarg marked this pull request as draft May 2, 2025 21:31
oalders
oalders previously approved these changes May 2, 2025
haarg added 11 commits May 3, 2025 16:00
The mapping script had options for doing a bunch of operations on
Elasticsearch, such doing arbitrary creations or patches. This code
often made a bunch of assumptions about how types worked.

These types of operations are better done manually against the
Elasticsearch APIs.
Elasticsearch 5 and newer has separate types for text and keywords
rather than using the string type. Update our mappings to use these
types, and add a compatibility shim to return the older style mappings
when running 2.x.
@haarg haarg force-pushed the haarg/es7-compat branch from 6078443 to e783c2b Compare May 3, 2025 14:00
@haarg haarg marked this pull request as ready for review May 3, 2025 15:20
@haarg haarg requested a review from oalders May 3, 2025 15:20
@haarg haarg merged commit 0200d61 into master May 3, 2025
1 check passed
@haarg haarg deleted the haarg/es7-compat branch May 3, 2025 15:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants