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
es.read.field.exclude behaves strangely with arrays #590
Comments
Hi, Found the problem and fixed it (at least the filter parsing). However there is some more work needed when used with Spark SQL since the exclusion (in mapping) is not handled when reading the |
As there hasn't been any update, closing the issue. |
Confirmed, all of the tests above worked as expected. Thank you. |
Thanks for confirming. Cheers! |
index a single document into
spark/mappingtest
such as:then run
yields a schema with
nested.bar
still included, and other odd structsexpected
changing the exclude to
conf.set("es.read.field.exclude", "nested")
returns
expected
conf.set("es.read.field.exclude", "bar*")
returns the even stranger:conf.set("es.read.field.exclude", "nested*")
does however return
I also get:
when the json document contains arrays with matching key names but in different structs when using an exclude.
Likely because the exclude I use ends up with some artifacts moved into different tree levels as seen above.
The text was updated successfully, but these errors were encountered: