-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[BUG] Since OpenSearch 2.12, when using flat_object, the error Preview of field's value: 'null' occurs. #13184
Comments
@naomichi-y looks like a regression, want to turn this into a (failing) YAML REST test? |
@dblock
With 2.11, the results are as follows.
2.12 has an error.
The test succeeds if the field name is 10 digits. |
@naomichi-y Thank you, this is perfect. Clearly a regression. Want to bisect it to the PR that broke it, next? |
@dblock bd5b5ee#diff-9b94311ef376a05bce2bbe32e99582f739378209a89aaa6dc4bc192e4b8f2660R111 |
Looks like this was introduced in #11425 (cc: @msfroh). Do you know the proper way to fix this @naomichi-y? Go for it! |
Okay. I'm getting a if (dotIndex != -1) {
path.setLength(Math.max(0, path.length() - currentFieldName.length() - 1));
} |
Start by writing a unit test in server/src/test/java/org/opensearch/common/xcontent/JsonToStringXContentParserTests.java that hits this problem. What is the value of |
Was this ever released? I see the fix for it was merged but I'm still hitting this on 2.14.0 Edit: My bad I was pulling the wrong docker tag |
Fixed in #13259. Closing. |
Describe the bug
I'm using
flat_object
with OpenSearch.In OpenSearch 2.12 or later, an error occurs if the field name to be registered in
flat_object
has more than 10 digits.Related component
Indexing
To Reproduce
I'm getting an internal error
String index out of range: -1
, so I tried renaming thefooooooooooo
field (11) tofooooooooooo
(10) and that solved the error.Expected behavior
The error does not occur until 2.11.
Additional Details
Plugins
Please list all plugins currently enabled.
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):
Additional context
The problem is occurring using Data Streams, but the same problem is reproduced without Data Streams.
The text was updated successfully, but these errors were encountered: