So the change was made by Impala developer but it is only relevant to Kudu, taking away the only way to swap tables.
I am curious if this change was agreed with Kudu devs. And if changes like that should be tracked by both Kudu and impala JIRAs since Impala is the only way right now to work with Kudu, besides APIs, that requires coding. Is there someone who chairs this type of decisions that impact Impala / Kudu users? This is important for me to understand before we invest into Kudu. On Fri, Jul 27, 2018 at 8:53 AM Boris Tyukin <bo...@boristyukin.com> wrote: > oh no....why?? 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 > <https://issues.apache.org/jira/browse/IMPALA-5654> should never been > approved without giving users a good alternative. > > Boris > > On Fri, Jul 27, 2018 at 7:10 AM Cliff Resnick <cre...@gmail.com> wrote: > >> We sometimes need to replace dimension tables in Kudu in a live database. >> The technique is described here: >> >> >> https://boristyukin.com/how-to-hot-swap-apache-kudu-tables-with-apache-impala/ >> >> After 2.12 and IMPALA-5654 >> <https://issues.apache.org/jira/browse/IMPALA-5654> it seems there is no >> longer a way to perform the final step, where the hot swap Kudu target >> table is renamed back to the original. It looks like IMPALA-6375 >> <https://issues.apache.org/jira/browse/IMPALA-6375> is going to address >> this, but in the meantime is there another workaround we can use? >> >> >> >> >>
