Closed findepi closed 3 years ago
cc @laurachenyu @phd3 @wmoustafa
Since it worked in Presto 344, i am marking this as a bug.
Since it worked in Presto 344, i am marking this as a bug.
Note that in 344, it was best effort. There was not guarantee about correctness or semantics, so I wouldn't consider it as "working".
I agree, i wouldn't call the overall complex hive view support as "working" in 344. CTE were working though, even if incidentally only. (from end-user perspective it may not matter why something is working, only whether it's working). Admittedly, the regression is failure on our side -- we did not document nor test what's actually working and what is not, so we couldn't see any regressions when doing https://github.com/prestosql/presto/pull/4661.
We are impacted by this issue and we ended up rolling back our recent upgrade (hive views support is a key requirement in our environment). Really appreciate any quick resolution to this challenge.
@rzhang10 started looking into this last week. We are encountering a couple of issues, but hopefully the fix will be out soon.
In the meantime, we're providing legacy behavior as an escape hatch for this and couple other regressions encountered with the introduction of Coral: https://github.com/prestosql/presto/pull/6195 This should remove blockers and help users in the short term, allowing us to focus on building better Hive VIEW support for the long term.
cc @losipiuk
This is addressed in Coral now https://github.com/linkedin/coral/pull/125. Thanks to @uzshao for the patch!
@wmoustafa, thanks! Is that in a release build, yet?
@martint, yes, in version 1.0.83
.
@uzshao that's awesome!
would you be willing to bump the coral version used in trino, along with adding a regression test in io.trino.tests.product.hive.AbstractTestHiveViews
?
cc @losipiuk
@findepi There's a PR open at https://github.com/trinodb/trino/pull/8935 which updates this all the way to 1.0.89.
@findepi There's a PR open at #8935 which updates this all the way to 1.0.89.
thanks @hashhar @ebyhr !
we should also add a test for a view with a WITH
. that would close this issue.