-
Notifications
You must be signed in to change notification settings - Fork 359
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
SparkSql Editor fetch_result issues with complex types - Hue 4.10 #2948
Comments
Hi @elisabetao, |
HI @Harshg999 Harsh, Sorry for the delay, yes I have tested the latest code in the master branch in github , the issues is still there for complex types. Here is how it looks You can test also on your side with an example as follows: Thanks a lot |
Hi @elisabetao what is the expected output I will try to reproduce it and look into it.Can u also share your ini file configuration. |
Hi @divincode , thanks for the update . I would expect to have the same results as in Hive : I think it's similar to the issue you remarked also for Trino/Presto. On my side to at least allow the display of the data in desktop/libs/notebook/src/notebook/connectors/spark_shell.py I updated the following in _fetch_result, as a quick hack/workaround :
but parsers need to be handled for all non Hive editors for Complex types.
|
This issue is stale because it has been open 30 days with no activity and is not "roadmap" labeled or part of any milestone. Remove stale label or comment or this will be closed in 5 days. |
Hi @elisabetao, thank you for opening this issue! |
Describe the bug:
When querying complex types in the latest Spark SQL Editor in Hue 4.10 the results are not being displayed by the _fetch_result method in desktop/libs/notebook/src/notebook/connectors/spark_shell.py
Steps to reproduce it?
Create a table with struct, array ort map types and query it though the SparkSQL Livy Editor
For now I am setting the type to string in case field['type']) is map or array, but maybe a better parser could be used for results fetching in SparkSQL Editor. Have anyone else encountered this issue?
Thanks a lot
The text was updated successfully, but these errors were encountered: