[
https://issues.apache.org/jira/browse/KUDU-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Henke resolved KUDU-2010.
-------------------------------
Fix Version/s: NA
Resolution: Cannot Reproduce
> 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
> Fix For: NA
>
>
> 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
(v8.3.4#803005)
