Docs: typo

example fails in bash

Closes #6977
[TEST] Fix SimpleThreadPoolTests to exclude test infra threads
[BUILD] skip bwc version check if directory doesn't exists or is not a directory
Reflect that 'field_value_factor' is only in 1.2.x

While the blogpost http://www.elasticsearch.org/blog/2014-04-02-this-week-in-elasticsearch/ states, that feature #5519 was
added to 1.x, the release notes for, e.g. v1.1.2, however tell otherwise.
Only the release notes for 1.2.0 list #5519 as a new feature.

Since the 1.x docs deprecate/discourage from using `_boost`, and seemingly give a migration example at
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-boost-field.html#function-score-instead-of-boost
users of 1.1.x should be warned.
[DOCS] clarify /_cat/fielddata REST api documentation
Add version 1.2.4 and 1.3.1 to the version table
Docs: Update query-string-syntax.asciidoc

Closes #6253
[DOCS] move all coming tags to added in master
Update named-queries-and-filters.asciidoc
[doc] Correct decay function equations in function_score description

Impact of decay and scale was missing from the equations.

Closes #6983
Fielddata: Fix the ordinals impl for sparse fields.

Caused by #6908
[DOCS] Fix nested root object indexing documentation

Types can no longer be specified when indexing, see:
https://github.com/elasticsearch/elasticsearch/pull/4552
Fielddata: goodbye comparators.

This commit removes custom comparators in favor of the ones that are in Lucene.

The major change is for nested documents: instead of having a comparator wrapper
that deals with nested documents, this is done at the fielddata level by having
a selector that returns the value to use for comparison.

Sorting with custom missing string values might be slower since it is using
TermValComparator since Lucene's TermOrdValComparator only supports sorting
missing values first or last. But other than this particular case, this change
will allow us to benefit from improvements on comparators from the Lucene side.

Close #5980
[TEST] Don't recycle in facets.

The recycling happening in facets is done manually and arrays are sometimes not
released. Aggregations do it in a less error-prone way by registering on to the
SearchContext.
Change numeric data types to use SORTED_NUMERIC docvalues type
instead of a custom encoding in BINARY.

In low level benchmarks this is 2x to 5x faster: its also optimized
for the common case where fields actually only contain at most one
value for each document.

Additionally SORTED_NUMERIC doesn't lose values if they appear more
than once, so mathematical computations such as averages are correct.

Closes #6967
Search & Count: Add option to early terminate doc collection

Allow users to control document collection termination, if a specified terminate_after number is
set. Upon setting the newly added parameter, the response will include a boolean terminated_early
flag, indicating if the document collection for any shard terminated early.

closes #6876
Aggregations: change to default shard_size in terms aggregation

The default shard size in the terms aggregation now uses BucketUtils.suggestShardSideQueueSize() to set the shard size if the user does not specify it as a parameter.

Closes #6857
Internal: streamline use of IndexClosedException introduced with #6475

Single index operations to use the newly added IndexClosedException introduced with #6475. This way we can also fail faster when we are try to execute operations on closed indices and their use is not allowed (depending on indices options). Indices blocks are still checked but we can already throw error while resolving indices (MetaData#concreteIndices).

Effectively this change also affects what we return when using one of the following apis: analyze, bulk, index, update, delete, explain, get, multi_get, mlt, term vector, multi_term vector. We now return `{"error":"IndexClosedException[[test] closed]","status":403}` instead of `{"error":"ClusterBlockException[blocked by: [FORBIDDEN/4/index closed];]","status":403}`.

Closes #6988