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

Field Data: optimize long type to use narrowest possible type automatically #2795

Closed
kimchy opened this issue Mar 18, 2013 · 0 comments
Closed

Comments

@kimchy
Copy link
Member

kimchy commented Mar 18, 2013

We load the values to memory, while we load, we can detect what is the narrowest type we need to in order to represent it in memory. This is the main reason why typically an explicit numeric type would be used in mapping, which is now no longer needed really...

@kimchy kimchy closed this as completed in 7d9cef9 Mar 18, 2013
pdegeus added a commit to pdegeus/elasticsearch that referenced this issue Mar 20, 2013
# By Shay Banon (43) and others
# Via Shay Banon
* master-upstream: (97 commits)
  better comment...
  if multicast socket closes, try and restart it also, throttle on socket failures, so it won't spin out of control... relates to elastic#2783
  multicastSocket should be volatile as well...
  broadcast API to by default ignore missing / illegal shard state this happens for example because we list assigned shards, and they might not have been allocated on the relevant node yet, no need to list those as actual failures in some APIs
  upgrade to guava 14.0.1
  tar.gz distro by mistake include a windows lib
  fix javadoc
  Correct filter strategy opt: random_access_random to random_access_always
  Field Data: optimize long type to use narrowest possible type automatically closes elastic#2795
  make ES compile with java 8 - that isAnnotationPresent bug is known, and probably will be fixed in later versions, but it costs us nothing to not use it now - some tests fail, mainly due to consistent ordering expected from Map (within versions) which does not seem to be preserved, need to fix those tests to be agnostic to it
  use ImmutableList.Builder instead of ArrayList
  fix logging message to include the index also add the list of current indices
  Mapping: dynamic flag is explicitly returned even when not set fixes elastic#2789
  Fix bug in RateLimiter.SimpleRateLimiter causing numeric overflow in StoreStats
  improve TODO comment
  add CamelCase support to Suggester where missing
  Remove `sort_order` and `sort_mode` in favor of `order` and `mode`
  Add `sort_oder` and `sortOrder` as valid field names for defining the sort order in a Sort object.
  Make StupidBackoff the default smoothing model for phrase suggester
  minor cleanup suggest api - make sure we close the parser - fail when no content is provided in the rest request - reuse the suggest parse element
  ...
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

1 participant