Catch RejectedExecutionException in outer ping request
Explicitly invoke refresh, this might have failed as part of type removal from the _percolator index.
Added missing metadata fields to upserted documents (parent, routing, ttl, timestamp, version and versionType)

Closes #3444
Use assertHitCount
Maxing out retries on conflict in bulk update cause null pointer exceptions

Also:
Bulk update one less retry then requested
Document for retries on conflict says it default to 1 (but default is 0)
TransportShardReplicationOperationAction methods now catches Throwables instead of exceptions
Added a little extra check to UpdateTests.concurrentUpdateWithRetryOnConflict

Closes #3447 & #3448
release 0.90.3
Included only runtime dependencies when copying

This makes sure, that no test dependencies are placed in the distribution
move to 0.90.4 snap
RPM Init script bugfix, which might prevent startup

Removing dangerous set calls, which might not set back the current state, but something invalid which leads to stop the script when proceeding
use awaitBusy, to give the delete index operation some time to remove the percolator queries associated to it on the _percolator index
Increased timeout
Improved test, printed out potential shard failures
added explicit creation of parent type in create index
take test out of the loop - too flaky
Add highlighting support for suggester.

This commit adds general highlighting support to the suggest feature.
The only implementation that implements this functionality at this
point is the phrase suggester.
The API supports a 'pre_tag' and a 'post_tag' that are used
to wrap suggested parts of the given user input changed by the
suggester.

Closes #3442
Add binary protocol backwards compatibility for suggest highlights

This change requires different request processing on the binary protocol
level since it has been we provide compatibilty across minor version.
Yet, the suggest feature is still experimental but we try best effort
to make upgrades as seamless as possible.
Improved filtering by _parent field

In the _parent field the type and id of the parent are stored as type#id, because of this a term filter on the _parent field with the parent id is always resolved to a terms filter with a type / id combination for each type in the mapping.

This can be improved by automatically use the most optimized filter (either term or terms) based on the number of parent types in the mapping.

Also added support to use the parent type in the term filter for the _parent field. Like this:
```json
{
   "term" : {
        "_parent" : "parent_type#1"
    }
}
```
This will then always automatically use the term filter.

Closes #3454
Return nothing instead of everything in MLT if no field is supported.

Today due the optimizations in the boolean query builder we adjust
a pure negative query with a 'match_all'. This is not the desired
behavior in the MLT API if all the fields in a document are unsupported.
If that happens today we return all documents but the one MLT is
executed on.

Closes #3453
Added improvements for terms filter on _parent field similar to what has been for term filter.

Relates to #3454
Improved error message when the mapping document is malformed