[jira] [Commented] (IMPALA-9114) TestKuduHMSIntegration failing: Kudu create table failing
[
https://issues.apache.org/jira/browse/IMPALA-9114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16964454#comment-16964454
]
Hao Hao commented on IMPALA-9114:
-
Looking at the Kudu log, it should be a test issue that somehow
TestKuduHMSIntegration ran even when the Kudu service was not running (no Kudu
log around 2019-10-31 12:46). I cannot find the log to show why this happened
as the test should only start when Kudu service has been
[restarted|https://github.com/apache/impala/blob/master/tests/common/custom_cluster_test_suite.py#L215].
Anyway, lower the priority as it should be a test issue.
> TestKuduHMSIntegration failing: Kudu create table failing
> -
>
> Key: IMPALA-9114
> URL: https://issues.apache.org/jira/browse/IMPALA-9114
> Project: IMPALA
> Issue Type: Bug
>Affects Versions: Impala 3.4.0
>Reporter: Bikramjeet Vig
>Assignee: Hao Hao
>Priority: Critical
> Labels: broken-build
>
> {noformat}
> Error Message
> ImpalaBeeswaxException: ImpalaBeeswaxException: INNER EXCEPTION: 'beeswaxd.ttypes.BeeswaxException'> MESSAGE: AnalysisException: Cannot
> analyze Kudu table 't': Error determining if Kudu's integration with the Hive
> Metastore is enabled: cannot complete before timeout:
> KuduRpc(method=getHiveMetastoreConfig, tablet=null, attempt=97,
> TimeoutTracker(timeout=18, elapsed=178723), Trace Summary(177842 ms):
> Sent(0), Received(0), Delayed(96), MasterRefresh(0), AuthRefresh(0),
> Truncated: false Delayed: (UNKNOWN, [ getHiveMetastoreConfig, 96 ]))
> Stacktrace
> custom_cluster/test_kudu.py:150: in test_create_managed_kudu_tables
> self.run_test_case('QueryTest/kudu_create', vector,
> use_db=unique_database)
> common/impala_test_suite.py:621: in run_test_case
> result = exec_fn(query, user=test_section.get('USER', '').strip() or None)
> common/impala_test_suite.py:556: in __exec_in_impala
> result = self.__execute_query(target_impalad_client, query, user=user)
> common/impala_test_suite.py:893: in __execute_query
> return impalad_client.execute(query, user=user)
> common/impala_connection.py:205: in execute
> return self.__beeswax_client.execute(sql_stmt, user=user)
> beeswax/impala_beeswax.py:187: in execute
> handle = self.__execute_query(query_string.strip(), user=user)
> beeswax/impala_beeswax.py:362: in __execute_query
> handle = self.execute_query_async(query_string, user=user)
> beeswax/impala_beeswax.py:356: in execute_query_async
> handle = self.__do_rpc(lambda: self.imp_service.query(query,))
> beeswax/impala_beeswax.py:519: in __do_rpc
> raise ImpalaBeeswaxException(self.__build_error_message(b), b)
> E ImpalaBeeswaxException: ImpalaBeeswaxException:
> EINNER EXCEPTION:
> EMESSAGE: AnalysisException: Cannot analyze Kudu table 't': Error
> determining if Kudu's integration with the Hive Metastore is enabled: cannot
> complete before timeout: KuduRpc(method=getHiveMetastoreConfig, tablet=null,
> attempt=97, TimeoutTracker(timeout=18, elapsed=178723), Trace
> Summary(177842 ms): Sent(0), Received(0), Delayed(96), MasterRefresh(0),
> AuthRefresh(0), Truncated: false
> EDelayed: (UNKNOWN, [ getHiveMetastoreConfig, 96 ]))
> Standard Output
> Stopping kudu
> Starting kudu (Web UI - http://localhost:8051)
> Standard Error
> -- 2019-10-31 12:46:18,353 INFO MainThread: Starting cluster with
> command:
> /data/jenkins/workspace/impala-asf-master-exhaustive/repos/Impala/bin/start-impala-cluster.py
> '--state_store_args=--statestore_update_frequency_ms=50
> --statestore_priority_update_frequency_ms=50
> --statestore_heartbeat_frequency_ms=50' --cluster_size=3 --num_coordinators=3
> --log_dir=/data/jenkins/workspace/impala-asf-master-exhaustive/repos/Impala/logs/custom_cluster_tests
> --log_level=1 '--impalad_args=-kudu_client_rpc_timeout_ms=3 '
> '--state_store_args=None ' --impalad_args=--default_query_options=
> 12:46:18 MainThread: Found 0 impalad/0 statestored/0 catalogd process(es)
> 12:46:18 MainThread: Starting State Store logging to
> /data/jenkins/workspace/impala-asf-master-exhaustive/repos/Impala/logs/custom_cluster_tests/statestored.INFO
> 12:46:18 MainThread: Starting Catalog Service logging to
> /data/jenkins/workspace/impala-asf-master-exhaustive/repos/Impala/logs/custom_cluster_tests/catalogd.INFO
> 12:46:18 MainThread: Starting Impala Daemon logging to
> /data/jenkins/workspace/impala-asf-master-exhaustive/repos/Impala/logs/custom_cluster_tests/impalad.INFO
> 12:46:18 MainThread: Starting Impala Daemon logging to
> /data/jenkins/workspace/impala-asf-master-exhaustive/repos/Impala/logs/custom_cluster_tests/impalad_node1.INFO
> 12:46:18 MainThread: Starting Impala Daemon logging to
>
[jira] [Updated] (IMPALA-9114) TestKuduHMSIntegration failing: Kudu create table failing
[
https://issues.apache.org/jira/browse/IMPALA-9114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Hao updated IMPALA-9114:
Priority: Minor (was: Critical)
> TestKuduHMSIntegration failing: Kudu create table failing
> -
>
> Key: IMPALA-9114
> URL: https://issues.apache.org/jira/browse/IMPALA-9114
> Project: IMPALA
> Issue Type: Bug
>Affects Versions: Impala 3.4.0
>Reporter: Bikramjeet Vig
>Assignee: Hao Hao
>Priority: Minor
> Labels: broken-build
>
> {noformat}
> Error Message
> ImpalaBeeswaxException: ImpalaBeeswaxException: INNER EXCEPTION: 'beeswaxd.ttypes.BeeswaxException'> MESSAGE: AnalysisException: Cannot
> analyze Kudu table 't': Error determining if Kudu's integration with the Hive
> Metastore is enabled: cannot complete before timeout:
> KuduRpc(method=getHiveMetastoreConfig, tablet=null, attempt=97,
> TimeoutTracker(timeout=18, elapsed=178723), Trace Summary(177842 ms):
> Sent(0), Received(0), Delayed(96), MasterRefresh(0), AuthRefresh(0),
> Truncated: false Delayed: (UNKNOWN, [ getHiveMetastoreConfig, 96 ]))
> Stacktrace
> custom_cluster/test_kudu.py:150: in test_create_managed_kudu_tables
> self.run_test_case('QueryTest/kudu_create', vector,
> use_db=unique_database)
> common/impala_test_suite.py:621: in run_test_case
> result = exec_fn(query, user=test_section.get('USER', '').strip() or None)
> common/impala_test_suite.py:556: in __exec_in_impala
> result = self.__execute_query(target_impalad_client, query, user=user)
> common/impala_test_suite.py:893: in __execute_query
> return impalad_client.execute(query, user=user)
> common/impala_connection.py:205: in execute
> return self.__beeswax_client.execute(sql_stmt, user=user)
> beeswax/impala_beeswax.py:187: in execute
> handle = self.__execute_query(query_string.strip(), user=user)
> beeswax/impala_beeswax.py:362: in __execute_query
> handle = self.execute_query_async(query_string, user=user)
> beeswax/impala_beeswax.py:356: in execute_query_async
> handle = self.__do_rpc(lambda: self.imp_service.query(query,))
> beeswax/impala_beeswax.py:519: in __do_rpc
> raise ImpalaBeeswaxException(self.__build_error_message(b), b)
> E ImpalaBeeswaxException: ImpalaBeeswaxException:
> EINNER EXCEPTION:
> EMESSAGE: AnalysisException: Cannot analyze Kudu table 't': Error
> determining if Kudu's integration with the Hive Metastore is enabled: cannot
> complete before timeout: KuduRpc(method=getHiveMetastoreConfig, tablet=null,
> attempt=97, TimeoutTracker(timeout=18, elapsed=178723), Trace
> Summary(177842 ms): Sent(0), Received(0), Delayed(96), MasterRefresh(0),
> AuthRefresh(0), Truncated: false
> EDelayed: (UNKNOWN, [ getHiveMetastoreConfig, 96 ]))
> Standard Output
> Stopping kudu
> Starting kudu (Web UI - http://localhost:8051)
> Standard Error
> -- 2019-10-31 12:46:18,353 INFO MainThread: Starting cluster with
> command:
> /data/jenkins/workspace/impala-asf-master-exhaustive/repos/Impala/bin/start-impala-cluster.py
> '--state_store_args=--statestore_update_frequency_ms=50
> --statestore_priority_update_frequency_ms=50
> --statestore_heartbeat_frequency_ms=50' --cluster_size=3 --num_coordinators=3
> --log_dir=/data/jenkins/workspace/impala-asf-master-exhaustive/repos/Impala/logs/custom_cluster_tests
> --log_level=1 '--impalad_args=-kudu_client_rpc_timeout_ms=3 '
> '--state_store_args=None ' --impalad_args=--default_query_options=
> 12:46:18 MainThread: Found 0 impalad/0 statestored/0 catalogd process(es)
> 12:46:18 MainThread: Starting State Store logging to
> /data/jenkins/workspace/impala-asf-master-exhaustive/repos/Impala/logs/custom_cluster_tests/statestored.INFO
> 12:46:18 MainThread: Starting Catalog Service logging to
> /data/jenkins/workspace/impala-asf-master-exhaustive/repos/Impala/logs/custom_cluster_tests/catalogd.INFO
> 12:46:18 MainThread: Starting Impala Daemon logging to
> /data/jenkins/workspace/impala-asf-master-exhaustive/repos/Impala/logs/custom_cluster_tests/impalad.INFO
> 12:46:18 MainThread: Starting Impala Daemon logging to
> /data/jenkins/workspace/impala-asf-master-exhaustive/repos/Impala/logs/custom_cluster_tests/impalad_node1.INFO
> 12:46:18 MainThread: Starting Impala Daemon logging to
> /data/jenkins/workspace/impala-asf-master-exhaustive/repos/Impala/logs/custom_cluster_tests/impalad_node2.INFO
> 12:46:21 MainThread: Found 3 impalad/1 statestored/1 catalogd process(es)
> 12:46:21 MainThread: Found 3 impalad/1 statestored/1 catalogd process(es)
> 12:46:21 MainThread: Getting num_known_live_backends from
> impala-ec2-centos74-m5-4xlarge-ondemand-0645.vpc.cloudera.com:25000
> 12:46:22 MainThread: Waiting for num_known_live_backends=3. Current value: 0
> 12:46:23 MainThread: Found 3 impalad/1
[jira] [Commented] (IMPALA-8856) TestKuduHMSIntegration.test_drop_managed_kudu_table failed with "the table does not exist"
[
https://issues.apache.org/jira/browse/IMPALA-8856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16906715#comment-16906715
]
Hao Hao commented on IMPALA-8856:
-
I think there are two options 1) increase the Kudu client time out config via
setting the kudu_client_rpc_timeout_ms flag; 2) catch the exception and check
if it is a 'NotFound' error. If so, then move on with the test. I am leaning
towards the first option as it is not only DeleteTable RPC can time out. Does
that sound good to you? If so, I can post a patch using the first option.
> TestKuduHMSIntegration.test_drop_managed_kudu_table failed with "the table
> does not exist"
> --
>
> Key: IMPALA-8856
> URL: https://issues.apache.org/jira/browse/IMPALA-8856
> Project: IMPALA
> Issue Type: Improvement
> Components: Catalog
>Affects Versions: Impala 3.3.0
>Reporter: Tim Armstrong
>Assignee: Hao Hao
>Priority: Blocker
> Labels: flaky
> Attachments:
> catalogd.impala-ec2-centos74-m5-4xlarge-ondemand-1188.vpc.cloudera.com.jenkins.log.INFO.20190812-144934.5595,
> hive-metastore.log,
> impalad.impala-ec2-centos74-m5-4xlarge-ondemand-1188.vpc.cloudera.com.jenkins.log.INFO.20190812-144935.5670,
>
> impalad.impala-ec2-centos74-m5-4xlarge-ondemand-1188.vpc.cloudera.com.jenkins.log.INFO.20190812-144935.5675,
>
> impalad.impala-ec2-centos74-m5-4xlarge-ondemand-1188.vpc.cloudera.com.jenkins.log.INFO.20190812-144935.5675,
>
> kudu-master.impala-ec2-centos74-m5-4xlarge-ondemand-1188.vpc.cloudera.com.jenkins.log.INFO.20190812-144746.28998,
>
> kudu-tserver.impala-ec2-centos74-m5-4xlarge-ondemand-1188.vpc.cloudera.com.jenkins.diagnostics.20190812-144746.0.28965,
>
> kudu-tserver.impala-ec2-centos74-m5-4xlarge-ondemand-1188.vpc.cloudera.com.jenkins.log.INFO.20190812-144746.28981,
>
> kudu-tserver.impala-ec2-centos74-m5-4xlarge-ondemand-1188.vpc.cloudera.com.jenkins.log.INFO.20190812-144746.29022
>
>
> {noformat}
> custom_cluster.test_kudu.TestKuduHMSIntegration.test_drop_managed_kudu_table
> (from pytest)
> Failing for the past 1 build (Since Failed#31 )
> Took 27 sec.
> add description
> Error Message
> KuduNotFound: the table does not exist: table_name:
> "test_drop_managed_kudu_table_a82c250c.foo"
> Stacktrace
> custom_cluster/test_kudu.py:256: in test_drop_managed_kudu_table
> kudu_client.delete_table(kudu_tbl_name)
> kudu/client.pyx:392: in kudu.client.Client.delete_table (kudu/client.cpp:7106)
> ???
> kudu/errors.pyx:56: in kudu.errors.check_status (kudu/errors.cpp:904)
> ???
> E KuduNotFound: the table does not exist: table_name:
> "test_drop_managed_kudu_table_a82c250c.foo"
> Standard Error
> -- 2019-08-12 14:49:32,854 INFO MainThread: Starting cluster with
> command:
> /data/jenkins/workspace/impala-asf-master-core-s3-data-cache/repos/Impala/bin/start-impala-cluster.py
> '--state_store_args=--statestore_update_frequency_ms=50
> --statestore_priority_update_frequency_ms=50
> --statestore_heartbeat_frequency_ms=50' --cluster_size=3 --num_coordinators=3
> --log_dir=/data/jenkins/workspace/impala-asf-master-core-s3-data-cache/repos/Impala/logs/custom_cluster_tests
> --log_level=1 --impalad_args=--default_query_options=
> 14:49:33 MainThread: Found 0 impalad/0 statestored/0 catalogd process(es)
> 14:49:33 MainThread: Starting State Store logging to
> /data/jenkins/workspace/impala-asf-master-core-s3-data-cache/repos/Impala/logs/custom_cluster_tests/statestored.INFO
> 14:49:34 MainThread: Starting Catalog Service logging to
> /data/jenkins/workspace/impala-asf-master-core-s3-data-cache/repos/Impala/logs/custom_cluster_tests/catalogd.INFO
> 14:49:35 MainThread: Starting Impala Daemon logging to
> /data/jenkins/workspace/impala-asf-master-core-s3-data-cache/repos/Impala/logs/custom_cluster_tests/impalad.INFO
> 14:49:35 MainThread: Starting Impala Daemon logging to
> /data/jenkins/workspace/impala-asf-master-core-s3-data-cache/repos/Impala/logs/custom_cluster_tests/impalad_node1.INFO
> 14:49:35 MainThread: Starting Impala Daemon logging to
> /data/jenkins/workspace/impala-asf-master-core-s3-data-cache/repos/Impala/logs/custom_cluster_tests/impalad_node2.INFO
> 14:49:38 MainThread: Found 3 impalad/1 statestored/1 catalogd process(es)
> 14:49:38 MainThread: Found 3 impalad/1 statestored/1 catalogd process(es)
> 14:49:38 MainThread: Getting num_known_live_backends from
> impala-ec2-centos74-m5-4xlarge-ondemand-1188.vpc.cloudera.com:25000
> 14:49:38 MainThread: Debug webpage not yet available: ('Connection aborted.',
> error(111, 'Connection refused'))
> 14:49:40 MainThread: Debug webpage did not become available in expected time.
> 14:49:40 MainThread: Waiting for num_known_live_backends=3. Current value:
> None
> 14:49:41
[jira] [Commented] (IMPALA-8856) TestKuduHMSIntegration.test_drop_managed_kudu_table failed with "the table does not exist"
[
https://issues.apache.org/jira/browse/IMPALA-8856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16906662#comment-16906662
]
Hao Hao commented on IMPALA-8856:
-
Looking at the Kudu master log, there has been two DeleteTable requests for
table "test_drop_managed_kudu_table_a82c250c.foo". Because the drop HMS table
took more than 10s to finish, the first request timed out and the client issued
a retry. The retry failed because the table has been already deleted by the
first request.
{noformat}
W0812 14:49:59.766089 29240 hms_client.cc:275] Time spent drop HMS table: real
13.625s user 0.000s sys 0.000s
W0812 14:49:59.766505 29179 rpcz_store.cc:253] Call
kudu.master.MasterService.DeleteTable from 127.0.0.1:42892 (request call id 3)
took 13631 ms (13.6 s). Client timeout ms (10 s)
{noformat}
The end result is the table has been deleted in Kudu and the HMS. And as Kudu
depends on the HMS, the client can receive 'Not Found' error even though the
table has already been deleted with a default timeout config. So I don't think
this is a blocker, rather it is a test flakiness.
> TestKuduHMSIntegration.test_drop_managed_kudu_table failed with "the table
> does not exist"
> --
>
> Key: IMPALA-8856
> URL: https://issues.apache.org/jira/browse/IMPALA-8856
> Project: IMPALA
> Issue Type: Improvement
> Components: Catalog
>Affects Versions: Impala 3.3.0
>Reporter: Tim Armstrong
>Assignee: Hao Hao
>Priority: Blocker
> Labels: flaky
> Attachments:
> catalogd.impala-ec2-centos74-m5-4xlarge-ondemand-1188.vpc.cloudera.com.jenkins.log.INFO.20190812-144934.5595,
> hive-metastore.log,
> impalad.impala-ec2-centos74-m5-4xlarge-ondemand-1188.vpc.cloudera.com.jenkins.log.INFO.20190812-144935.5670,
>
> impalad.impala-ec2-centos74-m5-4xlarge-ondemand-1188.vpc.cloudera.com.jenkins.log.INFO.20190812-144935.5675,
>
> impalad.impala-ec2-centos74-m5-4xlarge-ondemand-1188.vpc.cloudera.com.jenkins.log.INFO.20190812-144935.5675,
>
> kudu-master.impala-ec2-centos74-m5-4xlarge-ondemand-1188.vpc.cloudera.com.jenkins.log.INFO.20190812-144746.28998,
>
> kudu-tserver.impala-ec2-centos74-m5-4xlarge-ondemand-1188.vpc.cloudera.com.jenkins.diagnostics.20190812-144746.0.28965,
>
> kudu-tserver.impala-ec2-centos74-m5-4xlarge-ondemand-1188.vpc.cloudera.com.jenkins.log.INFO.20190812-144746.28981,
>
> kudu-tserver.impala-ec2-centos74-m5-4xlarge-ondemand-1188.vpc.cloudera.com.jenkins.log.INFO.20190812-144746.29022
>
>
> {noformat}
> custom_cluster.test_kudu.TestKuduHMSIntegration.test_drop_managed_kudu_table
> (from pytest)
> Failing for the past 1 build (Since Failed#31 )
> Took 27 sec.
> add description
> Error Message
> KuduNotFound: the table does not exist: table_name:
> "test_drop_managed_kudu_table_a82c250c.foo"
> Stacktrace
> custom_cluster/test_kudu.py:256: in test_drop_managed_kudu_table
> kudu_client.delete_table(kudu_tbl_name)
> kudu/client.pyx:392: in kudu.client.Client.delete_table (kudu/client.cpp:7106)
> ???
> kudu/errors.pyx:56: in kudu.errors.check_status (kudu/errors.cpp:904)
> ???
> E KuduNotFound: the table does not exist: table_name:
> "test_drop_managed_kudu_table_a82c250c.foo"
> Standard Error
> -- 2019-08-12 14:49:32,854 INFO MainThread: Starting cluster with
> command:
> /data/jenkins/workspace/impala-asf-master-core-s3-data-cache/repos/Impala/bin/start-impala-cluster.py
> '--state_store_args=--statestore_update_frequency_ms=50
> --statestore_priority_update_frequency_ms=50
> --statestore_heartbeat_frequency_ms=50' --cluster_size=3 --num_coordinators=3
> --log_dir=/data/jenkins/workspace/impala-asf-master-core-s3-data-cache/repos/Impala/logs/custom_cluster_tests
> --log_level=1 --impalad_args=--default_query_options=
> 14:49:33 MainThread: Found 0 impalad/0 statestored/0 catalogd process(es)
> 14:49:33 MainThread: Starting State Store logging to
> /data/jenkins/workspace/impala-asf-master-core-s3-data-cache/repos/Impala/logs/custom_cluster_tests/statestored.INFO
> 14:49:34 MainThread: Starting Catalog Service logging to
> /data/jenkins/workspace/impala-asf-master-core-s3-data-cache/repos/Impala/logs/custom_cluster_tests/catalogd.INFO
> 14:49:35 MainThread: Starting Impala Daemon logging to
> /data/jenkins/workspace/impala-asf-master-core-s3-data-cache/repos/Impala/logs/custom_cluster_tests/impalad.INFO
> 14:49:35 MainThread: Starting Impala Daemon logging to
> /data/jenkins/workspace/impala-asf-master-core-s3-data-cache/repos/Impala/logs/custom_cluster_tests/impalad_node1.INFO
> 14:49:35 MainThread: Starting Impala Daemon logging to
> /data/jenkins/workspace/impala-asf-master-core-s3-data-cache/repos/Impala/logs/custom_cluster_tests/impalad_node2.INFO
> 14:49:38 MainThread: Found 3
[jira] [Resolved] (IMPALA-8629) Adjust new KuduStorageHandler package
[
https://issues.apache.org/jira/browse/IMPALA-8629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Hao resolved IMPALA-8629.
-
Resolution: Fixed
Fix Version/s: Impala 3.3.0
> Adjust new KuduStorageHandler package
> -
>
> Key: IMPALA-8629
> URL: https://issues.apache.org/jira/browse/IMPALA-8629
> Project: IMPALA
> Issue Type: Sub-task
> Components: Catalog, Frontend
>Reporter: Grant Henke
>Assignee: Grant Henke
>Priority: Major
> Fix For: Impala 3.3.0
>
>
> Before releasing with the updated KuduStorageHandler, we should change the
> new KuduStorageHandler package from “org.apache.kudu.hive” to
> “org.apache.hadoop.hive.kudu”.
>
> This should being done to ensure the stand-in storage handler can be a real
> storage handler when a Hive integration is added in the future. The
> “org.apache.hadoop.hive” package is the standard package all Hive storage
> handlers lives under.
>
> Additionally the stand-in format details defined
> [here|https://github.com/apache/impala/blob/2bce974990e19788ec359deec50f06d44ec92048/fe/src/main/java/org/apache/impala/catalog/HdfsFileFormat.java#L70]
> should be updated as well. Values for those entries should be:
> {noformat}
> org.apache.hadoop.hive.kudu.KuduInputFormat
> org.apache.hadoop.hive.kudu.KuduOutputFormat
> org.apache.hadoop.hive.kudu.KuduSerDe
> {noformat}
>
> I have a WIP patch for HIVE-12971 and used that patch to validate that using
> "correct" stand-in values would allow Hive to read HMS tables/entries created
> by Impala.
>
> Note: This patch will need to be committed after the Kudu side patch is
> committed and the Kudu build/version may need to be update in Impala. A
> review for the Kudu side change is here:
> [https://gerrit.cloudera.org/#/c/13540/]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Resolved] (IMPALA-8502) Improve Kudu/Impala integration based on Kudu/HMS/Sentry integration
[ https://issues.apache.org/jira/browse/IMPALA-8502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao resolved IMPALA-8502. - Resolution: Fixed > Improve Kudu/Impala integration based on Kudu/HMS/Sentry integration > > > Key: IMPALA-8502 > URL: https://issues.apache.org/jira/browse/IMPALA-8502 > Project: IMPALA > Issue Type: New Feature > Components: Catalog, Frontend >Reporter: Hao Hao >Assignee: Hao Hao >Priority: Major > Fix For: Impala 3.3.0 > > > This is an umbrella JIRA to correspond to the [design > doc|https://docs.google.com/document/d/1HBEGEkrkHSd6h4qQ7O1nfySad9Hzyujf3_dYi5_M6eA/edit?usp=sharing] > that proposes to adapt Kudu/Impala integration accordingly with Kudu’s > integration with the HMS and Sentry. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IMPALA-8629) Adjust new KuduStorageHandler package
[
https://issues.apache.org/jira/browse/IMPALA-8629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Hao resolved IMPALA-8629.
-
Resolution: Fixed
Fix Version/s: Impala 3.3.0
> Adjust new KuduStorageHandler package
> -
>
> Key: IMPALA-8629
> URL: https://issues.apache.org/jira/browse/IMPALA-8629
> Project: IMPALA
> Issue Type: Sub-task
> Components: Catalog, Frontend
>Reporter: Grant Henke
>Assignee: Grant Henke
>Priority: Major
> Fix For: Impala 3.3.0
>
>
> Before releasing with the updated KuduStorageHandler, we should change the
> new KuduStorageHandler package from “org.apache.kudu.hive” to
> “org.apache.hadoop.hive.kudu”.
>
> This should being done to ensure the stand-in storage handler can be a real
> storage handler when a Hive integration is added in the future. The
> “org.apache.hadoop.hive” package is the standard package all Hive storage
> handlers lives under.
>
> Additionally the stand-in format details defined
> [here|https://github.com/apache/impala/blob/2bce974990e19788ec359deec50f06d44ec92048/fe/src/main/java/org/apache/impala/catalog/HdfsFileFormat.java#L70]
> should be updated as well. Values for those entries should be:
> {noformat}
> org.apache.hadoop.hive.kudu.KuduInputFormat
> org.apache.hadoop.hive.kudu.KuduOutputFormat
> org.apache.hadoop.hive.kudu.KuduSerDe
> {noformat}
>
> I have a WIP patch for HIVE-12971 and used that patch to validate that using
> "correct" stand-in values would allow Hive to read HMS tables/entries created
> by Impala.
>
> Note: This patch will need to be committed after the Kudu side patch is
> committed and the Kudu build/version may need to be update in Impala. A
> review for the Kudu side change is here:
> [https://gerrit.cloudera.org/#/c/13540/]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IMPALA-8678) ToSqlTest falures on S3 (from org.apache.impala.customservice.KuduHMSIntegrationTest
[
https://issues.apache.org/jira/browse/IMPALA-8678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16867878#comment-16867878
]
Hao Hao commented on IMPALA-8678:
-
Hmm, this is weird, because these tests are not supposed to run on S3 and
should be disabled
(https://github.com/apache/impala/blob/master/bin/run-all-tests.sh#L249). Were
you using the latest master?
> ToSqlTest falures on S3 (from
> org.apache.impala.customservice.KuduHMSIntegrationTest
>
>
> Key: IMPALA-8678
> URL: https://issues.apache.org/jira/browse/IMPALA-8678
> Project: IMPALA
> Issue Type: Bug
>Reporter: Andrew Sherman
>Assignee: Hao Hao
>Priority: Critical
>
> On S3 tests we get failures in
> org.apache.impala.analysis.ToSqlTest.TestCreateTableLikeFile (from
> org.apache.impala.customservice.KuduHMSIntegrationTest)
> org.apache.impala.analysis.ToSqlTest.alterTableAddPartitionTest (from
> org.apache.impala.customservice.KuduHMSIntegrationTest)
> {code}
> org.junit.ComparisonFailure: expected:<... month=2) LOCATION
> '[hdfs://localhost:20500]/y2050m2'> but was:<... month=2) LOCATION
> '[s3a://impala-test-uswest2-2]/y2050m2'>
> at org.junit.Assert.assertEquals(Assert.java:115)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at org.apache.impala.analysis.ToSqlTest.testToSql(ToSqlTest.java:123)
> at org.apache.impala.analysis.ToSqlTest.testToSql(ToSqlTest.java:105)
> at org.apache.impala.analysis.ToSqlTest.testToSql(ToSqlTest.java:95)
> at org.apache.impala.analysis.ToSqlTest.testToSql(ToSqlTest.java:82)
> at
> org.apache.impala.analysis.ToSqlTest.alterTableAddPartitionTest(ToSqlTest.java:1269)
> {code}
> {code}
> org.junit.ComparisonFailure: expected:<...ult.p LIKE PARQUET
> '[hdfs://localhost:20500]/test-warehouse/sche...> but was:<...ult.p LIKE
> PARQUET '[s3a://impala-test-uswest2-2]/test-warehouse/sche...>
> at org.junit.Assert.assertEquals(Assert.java:115)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at org.apache.impala.analysis.ToSqlTest.testToSql(ToSqlTest.java:123)
> at org.apache.impala.analysis.ToSqlTest.testToSql(ToSqlTest.java:105)
> at
> org.apache.impala.analysis.ToSqlTest.TestCreateTableLikeFile(ToSqlTest.java:386)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Resolved] (IMPALA-8507) Support DropTable DDL with Kudu/HMS integration in Catalogd mode
[ https://issues.apache.org/jira/browse/IMPALA-8507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao resolved IMPALA-8507. - Resolution: Fixed Fix Version/s: Impala 3.3.0 > Support DropTable DDL with Kudu/HMS integration in Catalogd mode > > > Key: IMPALA-8507 > URL: https://issues.apache.org/jira/browse/IMPALA-8507 > Project: IMPALA > Issue Type: Sub-task >Reporter: Hao Hao >Assignee: Hao Hao >Priority: Major > Fix For: Impala 3.3.0 > > > Similar to IMPALA-8504, but for DropTable DDL. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Resolved] (IMPALA-8507) Support DropTable DDL with Kudu/HMS integration in Catalogd mode
[ https://issues.apache.org/jira/browse/IMPALA-8507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao resolved IMPALA-8507. - Resolution: Fixed Fix Version/s: Impala 3.3.0 > Support DropTable DDL with Kudu/HMS integration in Catalogd mode > > > Key: IMPALA-8507 > URL: https://issues.apache.org/jira/browse/IMPALA-8507 > Project: IMPALA > Issue Type: Sub-task >Reporter: Hao Hao >Assignee: Hao Hao >Priority: Major > Fix For: Impala 3.3.0 > > > Similar to IMPALA-8504, but for DropTable DDL. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IMPALA-8502) Improve Kudu/Impala integration based on Kudu/HMS/Sentry integration
[ https://issues.apache.org/jira/browse/IMPALA-8502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao resolved IMPALA-8502. - Resolution: Fixed Assignee: Hao Hao Fix Version/s: Impala 3.3.0 > Improve Kudu/Impala integration based on Kudu/HMS/Sentry integration > > > Key: IMPALA-8502 > URL: https://issues.apache.org/jira/browse/IMPALA-8502 > Project: IMPALA > Issue Type: New Feature > Components: Catalog, Frontend >Reporter: Hao Hao >Assignee: Hao Hao >Priority: Major > Fix For: Impala 3.3.0 > > > This is an umbrella JIRA to correspond to the [design > doc|https://docs.google.com/document/d/1HBEGEkrkHSd6h4qQ7O1nfySad9Hzyujf3_dYi5_M6eA/edit?usp=sharing] > that proposes to adapt Kudu/Impala integration accordingly with Kudu’s > integration with the HMS and Sentry. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IMPALA-8506) Support RenameTable DDL with Kudu/HMS integration in Catalogd mode
[ https://issues.apache.org/jira/browse/IMPALA-8506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao resolved IMPALA-8506. - Resolution: Fixed Fix Version/s: Impala 3.3.0 > Support RenameTable DDL with Kudu/HMS integration in Catalogd mode > -- > > Key: IMPALA-8506 > URL: https://issues.apache.org/jira/browse/IMPALA-8506 > Project: IMPALA > Issue Type: Sub-task >Reporter: Hao Hao >Assignee: Hao Hao >Priority: Major > Fix For: Impala 3.3.0 > > > Similar to IMPALA-8504, but for RenameTable DDL. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Resolved] (IMPALA-8505) Support AlterTable DDL with Kudu/HMS integration in Catalogd mode
[ https://issues.apache.org/jira/browse/IMPALA-8505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao resolved IMPALA-8505. - Resolution: Fixed Fix Version/s: Impala 3.3.0 > Support AlterTable DDL with Kudu/HMS integration in Catalogd mode > - > > Key: IMPALA-8505 > URL: https://issues.apache.org/jira/browse/IMPALA-8505 > Project: IMPALA > Issue Type: Sub-task >Reporter: Hao Hao >Assignee: Hao Hao >Priority: Major > Fix For: Impala 3.3.0 > > > Similar to IMPALA-8504, but for AlterTable DDL. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Resolved] (IMPALA-8502) Improve Kudu/Impala integration based on Kudu/HMS/Sentry integration
[ https://issues.apache.org/jira/browse/IMPALA-8502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao resolved IMPALA-8502. - Resolution: Fixed Assignee: Hao Hao Fix Version/s: Impala 3.3.0 > Improve Kudu/Impala integration based on Kudu/HMS/Sentry integration > > > Key: IMPALA-8502 > URL: https://issues.apache.org/jira/browse/IMPALA-8502 > Project: IMPALA > Issue Type: New Feature > Components: Catalog, Frontend >Reporter: Hao Hao >Assignee: Hao Hao >Priority: Major > Fix For: Impala 3.3.0 > > > This is an umbrella JIRA to correspond to the [design > doc|https://docs.google.com/document/d/1HBEGEkrkHSd6h4qQ7O1nfySad9Hzyujf3_dYi5_M6eA/edit?usp=sharing] > that proposes to adapt Kudu/Impala integration accordingly with Kudu’s > integration with the HMS and Sentry. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Reopened] (IMPALA-8502) Improve Kudu/Impala integration based on Kudu/HMS/Sentry integration
[ https://issues.apache.org/jira/browse/IMPALA-8502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao reopened IMPALA-8502: - > Improve Kudu/Impala integration based on Kudu/HMS/Sentry integration > > > Key: IMPALA-8502 > URL: https://issues.apache.org/jira/browse/IMPALA-8502 > Project: IMPALA > Issue Type: New Feature > Components: Catalog, Frontend >Reporter: Hao Hao >Assignee: Hao Hao >Priority: Major > Fix For: Impala 3.3.0 > > > This is an umbrella JIRA to correspond to the [design > doc|https://docs.google.com/document/d/1HBEGEkrkHSd6h4qQ7O1nfySad9Hzyujf3_dYi5_M6eA/edit?usp=sharing] > that proposes to adapt Kudu/Impala integration accordingly with Kudu’s > integration with the HMS and Sentry. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Resolved] (IMPALA-8505) Support AlterTable DDL with Kudu/HMS integration in Catalogd mode
[ https://issues.apache.org/jira/browse/IMPALA-8505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao resolved IMPALA-8505. - Resolution: Fixed Fix Version/s: Impala 3.3.0 > Support AlterTable DDL with Kudu/HMS integration in Catalogd mode > - > > Key: IMPALA-8505 > URL: https://issues.apache.org/jira/browse/IMPALA-8505 > Project: IMPALA > Issue Type: Sub-task >Reporter: Hao Hao >Assignee: Hao Hao >Priority: Major > Fix For: Impala 3.3.0 > > > Similar to IMPALA-8504, but for AlterTable DDL. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IMPALA-8506) Support RenameTable DDL with Kudu/HMS integration in Catalogd mode
[ https://issues.apache.org/jira/browse/IMPALA-8506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao resolved IMPALA-8506. - Resolution: Fixed Fix Version/s: Impala 3.3.0 > Support RenameTable DDL with Kudu/HMS integration in Catalogd mode > -- > > Key: IMPALA-8506 > URL: https://issues.apache.org/jira/browse/IMPALA-8506 > Project: IMPALA > Issue Type: Sub-task >Reporter: Hao Hao >Assignee: Hao Hao >Priority: Major > Fix For: Impala 3.3.0 > > > Similar to IMPALA-8504, but for RenameTable DDL. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IMPALA-8503) Add option to allow Kudu cluster to start with HMS integration
[ https://issues.apache.org/jira/browse/IMPALA-8503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao resolved IMPALA-8503. - Resolution: Fixed Fix Version/s: Impala 3.3.0 > Add option to allow Kudu cluster to start with HMS integration > -- > > Key: IMPALA-8503 > URL: https://issues.apache.org/jira/browse/IMPALA-8503 > Project: IMPALA > Issue Type: Sub-task >Reporter: Hao Hao >Assignee: Hao Hao >Priority: Major > Fix For: Impala 3.3.0 > > > Currently static template configuration under testdata/cluster/ is used to > control Kudu gflags when starting a Kudu cluster. An option to allow custom > configuration such as enabling HMS integration is needed to allow tests to > run with Kudu clusters with different set of configurations. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IMPALA-8503) Add option to allow Kudu cluster to start with HMS integration
[ https://issues.apache.org/jira/browse/IMPALA-8503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao resolved IMPALA-8503. - Resolution: Fixed Fix Version/s: Impala 3.3.0 > Add option to allow Kudu cluster to start with HMS integration > -- > > Key: IMPALA-8503 > URL: https://issues.apache.org/jira/browse/IMPALA-8503 > Project: IMPALA > Issue Type: Sub-task >Reporter: Hao Hao >Assignee: Hao Hao >Priority: Major > Fix For: Impala 3.3.0 > > > Currently static template configuration under testdata/cluster/ is used to > control Kudu gflags when starting a Kudu cluster. An option to allow custom > configuration such as enabling HMS integration is needed to allow tests to > run with Kudu clusters with different set of configurations. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Resolved] (IMPALA-8504) Support CreateTable DDL with Kudu/HMS integration in Catalogd mode
[ https://issues.apache.org/jira/browse/IMPALA-8504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao resolved IMPALA-8504. - Resolution: Fixed Fix Version/s: Impala 3.3.0 > Support CreateTable DDL with Kudu/HMS integration in Catalogd mode > -- > > Key: IMPALA-8504 > URL: https://issues.apache.org/jira/browse/IMPALA-8504 > Project: IMPALA > Issue Type: Sub-task >Reporter: Hao Hao >Assignee: Hao Hao >Priority: Major > Fix For: Impala 3.3.0 > > > For both managed and external table, we need to ensure the syntax is correct > and Kudu related table creation DDL is adapted when Kudu/HMS integration is > enabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Created] (IMPALA-8618) Handle alter table name property for Kudu managed table
Hao Hao created IMPALA-8618: --- Summary: Handle alter table name property for Kudu managed table Key: IMPALA-8618 URL: https://issues.apache.org/jira/browse/IMPALA-8618 Project: IMPALA Issue Type: Improvement Reporter: Hao Hao Since IMPALA-IMPALA-5654, altering table name property for managed table should be disallowed. However, it looks like the code in [CatalogOpExecutor.java|https://github.com/apache/impala/blob/master/fe/src/main/java/org/apache/impala/service/CatalogOpExecutor.java#L2749] should be updated to handle such scenario as well (e.g throw exception) . -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Created] (IMPALA-8618) Handle alter table name property for Kudu managed table
Hao Hao created IMPALA-8618: --- Summary: Handle alter table name property for Kudu managed table Key: IMPALA-8618 URL: https://issues.apache.org/jira/browse/IMPALA-8618 Project: IMPALA Issue Type: Improvement Reporter: Hao Hao Since IMPALA-IMPALA-5654, altering table name property for managed table should be disallowed. However, it looks like the code in [CatalogOpExecutor.java|https://github.com/apache/impala/blob/master/fe/src/main/java/org/apache/impala/service/CatalogOpExecutor.java#L2749] should be updated to handle such scenario as well (e.g throw exception) . -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IMPALA-8614) Parameterize query_test/test_kudu.py to run with/without HMS integration enabled
Hao Hao created IMPALA-8614: --- Summary: Parameterize query_test/test_kudu.py to run with/without HMS integration enabled Key: IMPALA-8614 URL: https://issues.apache.org/jira/browse/IMPALA-8614 Project: IMPALA Issue Type: Test Reporter: Hao Hao Certain query_test/test_kudu.py can be parameterized to run with/without HMS integration enabled to improve test coverage. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IMPALA-8614) Parameterize query_test/test_kudu.py to run with/without HMS integration enabled
Hao Hao created IMPALA-8614: --- Summary: Parameterize query_test/test_kudu.py to run with/without HMS integration enabled Key: IMPALA-8614 URL: https://issues.apache.org/jira/browse/IMPALA-8614 Project: IMPALA Issue Type: Test Reporter: Hao Hao Certain query_test/test_kudu.py can be parameterized to run with/without HMS integration enabled to improve test coverage. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Work started] (IMPALA-8506) Support RenameTable DDL with Kudu/HMS integration in Catalogd mode
[ https://issues.apache.org/jira/browse/IMPALA-8506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-8506 started by Hao Hao. --- > Support RenameTable DDL with Kudu/HMS integration in Catalogd mode > -- > > Key: IMPALA-8506 > URL: https://issues.apache.org/jira/browse/IMPALA-8506 > Project: IMPALA > Issue Type: Sub-task >Reporter: Hao Hao >Assignee: Hao Hao >Priority: Major > > Similar to IMPALA-8504, but for RenameTable DDL. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Work started] (IMPALA-8505) Support AlterTable DDL with Kudu/HMS integration in Catalogd mode
[ https://issues.apache.org/jira/browse/IMPALA-8505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-8505 started by Hao Hao. --- > Support AlterTable DDL with Kudu/HMS integration in Catalogd mode > - > > Key: IMPALA-8505 > URL: https://issues.apache.org/jira/browse/IMPALA-8505 > Project: IMPALA > Issue Type: Sub-task >Reporter: Hao Hao >Assignee: Hao Hao >Priority: Major > > Similar to IMPALA-8504, but for AlterTable DDL. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Work started] (IMPALA-8507) Support DropTable DDL with Kudu/HMS integration in Catalogd mode
[ https://issues.apache.org/jira/browse/IMPALA-8507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-8507 started by Hao Hao. --- > Support DropTable DDL with Kudu/HMS integration in Catalogd mode > > > Key: IMPALA-8507 > URL: https://issues.apache.org/jira/browse/IMPALA-8507 > Project: IMPALA > Issue Type: Sub-task >Reporter: Hao Hao >Assignee: Hao Hao >Priority: Major > > Similar to IMPALA-8504, but for DropTable DDL. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Work started] (IMPALA-8504) Support CreateTable DDL with Kudu/HMS integration in Catalogd mode
[ https://issues.apache.org/jira/browse/IMPALA-8504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-8504 started by Hao Hao. --- > Support CreateTable DDL with Kudu/HMS integration in Catalogd mode > -- > > Key: IMPALA-8504 > URL: https://issues.apache.org/jira/browse/IMPALA-8504 > Project: IMPALA > Issue Type: Sub-task >Reporter: Hao Hao >Assignee: Hao Hao >Priority: Major > > For both managed and external table, we need to ensure the syntax is correct > and Kudu related table creation DDL is adapted when Kudu/HMS integration is > enabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Assigned] (IMPALA-8504) Support CreateTable DDL with Kudu/HMS integration in Catalogd mode
[ https://issues.apache.org/jira/browse/IMPALA-8504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao reassigned IMPALA-8504: --- Assignee: Hao Hao > Support CreateTable DDL with Kudu/HMS integration in Catalogd mode > -- > > Key: IMPALA-8504 > URL: https://issues.apache.org/jira/browse/IMPALA-8504 > Project: IMPALA > Issue Type: Sub-task >Reporter: Hao Hao >Assignee: Hao Hao >Priority: Major > > For both managed and external table, we need to ensure the syntax is correct > and Kudu related table creation DDL is adapted when Kudu/HMS integration is > enabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Work started] (IMPALA-8503) Add option to allow Kudu cluster to start with HMS integration
[ https://issues.apache.org/jira/browse/IMPALA-8503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IMPALA-8503 started by Hao Hao. --- > Add option to allow Kudu cluster to start with HMS integration > -- > > Key: IMPALA-8503 > URL: https://issues.apache.org/jira/browse/IMPALA-8503 > Project: IMPALA > Issue Type: Sub-task >Reporter: Hao Hao >Assignee: Hao Hao >Priority: Major > > Currently static template configuration under testdata/cluster/ is used to > control Kudu gflags when starting a Kudu cluster. An option to allow custom > configuration such as enabling HMS integration is needed to allow tests to > run with Kudu clusters with different set of configurations. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Assigned] (IMPALA-8503) Add option to allow Kudu cluster to start with HMS integration
[ https://issues.apache.org/jira/browse/IMPALA-8503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao reassigned IMPALA-8503: --- Assignee: Hao Hao > Add option to allow Kudu cluster to start with HMS integration > -- > > Key: IMPALA-8503 > URL: https://issues.apache.org/jira/browse/IMPALA-8503 > Project: IMPALA > Issue Type: Sub-task >Reporter: Hao Hao >Assignee: Hao Hao >Priority: Major > > Currently static template configuration under testdata/cluster/ is used to > control Kudu gflags when starting a Kudu cluster. An option to allow custom > configuration such as enabling HMS integration is needed to allow tests to > run with Kudu clusters with different set of configurations. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Created] (IMPALA-8506) Support RenameTable DDL with Kudu/HMS integration in Catalogd mode
Hao Hao created IMPALA-8506: --- Summary: Support RenameTable DDL with Kudu/HMS integration in Catalogd mode Key: IMPALA-8506 URL: https://issues.apache.org/jira/browse/IMPALA-8506 Project: IMPALA Issue Type: Sub-task Reporter: Hao Hao Similar to IMPALA-8504, but for RenameTable DDL. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Created] (IMPALA-8506) Support RenameTable DDL with Kudu/HMS integration in Catalogd mode
Hao Hao created IMPALA-8506: --- Summary: Support RenameTable DDL with Kudu/HMS integration in Catalogd mode Key: IMPALA-8506 URL: https://issues.apache.org/jira/browse/IMPALA-8506 Project: IMPALA Issue Type: Sub-task Reporter: Hao Hao Similar to IMPALA-8504, but for RenameTable DDL. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IMPALA-8507) Support DropTable DDL with Kudu/HMS integration in Catalogd mode
Hao Hao created IMPALA-8507: --- Summary: Support DropTable DDL with Kudu/HMS integration in Catalogd mode Key: IMPALA-8507 URL: https://issues.apache.org/jira/browse/IMPALA-8507 Project: IMPALA Issue Type: Sub-task Reporter: Hao Hao Similar to IMPALA-8504, but for DropTable DDL. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Created] (IMPALA-8507) Support DropTable DDL with Kudu/HMS integration in Catalogd mode
Hao Hao created IMPALA-8507: --- Summary: Support DropTable DDL with Kudu/HMS integration in Catalogd mode Key: IMPALA-8507 URL: https://issues.apache.org/jira/browse/IMPALA-8507 Project: IMPALA Issue Type: Sub-task Reporter: Hao Hao Similar to IMPALA-8504, but for DropTable DDL. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IMPALA-8505) Support AlterTable DDL with Kudu/HMS integration in Catalogd mode
Hao Hao created IMPALA-8505: --- Summary: Support AlterTable DDL with Kudu/HMS integration in Catalogd mode Key: IMPALA-8505 URL: https://issues.apache.org/jira/browse/IMPALA-8505 Project: IMPALA Issue Type: Sub-task Reporter: Hao Hao Similar to IMPALA-8504, but for AlterTable DDL. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Created] (IMPALA-8505) Support AlterTable DDL with Kudu/HMS integration in Catalogd mode
Hao Hao created IMPALA-8505: --- Summary: Support AlterTable DDL with Kudu/HMS integration in Catalogd mode Key: IMPALA-8505 URL: https://issues.apache.org/jira/browse/IMPALA-8505 Project: IMPALA Issue Type: Sub-task Reporter: Hao Hao Similar to IMPALA-8504, but for AlterTable DDL. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IMPALA-8504) Support CreateTable DDL with Kudu/HMS integration in Catalogd mode
Hao Hao created IMPALA-8504: --- Summary: Support CreateTable DDL with Kudu/HMS integration in Catalogd mode Key: IMPALA-8504 URL: https://issues.apache.org/jira/browse/IMPALA-8504 Project: IMPALA Issue Type: Sub-task Reporter: Hao Hao For both managed and external table, we need to ensure the syntax is correct and Kudu related table creation DDL is adapted when Kudu/HMS integration is enabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Created] (IMPALA-8504) Support CreateTable DDL with Kudu/HMS integration in Catalogd mode
Hao Hao created IMPALA-8504: --- Summary: Support CreateTable DDL with Kudu/HMS integration in Catalogd mode Key: IMPALA-8504 URL: https://issues.apache.org/jira/browse/IMPALA-8504 Project: IMPALA Issue Type: Sub-task Reporter: Hao Hao For both managed and external table, we need to ensure the syntax is correct and Kudu related table creation DDL is adapted when Kudu/HMS integration is enabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IMPALA-8503) Add option to allow Kudu cluster to start with HMS integration
Hao Hao created IMPALA-8503: --- Summary: Add option to allow Kudu cluster to start with HMS integration Key: IMPALA-8503 URL: https://issues.apache.org/jira/browse/IMPALA-8503 Project: IMPALA Issue Type: Sub-task Reporter: Hao Hao Currently static template configuration under testdata/cluster/ is used to control Kudu gflags when starting a Kudu cluster. An option to allow custom configuration such as enabling HMS integration is needed to allow tests to run with Kudu clusters with different set of configurations. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Created] (IMPALA-8503) Add option to allow Kudu cluster to start with HMS integration
Hao Hao created IMPALA-8503: --- Summary: Add option to allow Kudu cluster to start with HMS integration Key: IMPALA-8503 URL: https://issues.apache.org/jira/browse/IMPALA-8503 Project: IMPALA Issue Type: Sub-task Reporter: Hao Hao Currently static template configuration under testdata/cluster/ is used to control Kudu gflags when starting a Kudu cluster. An option to allow custom configuration such as enabling HMS integration is needed to allow tests to run with Kudu clusters with different set of configurations. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IMPALA-8502) Improve Kudu/Impala integration based on Kudu/HMS/Sentry integration
Hao Hao created IMPALA-8502: --- Summary: Improve Kudu/Impala integration based on Kudu/HMS/Sentry integration Key: IMPALA-8502 URL: https://issues.apache.org/jira/browse/IMPALA-8502 Project: IMPALA Issue Type: New Feature Components: Catalog, Frontend Reporter: Hao Hao This is an umbrella JIRA to correspond to the [design doc|https://docs.google.com/document/d/1HBEGEkrkHSd6h4qQ7O1nfySad9Hzyujf3_dYi5_M6eA/edit?usp=sharing] that proposes to adapt Kudu/Impala integration accordingly with Kudu’s integration with the HMS and Sentry. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IMPALA-8502) Improve Kudu/Impala integration based on Kudu/HMS/Sentry integration
Hao Hao created IMPALA-8502: --- Summary: Improve Kudu/Impala integration based on Kudu/HMS/Sentry integration Key: IMPALA-8502 URL: https://issues.apache.org/jira/browse/IMPALA-8502 Project: IMPALA Issue Type: New Feature Components: Catalog, Frontend Reporter: Hao Hao This is an umbrella JIRA to correspond to the [design doc|https://docs.google.com/document/d/1HBEGEkrkHSd6h4qQ7O1nfySad9Hzyujf3_dYi5_M6eA/edit?usp=sharing] that proposes to adapt Kudu/Impala integration accordingly with Kudu’s integration with the HMS and Sentry. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
