[Rule-based Auto-tagging] Add autotagging label resolving logic for multiple attributes#19486
Conversation
53fdb71 to
b3c9653
Compare
|
❌ Gradle check result for b3c9653: 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? |
modules/autotagging-commons/common/src/main/java/org/opensearch/rule/autotagging/Attribute.java
Outdated
Show resolved
Hide resolved
modules/autotagging-commons/common/src/main/java/org/opensearch/rule/autotagging/Attribute.java
Outdated
Show resolved
Hide resolved
modules/autotagging-commons/common/src/main/java/org/opensearch/rule/autotagging/Attribute.java
Outdated
Show resolved
Hide resolved
...utotagging-commons/common/src/main/java/org/opensearch/rule/storage/AttributeValueStore.java
Outdated
Show resolved
Hide resolved
...utotagging-commons/common/src/main/java/org/opensearch/rule/storage/AttributeValueStore.java
Outdated
Show resolved
Hide resolved
...utotagging-commons/common/src/main/java/org/opensearch/rule/storage/AttributeValueStore.java
Show resolved
Hide resolved
modules/autotagging-commons/common/src/main/java/org/opensearch/rule/FeatureValueMatch.java
Outdated
Show resolved
Hide resolved
modules/autotagging-commons/common/src/main/java/org/opensearch/rule/RuleAttribute.java
Outdated
Show resolved
Hide resolved
...utotagging-commons/src/main/java/org/opensearch/rule/labelresolver/FeatureValueResolver.java
Show resolved
Hide resolved
b3c9653 to
c4ce839
Compare
|
❌ Gradle check result for c4ce839: 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? |
c4ce839 to
6fc3ea6
Compare
|
❌ Gradle check result for 6fc3ea6: 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? |
6fc3ea6 to
12c5c98
Compare
|
❌ Gradle check result for 12c5c98: 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? |
12c5c98 to
43b2f02
Compare
139da8b to
291e67a
Compare
|
❌ Gradle check result for 291e67a: 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? |
|
@ruai0511 Do you want to iterate this to green: cc: @kaushalmahi12 |
...totagging-commons/src/main/java/org/opensearch/rule/feature_value_resolver/package-info.java
Outdated
Show resolved
Hide resolved
Signed-off-by: Ruirui Zhang <mariazrr@amazon.com>
Signed-off-by: Ruirui Zhang <mariazrr@amazon.com>
869da6e to
31fd4fb
Compare
|
@ruai0511 - Can you look into precommit failure: |
31fd4fb to
23d82c0
Compare
|
❌ Gradle check result for 23d82c0: 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: Ruirui Zhang <mariazrr@amazon.com>
23d82c0 to
4fb5ab2
Compare
|
❕ Gradle check result for 4fb5ab2: UNSTABLE Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure. |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #19486 +/- ##
============================================
+ Coverage 72.99% 73.01% +0.01%
+ Complexity 70416 70414 -2
============================================
Files 5708 5711 +3
Lines 322492 322585 +93
Branches 46704 46716 +12
============================================
+ Hits 235412 235536 +124
+ Misses 68161 68065 -96
- Partials 18919 18984 +65 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
…ultiple attributes (opensearch-project#19486) Signed-off-by: Ruirui Zhang <mariazrr@amazon.com>
Description
In the past, the auto tagging label resolving logic is only suitable for single attribute evaluation. Since we're adding more attributes into the feature now (username, role, index_pattern), we need a more comprehensive logic to find the best suited rule and label.
Feature documentation: https://docs.opensearch.org/latest/tuning-your-cluster/availability-and-recovery/rule-based-autotagging/autotagging/
Main classes & functions introduced:
Related Issues
Resolves #[Issue number to be closed when this PR is merged]
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.