[
https://issues.apache.org/jira/browse/HIVE-24159?focusedWorklogId=483913&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-483913
]
ASF GitHub Bot logged work on HIVE-24159:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 14/Sep/20 10:31
Start Date: 14/Sep/20 10:31
Worklog Time Spent: 10m
Work Description: abstractdog commented on pull request #1495:
URL: https://github.com/apache/hive/pull/1495#issuecomment-691967429
@ashutoshc : could you please take a quick look? thanks...
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 483913)
Time Spent: 20m (was: 10m)
> Kafka storage handler broken in secure environment pt2: short-circuit on
> non-secure environment
> -----------------------------------------------------------------------------------------------
>
> Key: HIVE-24159
> URL: https://issues.apache.org/jira/browse/HIVE-24159
> Project: Hive
> Issue Type: Improvement
> Reporter: László Bodor
> Assignee: László Bodor
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> As kafka_storage_handler.q was disabled by HIVE-23985, I haven't realized
> upstream that the kafka qtest fails. Instead of setting up a kerberized
> environment in qtest (which doesn't seem to be a usual usecase, e.g. haven't
> seen hive.server2.authentication.kerberos.principal used in *.q files) I
> managed to make the test with a simple
> UserGroupInformation.isSecurityEnabled() check, which can be also useful for
> every non-secure environment.
> For reference, the exception was:
> {code}
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
