Affects Version/s: None
Fix Version/s: None
This bug is a follow-on from
Although I could INSERT...SELECT from my Impala table into an unpartitioned Kudu table (after doing away with a TIMESTAMP column that caused an error), when I tried the exact same operation where the destination was a partitioned Kudu table, then I got another conversion error saying the Impala BOOLEAN type wasn't supported. Again, the Kudu docs say the BOOLEAN type should work:
Notice a couple of things:
- In this case, the source table is another Kudu table, not the original Impala table. (How does Kudu know at that point that the BOOLEAN data inside a Kudu table is the Impala BOOLEAN type?)
- The only difference between table log_ingest_docs_kudu (where the INSERT...SELECT worked) and log_ingest_docs_kudu2 (where it failed) is the DISTRIBUTE BY HASH added to the latter.
- The BOOLEAN message is stated to be a warning, yet it caused the operation to fail, since no rows are inserted into the destination table.
- If I go back to log_ingest_docs_kudu where the data (including the BOOLEAN column) was successfully transferred, I find that I can't do any query that references the BOOLEAN column. So the problem manifests itself consistently in the SELECT statement, and inconsistently in the INSERT statement (depends on whether the table has a DISTRIBUTE BY clause or not).