Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Remove legacy-geo module #96097

Open
iverase opened this issue May 15, 2023 · 1 comment
Open

Remove legacy-geo module #96097

iverase opened this issue May 15, 2023 · 1 comment
Labels
:Analytics/Geo Indexing, search aggregations of geo points and shapes >deprecation Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo)

Comments

@iverase
Copy link
Contributor

iverase commented May 15, 2023

In Elasticsearch 6.6.0, we introduced a new indexing strategy of geo_shape field mapper based on Lucene's bkd tree: #35320

From Elasticsearch 8.0.0, we don't allow to create new geo_shape mapping using the legacy indexing strategy using prefix trees: #70850

This legacy indexing strategy lives in the legacy-geo module/. This issue is to track the removal of the module because at the moment it is there only to support old indices. At some point those indices might be too old so the module can be removed.
@iverase iverase added :Analytics/Geo Indexing, search aggregations of geo points and shapes >deprecation labels May 15, 2023
@iverase iverase mentioned this issue May 15, 2023
Closed
3 tasks
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-analytics-geo (Team:Analytics)

@elasticsearchmachine elasticsearchmachine added the Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) label May 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
:Analytics/Geo Indexing, search aggregations of geo points and shapes >deprecation Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@iverase @elasticsearchmachine