Locale support in Elasticsearch
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Parent Issue
Multi-Lingual Epic
Task
We have tried to minimize our use of language ids and instead use the local code. In order to support this in dotCMS, we should add a new ES mapping for locale that is a keyword array that we put both the locale code AND the numeric language id in as an array. This would
- not blow up any existing code using the
+languageId: - allow queries to work in both cases like this:
+contentType:banner +locale:es-cr
or
+contentType:banner +locale:2
We should then do a pass in our documentation/example queries to support this.
Proposed Objective
Core Features
Proposed Priority
Priority 2 - Important
Acceptance Criteria
No response
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the Elasticsearch mapping and indexing code, then find the query handling for languageId and the documentation or example queries. Verify that locale supports both the locale code and numeric language ID while existing +languageId: queries continue to work, and update the documented query examples.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, java
- Domain
- search
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100