Roadmap for 2.0

[clintongormley]

• Switch doc_values=true to be the default for non-analyzed string fields #8312 Use doc values by default
• Remove possibility for conflicting field definitions and ambiguous field resolution #8870 Field/type mapping refactor
• Add ability to perform computations on aggregations #9876 Perform computation on aggregations
• Only send diff of cluster state instead of full cluster state #6295 Update cluster state using diffs
• Refactor parsing of queries/filters, aggs, suggester APIs #10217 Refactor query and filter, agg, suggester parsing/serialization (bumped to 3.0)
• Warn when using deprecated syntax #8963 Warn when using deprecated syntax
• Upgrade to Netty 4.0 #3226 Upgrade to Netty 4
• Lucene 5.1
• Lucene 5.2
• Testing and packaging changes for 2.0 #12768 Tests and packaging changes
• Shards should rebalance across multiple path.data on one node #11271 Shards should rebalance across multiple path.data on one node
• Remove SpawnModules #12783 Remove spawn modules

Index migration:

• [STORE] Move to one datapath per shard #9498 Move to one datapath per shard
• Allow upgrade API to only upgrade too-old segments #10213 Allow upgrade API to only upgrade too-old segments
• Migration advisory plugin  #10214 Migration advisory _site plugin
• Don't allow indices containing too-old segments to be opened #10215 Don't allow indices containing too-old segments to be opened

[joealex]

#6295 will be pretty important to have for very large clusters and have the flexibility to keep adding Nodes

#8312 is very much awaited along with #9498 which seems like got moved to 2.0 ?

[leonardehrenfried]

I know it's a little impatient to ask, but is there any indication when an ES2 beta will be released?

[dmitry]

Looks like there are still a lot of unclosed issues: https://github.com/elastic/elasticsearch/labels/v2.0.0

[runarmyklebust]

Does this mean that the suggested filter/query-merge are postponed to v3? Would be nice to know, since it will impact our development plans.

[clintongormley]

@runarmyklebust no - that's already merged. the query refactoring is about the java api and where requests get parsed: coordinating node or shard level. unrelated to the query/filter merging

[runarmyklebust]

Ok, thanks a lot, got me a bit worried there.