Adding forbidden API check for buggy range query behavior (#128671) (#128765)

This adds the buggy functions to forbidden API check. Will remove once
Lucene is updated.

Related #128671
This commit is contained in:
Benjamin Trent 2025-06-02 12:26:40 -04:00 committed by GitHub
parent bbd65c69ba
commit c28e01ecf4
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -61,3 +61,11 @@ org.apache.logging.log4j.message.ParameterizedMessage#<init>(java.lang.String, j
@defaultMessage Use WriteLoadForecaster#getForecastedWriteLoad instead @defaultMessage Use WriteLoadForecaster#getForecastedWriteLoad instead
org.elasticsearch.cluster.metadata.IndexMetadata#getForecastedWriteLoad() org.elasticsearch.cluster.metadata.IndexMetadata#getForecastedWriteLoad()
# This is a temporary patch as there is a low level Lucene bug in certain scenarios
# this should be fixed in the new Lucene release 10.3+
org.apache.lucene.document.LongField#newExactQuery(java.lang.String, long) @ Use org.elasticsearch.lucene.document.NumericField#newExactLongQuery(java.lang.String, long) instead.
org.apache.lucene.document.LongField#newRangeQuery(java.lang.String, long, long) @ Use org.elasticsearch.lucene.document.NumericField#newRangeLongQuery(java.lang.String, long, long) instead.
org.apache.lucene.document.IntField#newExactQuery(java.lang.String, int) @ Use org.elasticsearch.lucene.document.NumericField#newExactIntQuery(java.lang.String, int) instead.
org.apache.lucene.document.IntField#newRangeQuery(java.lang.String, int, int) @ Use org.elasticsearch.lucene.document.NumericField#newRangeIntQuery(java.lang.String, int, int) instead.
org.apache.lucene.search.IndexSortSortedNumericDocValuesRangeQuery @ use org.elasticsearch.lucene.search.XIndexSortSortedNumericDocValuesRangeQuery instead.