impala-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthew Jacobs (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IMPALA-5286) Query with Kudu col name w/ different casing from predicate fails
Date Fri, 05 May 2017 20:51:04 GMT
Matthew Jacobs created IMPALA-5286:
--------------------------------------

             Summary: Query with Kudu col name w/ different casing from predicate fails
                 Key: IMPALA-5286
                 URL: https://issues.apache.org/jira/browse/IMPALA-5286
             Project: IMPALA
          Issue Type: Bug
          Components: Frontend
    Affects Versions: Impala 2.8.0
            Reporter: Matthew Jacobs
            Assignee: Thomas Tauber-Marshall


When a Kudu table is created outside Impala with non-lower-case column names, an Impala query
using that column name in a predicate will fail.

Example:

Create a Kudu table in the python client:
{code}
import kudu
builder = kudu.schema_builder()
builder.add_column('key').type(kudu.int64).nullable(False).primary_key()
builder.add_column('VAL', type_=kudu.int64, nullable=False)
schema = builder.build()
from kudu.client import Partitioning
partitioning = Partitioning().add_hash_partitions(column_names=['key'], num_buckets=3)
c.create_table('foo', schema, partitioning)
{code}

Then in Impala:
{code}
create external table foo stored as kudu TBLPROPERTIES ( 'kudu.table_name' = 'foo' );

select * from foo order by VAL;
{code}

results in the failure: {{Unable to deserialize scan token: Invalid argument: Duplicate column
name: VAL}}

While Impala cannot support different cased column names that conflict (e.g. "VAL" and "val"
 should not be supported, see IMPALA-5283), this query could be supported.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message