Hi,
I think swapping tables is indeed a common need and not only for Kudu
tables. For this reason this workaround was not particularly good in my
opinion as it was Kudu-specific. Since Impala tables may have different
names than their corresponding tables in Kudu, this could be used to
provide
Thanks Tim for answering this!
One note for the very first mail in this thread:
https://issues.apache.org/jira/browse/IMPALA-6375 won't fix this issue
either. It will allow the user to make a managed Kudu table external and to
modify the underlying kudu.table_name in one step. With the current
thanks so much, Tim. I do feel much better now that you've explained the
reasons behind.
Using another client makes sense - will check that out. I did see a bunch
of methods in Kudu API but was hoping to use Impala all the way.
It would be really cool if this Jira will get traction as this is a
Hi,
Sorry you ran into this - we don't deliberately want to break workflows
but it can be tricky if we accidentally expose implementation details.
There was a previous CVE that resulted from creative use of this
functionality
oh nowhy?? just why?? we are about to upgrade to 2.12...
Todd, can this "improvement" get rolled back? This a breaking change and
does not contribute to making anything better. And now the only good way to
swap Kudu tables is gone.
I am really frustrated. IMPALA-5654
