impala-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Tauber-Marshall (JIRA)" <>
Subject [jira] [Created] (IMPALA-5284) Eliminate our dependence of the Kudu Java client
Date Fri, 05 May 2017 20:38:04 GMT
Thomas Tauber-Marshall created IMPALA-5284:

             Summary: Eliminate our dependence of the Kudu Java client
                 Key: IMPALA-5284
             Project: IMPALA
          Issue Type: Improvement
    Affects Versions: Impala 2.9.0
            Reporter: Thomas Tauber-Marshall
            Priority: Critical

Its difficult to ensure that we're always using the same versions of the Java and C++ Kudu
clients, potentially leading to conflicts. It would be nice if we could eliminate our dependence
on the Java client.

One way to do this would be to add JNI calls in the FE/catalog to call into the Kudu C++ client
in the BE. Unfortunately, this could result in a lot of boiler plate code, as there are a
lot of Kudu client functions that are called from the FE/catalog (e.g. tableExists, openTable,
createTable, deleteTable, getSchema, getPartitionSchema, getColumns) that would need to be
routed through the JNI.

This message was sent by Atlassian JIRA

View raw message