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.

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

Use Lucene's native encoding of numeric stored values #2433

Closed
chrismale opened this issue Nov 22, 2012 · 1 comment
Closed

Use Lucene's native encoding of numeric stored values #2433

chrismale opened this issue Nov 22, 2012 · 1 comment

Comments

@chrismale
Copy link
Contributor

Currently ElasticSearch converts numeric values to byte arrays for storing. However Lucene has native storage of numeric values which has less overhead.

We need to support backwards compatibility with indexes using the byte array encoding, therefore we will use the ElasticSearch index version as a way to identify those indexes that will be using the byte array encoding and those that will be using the native encoding.

@kimchy
Copy link
Member

kimchy commented Feb 26, 2013

Implemented.

@kimchy kimchy closed this as completed Feb 26, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants