-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Raise error when unrecognized content token type is found while indexing #19097
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
Raise error when unrecognized content token type is found while indexing #19097
Conversation
|
❌ Gradle check result for ac73676: 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? |
ac73676 to
af8219f
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #19097 +/- ##
============================================
+ Coverage 72.79% 72.83% +0.03%
- Complexity 69605 69683 +78
============================================
Files 5658 5658
Lines 320079 320078 -1
Branches 46345 46345
============================================
+ Hits 232996 233114 +118
+ Misses 68230 68085 -145
- Partials 18853 18879 +26 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Signed-off-by: Bruce Hong <bruce.hong@glean.com>
…com/bruce-hong-glean/OpenSearch into fix-false-allow-templates-edge-case
Signed-off-by: Bruce Hong <bruce.hong@glean.com>
|
❌ Gradle check result for f87c059: null 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: Bruce Hong <bruce.hong@glean.com>
|
^ wanted to bump this. Wasn't really sure what a good solution to the remaining comment was. cc @andrross as well since you helped merge the original PR |
|
❕ Gradle check result for 57d5304: 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. |
…ing (opensearch-project#19097) Signed-off-by: Bruce Hong <bruce.hong@glean.com>
…ing (opensearch-project#19097) Signed-off-by: Bruce Hong <bruce.hong@glean.com> Signed-off-by: Ankit Jain <jainankitk@apache.org>
…ing (opensearch-project#19097) Signed-off-by: Bruce Hong <bruce.hong@glean.com> Signed-off-by: Ankit Jain <jainankitk@apache.org>
…ing (opensearch-project#19097) Signed-off-by: Bruce Hong <bruce.hong@glean.com>
…ing (opensearch-project#19097) Signed-off-by: Bruce Hong <bruce.hong@glean.com>
…ing (opensearch-project#19097) Signed-off-by: Bruce Hong <bruce.hong@glean.com>
Description
We merged this PR last week to introduce
false_allow_templatesas an indexing option. Taking another pass after it was merged, I realized it changed some behaviour in other indexing cases too (where there in an unrecognized content token). This should probably throw an error regardless of indexing rules and this returns to status quo before the PR above.Related Issues
Not sure how strict this is. Let me know if I should create an issue for this.
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.