Qubole Notebook not showing federation databases
See original GitHub issueWhen running following set of command via hive or spark engine on Qubole, proper results are displayed. i.e. List of all the databases from primary & federated MSs are showing.
hive> show databases;
LIST_OF_PRIMARY_MS_SCHEMAS
LIST_OF_FEDERATED_MS_SCHEMAS
When running same query via qubole-notebook, only PM schemas are displayed. I am using same Spark cluster.
spark.sql("show databases").show()
ONLY_LIST_OF_PRIMARY_MS_SCHEMAS
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Troubleshooting Errors and Exceptions in Notebook Paragraphs
This topic provides information about the errors and exceptions that you might encounter when running notebook paragraphs. You can resolve these errors and ......
Read more >Managing Notebooks - Qubole Data Service Documentation
Viewing a Notebook Information¶. Click the notebook in the left panel to view its details. The notebook's ID, its type, associated cluster are...
Read more >Troubleshooting Notebook Issues
When troubleshooting a failed paragraph in the notebook, you can analyze the Zeppelin logs and Spark logs to identify the errors and exceptions...
Read more >Troubleshooting Query Problems – Before You Contact Support
Is the issue happening intermittently or always? If intermittent, provide successful and failed command ID(s). Was it running before successfully? Have there ...
Read more >Notebooks and Dashboards — Qubole Data Service ...
JUPY-269: Jupyter notebooks were not working with clusters configured with default locations on ADLS and ABFS storage. This issue is fixed.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for the extra info on resolving the issue!
Yeah, I’m not sure, it should really be documented in Spark/Qubole - “How to specify a custom Hive metastore” as it’s not really related to WaggleDance directly. If we add it to our documentation then we have the maintenance burden of keeping this up to date for different versions of Qubole/Spark etc.