opensearch-project/OpenSearch

[Feature Request] Analyzers on non-text sub fields

Open

#11,882 opened on Jan 15, 2024

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Java (1,505 forks)batch import
Indexingenhancementhelp wanted

Repository metrics

Stars
 (8,123 stars)
PR merge metrics
 (Avg merge 5d 9h) (266 merged PRs in 30d)

Description

Is your feature request related to a problem? Please describe

In my domain, Every single type of document has an id that consists of two parts: id space and thei d itself, e.g. 31-111. When trying to sort by id, I'd actually want to sort by the last part, numerically. Currently I cannot create an analyzer for a sub field (ie.g. d.number) that would index the id part as a long because analyzers work on strings.

Describe the solution you'd like

When the main field is a string (text, keyword) and the sub field is another type, you should be able to set an analyzer to the sub field. Opensearch should try to cast the result to the type of the sub field.

Related component

Indexing

Describe alternatives you've considered

Store the number part in a separate field.

  • It's not part of the data so the result is awkward.
  • The purpose of sub fields is to avoid this exact thing.

Script sorting

  • Performance becomes an issue.

Additional context

No response

Contributor guide

Research direction
Investigate how OpenSearch handles sub field analysers in mapping parsing, and how to allow analyzers on non text sub fields by casting the analyzed result to the sub field type. Look at the IndexFieldMapper and related classes.
Tech stack
java
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 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
JavaOpenSearchLucene
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40