presto cli error message is confusing
See original GitHub issueIn a schema, where no table foo
exists, if I issue this query:
select * from foo;
the cli responds with
select * from foo;
Query is gone (server restarted?)
In the log, this exception is logged:
I would have expected a more meaningful error message (and I think the CLI did that in the past) such as “table ‘foo’ is unknown”.
This is using presto 0.213
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Error: Presto server is still initializing - Stack Overflow
I am using presto-cli command on AWS EMR. I am passing a file (-f option) with multiple queries to execute in presto.
Read more >Troubleshooting — presto-admin 2.3 documentation
If the Presto servers fail to start or crash soon after starting, look at the presto server logs on the Presto cluster /var/log/presto...
Read more >Kerberos based authentication for Presto - Google Groups
Hi all,. We are trying to enable Kerberos authentication for our Presto cluster (version 0.143) on Amazon EMR (version emr-4.6.0) based on this...
Read more >F8 2019: Getting Started with Presto Run SQL at Any Scale
A hands- on tutorial for getting started with Presto and large-scale analytics with multiple data sources.
Read more >Presto Federated Queries - Towards Data Science
Note table references on lines 11 and 12, and on lines 13 and 41, as opposed to line 42. Again, we have run...
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
i thought the same. @hgschmie i think Presto 0.213 already contains https://github.com/prestodb/presto/pull/11792 . Are you using CLI 0.213 as well?
Fixed.