elastic/elasticsearch

Consider deprecating/ removing support for string-style queries on certain metadata fields.

Open

#34,160 opened on Sep 28, 2018

View on GitHub
 (2 comments) (1 reaction) (0 assignees)Java (25,882 forks)batch import
:Search Foundations/Mapping>deprecationTeam:Search Foundationshelp wanted

Repository metrics

Stars
 (76,700 stars)
PR merge metrics
 (Avg merge 2d) (1,000 merged PRs in 30d)

Description

In addition to term-based queries, we currently support prefix, regex, and wildcard queries on certain metadata fields like _ignored and _routing. It’s not clear that supporting these additional query types is useful, and it limits how we’re able to store these fields. As an example, _id fields do not support these queries, and we’re able to encode them using a flexible scheme.

Unless they're actively used, we should consider deprecating + eventually removing support for these query types.

Relates to #34089, where the discussion first arose.

Contributor guide

Research direction
Investigate usage of prefix, regex, and wildcard queries on ignored and routing fields, analyze impact on users, and propose deprecation path. See related issue #34089.
Tech stack
java
Domain
backend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
ElasticsearchJava
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60