You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2019/09/19 17:31:00 UTC
[jira] [Commented] (IMPALA-8559) Support config validation for
event processor on HMS-3
[ https://issues.apache.org/jira/browse/IMPALA-8559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16933613#comment-16933613 ]
ASF subversion and git services commented on IMPALA-8559:
---------------------------------------------------------
Commit b2e5e942867ee1eeca754fd383075e7db3c8b590 in impala's branch refs/heads/master from Anurag Mantripragada
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=b2e5e94 ]
IMPALA-8761: Improve events processor configuration validation.
This patch aims to improve the validation of configuration keys
from the HMS.
IMPALA-8559 introduced configuration validation for events processor
configurations. In the existing implementation, the events processor
errors out as soon as it sees a validation failure. If there are
more than one configuration errors, the users may have to restart
HMS each time they fix a configuration error. This is bad user
experience. This change collects all the configuration issues and
logs expected values before erroring out. Users can now fix all
issues in one go.
Testing:
Added testValidateConfigs() to assert if multiple incorrect values
are detected at once.
Change-Id: I73480872ef93215d05c1fd922e64eb68a8a63a42
Reviewed-on: http://gerrit.cloudera.org:8080/14240
Reviewed-by: Bharath Vissapragada <bh...@cloudera.com>
Tested-by: Impala Public Jenkins <im...@cloudera.com>
> Support config validation for event processor on HMS-3
> ------------------------------------------------------
>
> Key: IMPALA-8559
> URL: https://issues.apache.org/jira/browse/IMPALA-8559
> Project: IMPALA
> Issue Type: Sub-task
> Reporter: Vihang Karajgaonkar
> Assignee: Vihang Karajgaonkar
> Priority: Major
> Fix For: Impala 3.3.0
>
>
> HMS-3 does not need certain configuration validations which are currently added to {{EventProcessorConfigValidation}}. We should use the metastore shim to select the ones which are interesting when running against HMS-3.
> Also, it looks like HMS-3 adds authorization against the notification API so we should include {{hive.metastore.event.db.notification.api.auth}} to {{false}} to the mini-cluster hive-site.xml.
--
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