[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 ] Carl Steinbach updated HIVE-3505: - Assignee: Sean Mackrory Status: Open (was: Patch Available) @Sean: comments on reviewboard. Thanks. 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 Assignee: 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 ] Carl Steinbach updated HIVE-3505: - Component/s: Logging 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 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] [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
