Skip to content

Fixing support for empty and null arrays #1827

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

Merged
merged 1 commit into from
Jan 6, 2022

Conversation

masseyke
Copy link
Member

This commit makes it so that if an array is null in Elasticsearch, it comes into es-hadoop/spark as null. Previously
it showed up as either [] or [null], depending on spark version.
Closes #1527

Copy link
Member

@jbaiera jbaiera left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@masseyke masseyke merged commit 5160a05 into elastic:master Jan 6, 2022
@masseyke masseyke deleted the fix/null-and-empty-arrays branch January 6, 2022 22:20
@jrodewig jrodewig added v7.17.1 and removed v7.17.0 labels Jan 28, 2022
masseyke added a commit to masseyke/elasticsearch-hadoop that referenced this pull request Jan 28, 2022
This commit makes it so that if an array is null in Elasticsearch, it comes into es-hadoop/spark as null. Previously
it showed up as either [] or [null], depending on spark version.
Closes elastic#1527
masseyke added a commit that referenced this pull request Jan 28, 2022
This commit makes it so that if an array is null in Elasticsearch, it comes into es-hadoop/spark as null. Previously
it showed up as either [] or [null], depending on spark version.
Closes #1527
masseyke added a commit to masseyke/elasticsearch-hadoop that referenced this pull request Jan 28, 2022
This commit makes it so that if an array is null in Elasticsearch, it comes into es-hadoop/spark as null. Previously
it showed up as either [] or [null], depending on spark version.
Closes elastic#1527
masseyke added a commit that referenced this pull request Jan 31, 2022
This commit makes it so that if an array is null in Elasticsearch, it comes into es-hadoop/spark as null. Previously
it showed up as either [] or [null], depending on spark version.
Closes #1527
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

array type default is array and has one null value
3 participants