Forbid negative weight in Function Score Query#33390
Conversation
|
Pinging @elastic/es-search-aggs |
| } | ||
|
|
||
| private Float checkWeight(Float weight) { | ||
| if (weight != null && weight < 0) { |
There was a problem hiding this comment.
Can you do Float.compare(weight, 0) < 0)
|
|
||
| private Float checkWeight(Float weight) { | ||
| if (weight != null && weight < 0) { | ||
| DEPRECATION_LOGGER.deprecated("[weight] cannot be negative for a filtering function [{}]", weight); |
There was a problem hiding this comment.
Since this is master can you throw an IllegalArgumentException and we'll handle the deprecation when we backport to 6x.
There was a problem hiding this comment.
Hm... I thought that it is preferred to have one PR against master handing the deprecation (that is backported to 6.x) and a second (followup) PR for the removal (and IAE) that is only on master.
My bad;) I will change the PR shortly.
There was a problem hiding this comment.
For this one I think we can have two prs, one for the removal and one for the deprecation that targets 6x only. There are some [tests]6269744#diff-9af0a85c71293ca3d30f83fe80aedd28 in master that will fail in 6x because they produce negative weights so the backport is not trivial.
weight is negative in a Function Score Queryweight in Function Score Query
|
test this please |
…o neg_weight_depr
|
test this please |
|
Thanks @lipsill ! As discussed earlier we need a new pr for the backport in 6x where some tests need to be adapted. |
* master: (43 commits) [HLRC][ML] Add ML put datafeed API to HLRC (elastic#33603) Update AWS SDK to 1.11.406 in repository-s3 (elastic#30723) Expose CCR stats to monitoring (elastic#33617) [Docs] Update match-query.asciidoc (elastic#33610) TEST: Adjust rollback condition when shard is empty [CCR] Improve shard follow task's retryable error handling (elastic#33371) Forbid negative `weight` in Function Score Query (elastic#33390) Clarify context suggestions filtering and boosting (elastic#33601) Disable CCR REST endpoints if CCR disabled (elastic#33619) Lower version on full cluster restart settings test Upgrade remote cluster settings (elastic#33537) NETWORKING: http.publish_host Should Contain CNAME (elastic#32806) Add test coverage for global checkpoint listeners Reset replica engine to global checkpoint on promotion (elastic#33473) HLRC: ML Delete Forecast API (elastic#33526) Remove debug logging in full cluster restart tests (elastic#33612) Expose CCR to the transport client (elastic#33608) Mute testIndexDeletionWhenNodeRejoins SQL: Make Literal a NamedExpression (elastic#33583) [DOCS] Adds missing built-in user information (elastic#33585) ...
* master: (128 commits) [HLRC][ML] Add ML put datafeed API to HLRC (elastic#33603) Update AWS SDK to 1.11.406 in repository-s3 (elastic#30723) Expose CCR stats to monitoring (elastic#33617) [Docs] Update match-query.asciidoc (elastic#33610) TEST: Adjust rollback condition when shard is empty [CCR] Improve shard follow task's retryable error handling (elastic#33371) Forbid negative `weight` in Function Score Query (elastic#33390) Clarify context suggestions filtering and boosting (elastic#33601) Disable CCR REST endpoints if CCR disabled (elastic#33619) Lower version on full cluster restart settings test Upgrade remote cluster settings (elastic#33537) NETWORKING: http.publish_host Should Contain CNAME (elastic#32806) Add test coverage for global checkpoint listeners Reset replica engine to global checkpoint on promotion (elastic#33473) HLRC: ML Delete Forecast API (elastic#33526) Remove debug logging in full cluster restart tests (elastic#33612) Expose CCR to the transport client (elastic#33608) Mute testIndexDeletionWhenNodeRejoins SQL: Make Literal a NamedExpression (elastic#33583) [DOCS] Adds missing built-in user information (elastic#33585) ...
Relates to #31927