Christoph Büscher 15c59d07b3 Remove ParseFieldMatcher from AbstractXContentParser ...

Currently we are able to set a ParseFieldMatcher on XContentParsers,
mainly to conveniently carry it around to be available where the
actual parsing happens. This was just recently introduced together
with ObjectParser so that ObjectParser can make use of deprecation
logging and throwing errors while parsing.

This however is trappy because we create parsers in so many places in
the code and it is easy to forget setting the right ParseFieldMatcher.
Instead we should hold the ParseFieldMatcher only in the parse contexts
(e.g. QueryParseContext).

This PR removes the ParseFieldMatcher from XContentParser. ObjectParser
can still make use of it because we can make the otherwise unbounded
`context` type to extend an interface that makes sure contexts used in
ObjectParser can supply a ParseFieldMatcher. Contexts in ObjectParser
are now no longer optional, but it is sufficient to pass in a small
lambda expression in places where no other context is available.

Relates to #17417

2016-04-15 15:14:46 +02:00

..

src

Remove ParseFieldMatcher from AbstractXContentParser

2016-04-15 15:14:46 +02:00

build.gradle

Revert "Silence reindex's rest tests"

2016-03-02 09:17:06 -05:00