[
https://issues.apache.org/jira/browse/KUDU-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suzanne McIntosh updated KUDU-1675:
-----------------------------------
Environment: VMWare VM running Centos 6.6 and Kudu 1.0 (0.10).
Description:
The following select statement is no longer a valid way to test that
Impala-Kudu was successfully installed:
select if(version() like '%KUDU%', "all set to go!", "check your configs") as s;
'KUDU' is no longer embedded in the result returned by version():
[localhost.localdomain:21000] > version;
Shell version: Impala Shell v2.8.0-cdh5-INTERNAL () built on Fri Sep 16
00:09:21 PDT 2016
Server version: impalad version 2.8.0-cdh5-INTERNAL RELEASE (build )
Instead, the documentation (here:
http://kudu.apache.org/docs/kudu_impala_integration.html) should suggest an
alternative approach to verify that Impala-Kudu is functioning and integrated
with Kudu. For example, verify by creating a table as follows:
[localhost.localdomain:21000] > CREATE TABLE my_first_table ( id BIGINT, name
STRING ) DISTRIBUTE BY HASH INTO 16 BUCKETS TBLPROPERTIES( 'storage_handler' =
'com.cloudera.kudu.hive.KuduStorageHandler', 'kudu.table_name' =
'my_first_table', 'kudu.master_addresses' = '127.0.0.1:7051',
'kudu.key_columns' = 'id' );
Query: create TABLE my_first_table ( id BIGINT, name STRING ) DISTRIBUTE BY
HASH INTO 16 BUCKETS TBLPROPERTIES( 'storage_handler' =
'com.cloudera.kudu.hive.KuduStorageHandler', 'kudu.table_name' =
'my_first_table', 'kudu.master_addresses' = '127.0.0.1:7051',
'kudu.key_columns' = 'id' )
Fetched 0 row(s) in 0.77s
[localhost.localdomain:21000] > show tables;
Query: show tables
+----------------+
| name |
+----------------+
| my_first_table |
+----------------+
Fetched 1 row(s) in 0.01s
was:
The following select statement is no longer a valid way to test that
Impala-Kudu was successfully installed:
select if(version() like '%KUDU%', "all set to go!", "check your configs") as s;
'KUDU' is no longer embedded in the result returned by version():
[localhost.localdomain:21000] > version;
Shell version: Impala Shell v2.8.0-cdh5-INTERNAL () built on Fri Sep 16
00:09:21 PDT 2016
Server version: impalad version 2.8.0-cdh5-INTERNAL RELEASE (build )
Instead, the documentation should suggest an alternative approach to verify
that Impala-Kudu is functioning and integrated with Kudu. For example, verify
by creating a table as follows:
[localhost.localdomain:21000] > CREATE TABLE my_first_table ( id BIGINT, name
STRING ) DISTRIBUTE BY HASH INTO 16 BUCKETS TBLPROPERTIES( 'storage_handler' =
'com.cloudera.kudu.hive.KuduStorageHandler', 'kudu.table_name' =
'my_first_table', 'kudu.master_addresses' = '127.0.0.1:7051',
'kudu.key_columns' = 'id' );
Query: create TABLE my_first_table ( id BIGINT, name STRING ) DISTRIBUTE BY
HASH INTO 16 BUCKETS TBLPROPERTIES( 'storage_handler' =
'com.cloudera.kudu.hive.KuduStorageHandler', 'kudu.table_name' =
'my_first_table', 'kudu.master_addresses' = '127.0.0.1:7051',
'kudu.key_columns' = 'id' )
Fetched 0 row(s) in 0.77s
[localhost.localdomain:21000] > show tables;
Query: show tables
+----------------+
| name |
+----------------+
| my_first_table |
+----------------+
Fetched 1 row(s) in 0.01s
> Obsolete approach for verifying Impala-Kudu
> -------------------------------------------
>
> Key: KUDU-1675
> URL: https://issues.apache.org/jira/browse/KUDU-1675
> Project: Kudu
> Issue Type: Bug
> Components: documentation
> Affects Versions: 0.10.0
> Environment: VMWare VM running Centos 6.6 and Kudu 1.0 (0.10).
> Reporter: Suzanne McIntosh
>
> The following select statement is no longer a valid way to test that
> Impala-Kudu was successfully installed:
> select if(version() like '%KUDU%', "all set to go!", "check your configs") as
> s;
> 'KUDU' is no longer embedded in the result returned by version():
> [localhost.localdomain:21000] > version;
> Shell version: Impala Shell v2.8.0-cdh5-INTERNAL () built on Fri Sep 16
> 00:09:21 PDT 2016
> Server version: impalad version 2.8.0-cdh5-INTERNAL RELEASE (build )
> Instead, the documentation (here:
> http://kudu.apache.org/docs/kudu_impala_integration.html) should suggest an
> alternative approach to verify that Impala-Kudu is functioning and integrated
> with Kudu. For example, verify by creating a table as follows:
> [localhost.localdomain:21000] > CREATE TABLE my_first_table ( id BIGINT, name
> STRING ) DISTRIBUTE BY HASH INTO 16 BUCKETS TBLPROPERTIES( 'storage_handler'
> = 'com.cloudera.kudu.hive.KuduStorageHandler', 'kudu.table_name' =
> 'my_first_table', 'kudu.master_addresses' = '127.0.0.1:7051',
> 'kudu.key_columns' = 'id' );
>
> Query: create TABLE my_first_table ( id BIGINT, name STRING ) DISTRIBUTE BY
> HASH INTO 16 BUCKETS TBLPROPERTIES( 'storage_handler' =
> 'com.cloudera.kudu.hive.KuduStorageHandler', 'kudu.table_name' =
> 'my_first_table', 'kudu.master_addresses' = '127.0.0.1:7051',
> 'kudu.key_columns' = 'id' )
> Fetched 0 row(s) in 0.77s
>
> [localhost.localdomain:21000] > show tables;
> Query: show tables
> +----------------+
> | name |
> +----------------+
> | my_first_table |
> +----------------+
> Fetched 1 row(s) in 0.01s
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
