You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Thomas Tauber-Marshall (JIRA)" <ji...@apache.org> on 2017/08/14 22:39:00 UTC
[jira] [Created] (IMPALA-5799) INSERTs into Kudu can crash if a
column is dropped concurrently
Thomas Tauber-Marshall created IMPALA-5799:
----------------------------------------------
Summary: INSERTs into Kudu can crash if a column is dropped concurrently
Key: IMPALA-5799
URL: https://issues.apache.org/jira/browse/IMPALA-5799
Project: IMPALA
Issue Type: Bug
Components: Backend
Affects Versions: Impala 2.10.0
Reporter: Thomas Tauber-Marshall
Priority: Critical
When inserting into a Kudu table, we check that the table schema matches the values to insert during planning. Once the KuduTableSink opens the KuduTable object, we're guaranteed that the KuduTable's schema won't change.
However, there's a window of vulnerability between the checks in the FE and opening the table in the BE where the schema could change. The only change that we allow that is incompatible is dropping a column, which can cause Impala to crash.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)