OpenSearch

History

Alan Woodward d23112f441 Report parser name and location in XContent deprecation warnings (#53805 ) It's simple to deprecate a field used in an ObjectParser just by adding deprecation markers to the relevant ParseField objects. The warnings themselves don't currently have any context - they simply say that a deprecated field has been used, but not where in the input xcontent it appears. This commit adds the parent object parser name and XContentLocation to these deprecation messages. Note that the context is automatically stripped from warning messages when they are asserted on by integration tests and REST tests, because randomization of xcontent type during these tests means that the XContentLocation is not constant	2020-03-20 11:52:55 +00:00
..
src/test/java/org/elasticsearch/http	Report parser name and location in XContent deprecation warnings (#53805 )	2020-03-20 11:52:55 +00:00
build.gradle	Apply 2-space indent to all gradle scripts (#49071 )	2019-11-14 11:01:23 +00:00

Alan Woodward d23112f441 Report parser name and location in XContent deprecation warnings (#53805 )

It's simple to deprecate a field used in an ObjectParser just by adding deprecation
markers to the relevant ParseField objects. The warnings themselves don't currently
have any context - they simply say that a deprecated field has been used, but not
where in the input xcontent it appears. This commit adds the parent object parser
name and XContentLocation to these deprecation messages.

Note that the context is automatically stripped from warning messages when they
are asserted on by integration tests and REST tests, because randomization of
xcontent type during these tests means that the XContentLocation is not constant

2020-03-20 11:52:55 +00:00

src/test/java/org/elasticsearch/http

Report parser name and location in XContent deprecation warnings (#53805 )

2020-03-20 11:52:55 +00:00

build.gradle

Apply 2-space indent to all gradle scripts (#49071 )

2019-11-14 11:01:23 +00:00