JanusGraph / JanusGraph/janusgraph
Document configuration for non-European languages for Index Backends
- Dominant language
- Java
- Stars
- 5.8k
- Forks
- 1.2k
- Avg merge
- 13h 53m
- Merged PRs (30d)
- 6
Description
We got some questions about problems with index backends when a non-European language is used, for example in our Gitter chat and in these issues:
- #940
- #922
- #1416
The answer is usually to configure [a custom analyzer](https://docs.janusgraph.org/0.3.1/field-mapping.html#_custom_analyzer) that supports their language. We could add the use case of a property with values for a non-European language to our docs to make this more clear.
Contributor guide
Research direction
Start with the custom analyzer section in the linked field-mapping documentation and review issues #940, #922, and #1416 for the reported non-European-language use cases. Add a representative property example showing the required language-supporting analyzer, and confirm the documentation clearly explains the configuration.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100