-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use terms in set for concrete IPs keep disjunctions over ranges. fix #16200 #16202
Conversation
Please confirm my understanding, then I come up with thorough testing. |
❌ Gradle check result for e782068: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
❌ Gradle check result for 0a1c3d0: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
❌ Gradle check result for bebebac: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
❌ Gradle check result for fbbb0bc: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Signed-off-by: mikhail-khludnev <[email protected]>
0586f06
to
da89a31
Compare
❌ Gradle check result for da89a31: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Signed-off-by: mikhail-khludnev <[email protected]>
❌ Gradle check result for 33b8494: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Signed-off-by: mikhail-khludnev <[email protected]>
❌ Gradle check result for 3c15413: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Signed-off-by: mikhail-khludnev <[email protected]>
❌ Gradle check result for 853a344: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
https://build.ci.opensearch.org/job/gradle-check/49705/consoleFull I'm not sure what I can do with it. |
import static org.opensearch.action.support.WriteRequest.RefreshPolicy.IMMEDIATE; | ||
import static org.hamcrest.Matchers.equalTo; | ||
|
||
public class SearchIpFieldTermsTests extends OpenSearchSingleNodeTestCase { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It might be too heavy testing approach for the current change. However, such depth is necessary for the second stage (when ranges will be combined at PointsVisitor level).
There might be just a IpFieldTypeTest
asserting resulting BooleanQuery has set of IP points. WDYT?
final String ip; | ||
final int prefix; | ||
if (IPv4_ONLY) { | ||
ip = generateRandomIPv4(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's just IP4 test, no IP6. Is IP6 necessary, is it worth to combine 6th and 4th in the single test?
closing in favor of #16391 |
Description
Combines a many concrete IPs into set when querying IP field
Related Issues
Resolves #16200
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.