You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2025/03/21 11:57:00 UTC
[jira] [Updated] (HIVE-28838) Remove JDBC connection info from explain extended output
[ https://issues.apache.org/jira/browse/HIVE-28838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated HIVE-28838:
----------------------------------
Labels: pull-request-available (was: )
> Remove JDBC connection info from explain extended output
> --------------------------------------------------------
>
> Key: HIVE-28838
> URL: https://issues.apache.org/jira/browse/HIVE-28838
> Project: Hive
> Issue Type: Task
> Components: HiveServer2
> Reporter: Zsolt Miskolczi
> Assignee: Zsolt Miskolczi
> Priority: Major
> Labels: pull-request-available
>
> At the current behaviour, tables created with JdbcStorageHandler lists out the jdbc connection info in the explain extended output:
> {noformat}
> hive.sql.database.type DERBY
> hive.sql.dbcp.username APP
> hive.sql.jdbc.driver org.apache.derby.jdbc.EmbeddedDriver
> hive.sql.jdbc.url jdbc:derby:memory:junit_metastore_db;create=true
> {noformat}
> The reason is because of configureTableJobProperties adds the connection info to the input job - so that, a jdbc table can be queried.
> The goal is to remove the sensitive properties from the explain extended output.
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)