[
https://issues.apache.org/jira/browse/KUDU-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16011082#comment-16011082
]
Todd Lipcon commented on KUDU-2010:
-----------------------------------
My guess here is that the the table was very large and for some reason it was
taking a long time to complete the "alter table" statement. This caused the
timeout, and also the inconsistent-looking behavior afterward. "GetTableSchema"
will continue to return the old schema until the alter-table command is
complete, so if something was keeping it from completing in a timely fashion, I
can imagine seeing the issue as reported. However, it seems incorrect that
Impala's "ALTER" went through.
[~bruceSz] what version of the Impala-Kudu integration are you using? Are you
on Impala 2.8? The latest versions of Impala do not store column metadata in
the HMS, so I would expect it to be consistent with the Java client, but if
you're on an older release you might see different behavior.
> java kudu client get wrong column info from kudu-master
> -------------------------------------------------------
>
> Key: KUDU-2010
> URL: https://issues.apache.org/jira/browse/KUDU-2010
> Project: Kudu
> Issue Type: Bug
> Components: client, master
> Reporter: zhangsong
> Priority: Minor
>
> when issuing "alter table " command to rename a kudu table from
> impala-shell, impala throw a exception "operation timeout"
> sql is like "alter table xx rename coupontype_new coupontype int"
> After that , found the column is not renamed , the column is still named
> "coupontype_new " from impala. but the column has been altered to coupontype
> on kudu-master ui. with version=1.
> Meanwhile the table is not readable anymore due to "unknown column"
> exception.
> Using a java-client (both 0.10.0 and 1.2) to get schema, found the column's
> name is still the old one : "coupontype_new" .(which is strange, on
> kudu-master ui' the column's name has been changed to new name "coupontype")
> after altering kudu-table's column name back to old one using java
> kudu-client , the issue is solved temporarily.
> So the problem is that java kudu-client 's "getSchema" api return different
> schema infos compared with those shown on kudu-master ui.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
