-
Notifications
You must be signed in to change notification settings - Fork 28.5k
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
[SPARK-10113][SQL] Explicit error message for unsigned Parquet logical types #9646
Conversation
Test build #45693 has finished for PR 9646 at commit
|
cc @liancheng |
Would you please rename the PR title to "Explicit error message for unsigned Parquet logical types"? Since this PR doesn't introduce "support" for unsigned types. Otherwise LGTM. Thanks! |
This seems fine for now, but its not clear to me why the right answer isn't to read it in as a higher precision signed type. |
Merging to master and 1.6 |
…l types Parquet supports some unsigned datatypes. However, Since Spark does not support unsigned datatypes, it needs to emit an exception with a clear message rather then with the one saying illegal datatype. Author: hyukjinkwon <gurwls223@gmail.com> Closes #9646 from HyukjinKwon/SPARK-10113. (cherry picked from commit f5a9526) Signed-off-by: Michael Armbrust <michael@databricks.com>
@marmbrus That's also an option, but seems somewhat confusing to me. Especially, in this way |
…l types Parquet supports some unsigned datatypes. However, Since Spark does not support unsigned datatypes, it needs to emit an exception with a clear message rather then with the one saying illegal datatype. Author: hyukjinkwon <gurwls223@gmail.com> Closes apache#9646 from HyukjinKwon/SPARK-10113.
Parquet supports some unsigned datatypes. However, Since Spark does not support unsigned datatypes, it needs to emit an exception with a clear message rather then with the one saying illegal datatype.