[jira] [Resolved] (IMPALA-5284) Eliminate our dependence of the Kudu Java client

["Tim Armstrong (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IMPALA-5284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Armstrong resolved IMPALA-5284.
-----------------------------------
    Resolution: Later

> Eliminate our dependence of the Kudu Java client
> ------------------------------------------------
>
>                 Key: IMPALA-5284
>                 URL: https://issues.apache.org/jira/browse/IMPALA-5284
>             Project: IMPALA
>          Issue Type: Improvement
>    Affects Versions: Impala 2.9.0
>            Reporter: Thomas Tauber-Marshall
>            Priority: Minor
>              Labels: kudu
>
> Its difficult to ensure that we're always using the same versions of the Java and C++ Kudu clients, potentially leading to conflicts. It also makes the Impala build more cumbersome. It would be nice if we could eliminate our dependence on the Java client and just rely on the C++ 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
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org