[jira] [Updated] (HIVE-3277) Enable Metastore audit logging for non-secure connections
[ https://issues.apache.org/jira/browse/HIVE-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HIVE-3277: Attachment: HIVE-3277.patch > Enable Metastore audit logging for non-secure connections > - > > Key: HIVE-3277 > URL: https://issues.apache.org/jira/browse/HIVE-3277 > Project: Hive > Issue Type: Improvement > Components: Logging, Metastore, Security >Reporter: Carl Steinbach > Attachments: HIVE-3277.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3277) Enable Metastore audit logging for non-secure connections
[ https://issues.apache.org/jira/browse/HIVE-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HIVE-3277: Status: Patch Available (was: Open) This patch uses the alternative method of determining the IP address in the event that there is no SASL connection. I've tested this out on a pseudo-distributed Hadoop cluster and audit logging worked. > Enable Metastore audit logging for non-secure connections > - > > Key: HIVE-3277 > URL: https://issues.apache.org/jira/browse/HIVE-3277 > Project: Hive > Issue Type: Improvement > Components: Logging, Metastore, Security >Reporter: Carl Steinbach > Attachments: HIVE-3277.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3277) Enable Metastore audit logging for non-secure connections
[ https://issues.apache.org/jira/browse/HIVE-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HIVE-3277: Attachment: (was: HIVE-3277.patch) > Enable Metastore audit logging for non-secure connections > - > > Key: HIVE-3277 > URL: https://issues.apache.org/jira/browse/HIVE-3277 > Project: Hive > Issue Type: Improvement > Components: Logging, Metastore, Security >Reporter: Carl Steinbach >Assignee: Sean Mackrory > Attachments: HIVE-3277.patch.1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3277) Enable Metastore audit logging for non-secure connections
[ https://issues.apache.org/jira/browse/HIVE-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HIVE-3277: Attachment: HIVE-3277.patch.1 My apologies - original patch was malformed. > Enable Metastore audit logging for non-secure connections > - > > Key: HIVE-3277 > URL: https://issues.apache.org/jira/browse/HIVE-3277 > Project: Hive > Issue Type: Improvement > Components: Logging, Metastore, Security >Reporter: Carl Steinbach >Assignee: Sean Mackrory > Attachments: HIVE-3277.patch.1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3277) Enable Metastore audit logging for non-secure connections
[ https://issues.apache.org/jira/browse/HIVE-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13462121#comment-13462121 ] Sean Mackrory commented on HIVE-3277: - Code review: https://reviews.apache.org/r/7236/ > Enable Metastore audit logging for non-secure connections > - > > Key: HIVE-3277 > URL: https://issues.apache.org/jira/browse/HIVE-3277 > Project: Hive > Issue Type: Improvement > Components: Logging, Metastore, Security >Reporter: Carl Steinbach >Assignee: Sean Mackrory > Attachments: HIVE-3277.patch.1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3277) Enable Metastore audit logging for non-secure connections
[ https://issues.apache.org/jira/browse/HIVE-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HIVE-3277: Attachment: HIVE-3277.patch.2 Second patch fixes a code style issue > Enable Metastore audit logging for non-secure connections > - > > Key: HIVE-3277 > URL: https://issues.apache.org/jira/browse/HIVE-3277 > Project: Hive > Issue Type: Improvement > Components: Logging, Metastore, Security >Reporter: Carl Steinbach >Assignee: Sean Mackrory > Attachments: HIVE-3277.patch.1, HIVE-3277.patch.2 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-3505) log4j template has logging threshold that hides all audit logs
Sean Mackrory created HIVE-3505: --- Summary: log4j template has logging threshold that hides all audit logs Key: HIVE-3505 URL: https://issues.apache.org/jira/browse/HIVE-3505 Project: Hive Issue Type: Bug Reporter: Sean Mackrory With the "template" for log4j configuration provided in the tarball, audit logging is hidden (it's logged as "INFO"). By making the log threshold a parameter, this information remains hidden when using the CLI (which is desired) but can be overridden when starting services to enable audit-logging. (This is primarily so that Hive is more functional out-of-the-box as installed by Apache Bigtop). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3505) log4j template has logging threshold that hides all audit logs
[ https://issues.apache.org/jira/browse/HIVE-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HIVE-3505: Attachment: HIVE-3505.patch.1 > log4j template has logging threshold that hides all audit logs > -- > > Key: HIVE-3505 > URL: https://issues.apache.org/jira/browse/HIVE-3505 > Project: Hive > Issue Type: Bug >Reporter: Sean Mackrory > Attachments: HIVE-3505.patch.1 > > > With the "template" for log4j configuration provided in the tarball, audit > logging is hidden (it's logged as "INFO"). By making the log threshold a > parameter, this information remains hidden when using the CLI (which is > desired) but can be overridden when starting services to enable audit-logging. > (This is primarily so that Hive is more functional out-of-the-box as > installed by Apache Bigtop). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3505) log4j template has logging threshold that hides all audit logs
[ https://issues.apache.org/jira/browse/HIVE-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HIVE-3505: Status: Patch Available (was: Open) Code review here: https://reviews.apache.org/r/7238/ > log4j template has logging threshold that hides all audit logs > -- > > Key: HIVE-3505 > URL: https://issues.apache.org/jira/browse/HIVE-3505 > Project: Hive > Issue Type: Bug >Reporter: Sean Mackrory > Attachments: HIVE-3505.patch.1 > > > With the "template" for log4j configuration provided in the tarball, audit > logging is hidden (it's logged as "INFO"). By making the log threshold a > parameter, this information remains hidden when using the CLI (which is > desired) but can be overridden when starting services to enable audit-logging. > (This is primarily so that Hive is more functional out-of-the-box as > installed by Apache Bigtop). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3505) log4j template has logging threshold that hides all audit logs
[ https://issues.apache.org/jira/browse/HIVE-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HIVE-3505: Attachment: HIVE-3505.patch.2 This patch fixes a typo that existed on these lines before this fix. This patch is also in SVN format (as opposed to git). > log4j template has logging threshold that hides all audit logs > -- > > Key: HIVE-3505 > URL: https://issues.apache.org/jira/browse/HIVE-3505 > Project: Hive > Issue Type: Bug > Components: Logging >Reporter: Sean Mackrory >Assignee: Sean Mackrory > Attachments: HIVE-3505.patch.1, HIVE-3505.patch.2 > > > With the "template" for log4j configuration provided in the tarball, audit > logging is hidden (it's logged as "INFO"). By making the log threshold a > parameter, this information remains hidden when using the CLI (which is > desired) but can be overridden when starting services to enable audit-logging. > (This is primarily so that Hive is more functional out-of-the-box as > installed by Apache Bigtop). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3505) log4j template has logging threshold that hides all audit logs
[ https://issues.apache.org/jira/browse/HIVE-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13462221#comment-13462221 ] Sean Mackrory commented on HIVE-3505: - log4j.threshold and hive.root.logger specify two different levels. Should they actually be the same, in reality or should only one be paramterized? Which would be most intuitive considering how this file gets used? > log4j template has logging threshold that hides all audit logs > -- > > Key: HIVE-3505 > URL: https://issues.apache.org/jira/browse/HIVE-3505 > Project: Hive > Issue Type: Bug > Components: Logging >Reporter: Sean Mackrory >Assignee: Sean Mackrory > Attachments: HIVE-3505.patch.1, HIVE-3505.patch.2 > > > With the "template" for log4j configuration provided in the tarball, audit > logging is hidden (it's logged as "INFO"). By making the log threshold a > parameter, this information remains hidden when using the CLI (which is > desired) but can be overridden when starting services to enable audit-logging. > (This is primarily so that Hive is more functional out-of-the-box as > installed by Apache Bigtop). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3505) log4j template has logging threshold that hides all audit logs
[ https://issues.apache.org/jira/browse/HIVE-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HIVE-3505: Attachment: HIVE-3505.patch.3 New patch applies the same change to hive-exec-log4j.properties > log4j template has logging threshold that hides all audit logs > -- > > Key: HIVE-3505 > URL: https://issues.apache.org/jira/browse/HIVE-3505 > Project: Hive > Issue Type: Bug > Components: Logging >Reporter: Sean Mackrory >Assignee: Sean Mackrory > Attachments: HIVE-3505.patch.1, HIVE-3505.patch.2, HIVE-3505.patch.3 > > > With the "template" for log4j configuration provided in the tarball, audit > logging is hidden (it's logged as "INFO"). By making the log threshold a > parameter, this information remains hidden when using the CLI (which is > desired) but can be overridden when starting services to enable audit-logging. > (This is primarily so that Hive is more functional out-of-the-box as > installed by Apache Bigtop). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3505) log4j template has logging threshold that hides all audit logs
[ https://issues.apache.org/jira/browse/HIVE-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HIVE-3505: Attachment: HIVE-3505.patch.4 > log4j template has logging threshold that hides all audit logs > -- > > Key: HIVE-3505 > URL: https://issues.apache.org/jira/browse/HIVE-3505 > Project: Hive > Issue Type: Bug > Components: Logging >Reporter: Sean Mackrory >Assignee: Sean Mackrory > Attachments: HIVE-3505.patch.1, HIVE-3505.patch.2, HIVE-3505.patch.3, > HIVE-3505.patch.4 > > > With the "template" for log4j configuration provided in the tarball, audit > logging is hidden (it's logged as "INFO"). By making the log threshold a > parameter, this information remains hidden when using the CLI (which is > desired) but can be overridden when starting services to enable audit-logging. > (This is primarily so that Hive is more functional out-of-the-box as > installed by Apache Bigtop). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3277) Enable Metastore audit logging for non-secure connections
[ https://issues.apache.org/jira/browse/HIVE-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HIVE-3277: Resolution: Fixed Status: Resolved (was: Patch Available) > Enable Metastore audit logging for non-secure connections > - > > Key: HIVE-3277 > URL: https://issues.apache.org/jira/browse/HIVE-3277 > Project: Hive > Issue Type: Improvement > Components: Logging, Metastore, Security >Reporter: Carl Steinbach >Assignee: Sean Mackrory > Attachments: HIVE-3277.patch.1, HIVE-3277.patch.2 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-4070) Like operator in Hive is case sensitive while in MySQL (and most likely other DBs) it's case insensitive
[ https://issues.apache.org/jira/browse/HIVE-4070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HIVE-4070: Summary: Like operator in Hive is case sensitive while in MySQL (and most likely other DBs) it's case insensitive (was: Like operator in Hive is case sensitive while in MySQL (and most likely other DBs) it's case sensitive) > Like operator in Hive is case sensitive while in MySQL (and most likely other > DBs) it's case insensitive > > > Key: HIVE-4070 > URL: https://issues.apache.org/jira/browse/HIVE-4070 > Project: Hive > Issue Type: Bug > Components: UDF >Affects Versions: 0.10.0 >Reporter: Mark Grover >Assignee: Mark Grover > Fix For: 0.11.0 > > > Hive's like operator seems to be case sensitive. > See > https://github.com/apache/hive/blob/trunk/ql/src/java/org/apache/hadoop/hive/ql/udf/UDFLike.java#L164 > However, MySQL's like operator is case insensitive. I don't have other DB's > (like PostgreSQL) installed and handy but I am guessing their LIKE is case > insensitive as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-4070) Like operator in Hive is case sensitive while in MySQL (and most likely other DBs) it's case sensitive
[ https://issues.apache.org/jira/browse/HIVE-4070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13585944#comment-13585944 ] Sean Mackrory commented on HIVE-4070: - Though admittedly it was a question of mine trying to clarify HiveQL that spawned this thought, I don't necessarily think HiveQL's LIKE operator _should_ be case insensitive. It would certainly make HiveQL more consistent with SQL if it was, but when running extremely long queries over certain types of data, I could see it being a nice feature that LIKE gives you the flexibility of wild-cards without the overhead of case insensitivity. There's always the option of using RLIKE when one is looking for a very flexible match, but I think this is a toss-up between compliance with SQL's behavior and being able to limit the overhead of the query when possible. > Like operator in Hive is case sensitive while in MySQL (and most likely other > DBs) it's case sensitive > -- > > Key: HIVE-4070 > URL: https://issues.apache.org/jira/browse/HIVE-4070 > Project: Hive > Issue Type: Bug > Components: UDF >Affects Versions: 0.10.0 >Reporter: Mark Grover >Assignee: Mark Grover > Fix For: 0.11.0 > > > Hive's like operator seems to be case sensitive. > See > https://github.com/apache/hive/blob/trunk/ql/src/java/org/apache/hadoop/hive/ql/udf/UDFLike.java#L164 > However, MySQL's like operator is case insensitive. I don't have other DB's > (like PostgreSQL) installed and handy but I am guessing their LIKE is case > insensitive as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3819) Creating a table on Hive without Hadoop daemons running returns a misleading error
[
https://issues.apache.org/jira/browse/HIVE-3819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13602318#comment-13602318
]
Sean Mackrory commented on HIVE-3819:
-
I just ran into this error while Hadoop daemons were running but the problem
was that the Hive Metastore was running (backed by the embedded Derby database)
and the hive client was running in embedded mode and also trying to connect to
the embedded Derby database. Perhaps there are multiple common
misconfigurations that result in this error.
> Creating a table on Hive without Hadoop daemons running returns a misleading
> error
> --
>
> Key: HIVE-3819
> URL: https://issues.apache.org/jira/browse/HIVE-3819
> Project: Hive
> Issue Type: Bug
> Components: CLI, Metastore
>Reporter: Mark Grover
>
> I was running hive without running the underlying hadoop daemon's running.
> Hadoop was configured to run in pseudo-distributed mode. However, when I
> tried to create a hive table, I got this rather misleading error:
> {code}
> FAILED: Error in metadata: java.lang.RuntimeException: Unable to instantiate
> org.apache.hadoop.hive.metastore.HiveMetaStoreClient
> FAILED: Execution Error, return code 1 from
> org.apache.hadoop.hive.ql.exec.DDLTask
> {code}
> We should look into making this error message less misleading (more about
> hadoop daemons not running instead of metastore client not being
> instantiable).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
