-
Notifications
You must be signed in to change notification settings - Fork 24.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
XContentParser with excludes filters emits invalid json in common cases #80142
Comments
Pinging @elastic/es-core-infra (Team:Core/Infra) |
Oh yeah, that's fixed in modern jackson. Let's see about updating! |
This grabs a new version of jackson and snakeyaml to get some bug fixes. It also updates azure to stay compatible with the new jackson. Closes elastic#66555 Closes elastic#67214 Closes elastic#80142
This grabs a new version of jackson and snakeyaml to get some bug fixes. It also updates azure to stay compatible with the new jackson. Closes elastic#66555 Closes elastic#67214 Closes elastic#80142
in the new jackson version, filterOnBuilder is ok, but filterOnParser is also bad |
The upgrade to jackson in #80160 did seem to fix it for me. That's just stuck.... |
It happens to me a lot too. I'm glad it's fixed though. |
Elasticsearch version (
bin/elasticsearch --version
): masterPlugins installed: [] no
JVM version (
java -version
):OS version (
uname -a
if on a Unix-like system):Description of the problem including expected versus actual behavior:
Steps to reproduce:
Please include a minimal but complete recreation of the problem,
including (e.g.) index creation, mappings, settings, query etc. The easier
you make for us to reproduce it, the more likely that somebody will take the
time to look at it.
AbstractXContentFilteringTestCase
I think the right action is passed the test.
It appears in excludes mode.
when excludes pattern contain than longer than input. like:
and the pattern is : bar.xxx.
The text was updated successfully, but these errors were encountered: