rename fieldQuery/fieldFilter to termQuery/termFilter in mappers
Use FieldType and not deprecated Field construction
more mapper simplification, reduce the value methods
support multiple values when mappers construct queries
this will allow us to optimize parsing using actual values (numbers/bytes)
use object parser value for queries that support it
fix index xcontent flag with id
add explicit termsFilter in mapper, and use that in terms filter
This also enabled support for terms filter on _id field for example
backport lucene 4.1 terms filter and use it where applicable
fix thread pool stats largest
cleanup unused term factory
cleanup more calls to Term with String value
move regex to use Object as paramater as well
remove unused method
cleanup
optimize search hit to use Text for type and id
this will reduce serialization string overheads, and faster xcontent(json) generation
Support for hunspell token filter

Closes: #646

- Introduced HunspellService which holds a repository of hunspell dictionaries
- It is possible to register a dictionary via a plugin or by placing the dictionary files on the file system
Support for root logger level runtime update

Closes: #2517
add simple way to get the index creation version when building a mapper
Changed how the stored values of numeric fields are stored in the index. Before numeric values were stored in binary representation, now the values in numeric representation.
fixed hunspell test to clean up properly