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
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
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
Hi Baptiste,
There's an on-going work that enhances the impalad to be able to shut down
gracefully: https://gerrit.cloudera.org/c/10744/ Thanks to Tim's efforts on
this and hope it can be merged soon (so the patch can be more easier to merge
into the 2.x branch).
We've faced the similar
