Support complex Hive views

[findepi]

• [x] integrate Coral with Presto https://github.com/prestosql/presto/pull/4661
• [x] Fix hive.translate-hive-views handling https://github.com/prestosql/presto/issues/5623
• [x] Cannot access Hive view when Hive catalog name is not "hive" https://github.com/prestosql/presto/issues/5785
• [ ] documentation https://github.com/prestosql/presto/issues/4619
• [ ] Improve Calcite shading https://github.com/prestosql/presto/issues/5604
• [ ] Add tests for Hive view privilege checks https://github.com/prestosql/presto/issues/5605
• [ ] Support Hive view containing current_date(), current_timestamp() #5688
• [x] Support Hive VIEW with current_user #6718
• [ ] Hive function call in a Hive view is not translated into Presto signature #5978
• [ ] Ensure date functions in Hive VIEW are considered to have right return type #5979
• [ ] Support Hive VIEW with translate() function call #5975
• [x] Support HIVE VIEW with LATERAL VIEW json_tuple AS ... #7242
• [ ] Support HIVE VIEW with LATERAL VIEW json_tuple without AS #7456
• [ ] Support HIVE VIEW with get_json_object #7457
• [x] Support Hive VIEW with common table expression (WITH CTE) #5977
• [ ] Support Hive VIEW with CAST to decimal #6450
• [ ] Support Hive VIEW with simple CASE expression https://github.com/prestosql/presto/issues/5837
• [ ] Support Hive VIEW with LATERAL VIEW [OUTER] EXPLODE on array of struct #7408
• [ ] Support Hive VIEW with UNION (DISTINCT) #7295
• [ ] Support Hive VIEW with window function #6353
• [ ] Support Hive VIEW with text || concatenation (including coercions) #6762
• [ ] Support Hive views that uses type coercions that are different in Hive than Trino #7393
• [ ] Hive VIEW with char(n) fails with "View is stale; it must be re-created" #6234
• [ ] Respect hive.timestamp-precision in Hive VIEW #6295
• [ ] Test Hive VIEW with all Hive data types #6269
• [ ] Accessing Hive VIEW with anonymous columns fails with "view .. is stale; it must be re-created" #5908
• [ ] Update outdated Hive VIEW product tests #5911
• [ ] Add tests for view staleness detection #5917
• [ ] Support custom UDFs https://github.com/prestosql/presto/issues/5689
• [x] Queries on information_schema.views fails due to hive view translation failure https://github.com/prestosql/presto/issues/6370
• [ ] Unusable SHOW CREATE VIEW when Hive view isn't compatible with Presto syntax #3693
• [x] Incorrect results when Hive VIEW contains array subscript with non-literal #7271
• [x] Incorrect query results when reading Hive VIEW with nested GROUP BYs #7635
• [ ] SerDeException for Avro Hive views #8748
• [x] https://github.com/trinodb/trino/issues/8789
• [x] #8853
• [ ] Incorrect translation of table.* references in Hive views #9027
• [ ] Support Hive view containing INTERVAL #9058
• [ ] #9023
• [ ] Add an option to run Hive views as INVOKER #9227
• [ ] https://github.com/trinodb/trino/issues/10156

[findepi]

cc @laurachenyu @phd3

[wmoustafa]

I think "Support custom UDFS" should refer to #5689 instead.

[wmoustafa]

Created Coral Slack workspace to discuss the roadmap and the prioritization of those issues. Everyone is welcome to join.

[wmoustafa]

@findepi, can we mark which of those issues (maybe in each issue) were encountered in a real use case vs synthetic testing? Can we also ask users to thumb up an issue if they are facing it? This way we can get a sense if the issue was created as part of a validation test, or a real user problem, and how many are interested in it. This will largely guide which issues to prioritize. cc: @martint @electrum @dain

[findepi]

can we mark which of those issues (maybe in each issue) were encountered in a real use case vs synthetic testing?

Thats interesting idea but we never do this. I actually believe edge cases are easier to find by experts in the given technology, so that end users can enjoy peace of mind.

Can we also ask users to thumb up an issue if they are facing it?

there is no good way to ask for this, but people may do this nonetheless

[Manish-starburst]

Can we link this issue: https://github.com/prestosql/presto/issues/6353