we had support most hive sql syntax, is it possible to commit to trino?
See original GitHub issuefor example:
select ‘data’ equals select “data” and select `data` equls select data in hive
but select “data” equals select data in presto
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:18 (10 by maintainers)
Top Results From Across the Web
Migrating from Hive — Trino 403 Documentation
Trino uses ANSI SQL syntax and semantics, whereas Hive uses a language similar to SQL called HiveQL which is loosely modeled after MySQL...
Read more >Hive ACID and transactional tables' support in Presto - Trino
In this blog post we cover the concepts of Hive ACID and transactional tables along with the changes done in Presto to support...
Read more >SELECT — Trino 403 Documentation
This syntax allows users to perform analysis that requires aggregation on multiple sets of columns in a single query. Complex grouping operations do...
Read more >Supporting DELETE and UPDATE — Trino 403 Documentation
The Trino engine provides APIs to support row-level SQL DELETE and UPDATE . To implement DELETE or UPDATE , a connector must layer...
Read more >Hive connector — Trino 403 Documentation
Trino only uses the first two components: the data and the metadata. It does not use HiveQL or any part of Hive's execution...
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 Free
Top 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
Conceptually Trino SQL and Hive SQL are way different. For example notice that Hive does not have a concept of catalogs.
I think you it would be better to have a proxy/gateway that would take care of SQL translation for you. So instead of going to Trino, user would connect to something else which would translate SQL and then query Trino. So this would be a different layer and so different project I guess.
👋 @ImTangYun - this issue has drawbacks that don’t align with our preferred approach, so we’re not going to proceed with this implementation. If you’d like to continue the discussion on this at any point in the future, feel free to re-open and chime in.
See: https://github.com/trinodb/trino/pull/10379#issuecomment-1301060587