[
https://issues.apache.org/jira/browse/HIVE-16313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Vary updated HIVE-16313:
------------------------------
Attachment: HIVE-16313.patch
When the log level is set to DEBUG and we had to wait for the compile lock then
there will be duplicate messages written to the log files every time:
{code}
2017-03-28T07:13:45,520 DEBUG [8b9772ae-cab0-4eb4-8256-404222a5caa0
HiveServer2-Handler-Pool: Thread-71] ql.Driver: Waiting to acquire compile
lock: drop table if exists drop_with_concurrency_1
Waiting to acquire compile lock.
2017-03-28T07:13:45,520 DEBUG [8b9772ae-cab0-4eb4-8256-404222a5caa0
HiveServer2-Handler-Pool: Thread-71] ql.Driver: Acquired the compile lock.
Acquired the compile lock.
{code}
To handle this situation we had be sure, that the logs are filtered in a
specific order with the patters.
[~ychena], could you please review?
Thanks,
Peter
> Flaky test: TestBeeLineDriver[drop_with_concurrency]
> ----------------------------------------------------
>
> Key: HIVE-16313
> URL: https://issues.apache.org/jira/browse/HIVE-16313
> Project: Hive
> Issue Type: Sub-task
> Components: Test
> Reporter: Peter Vary
> Assignee: Peter Vary
> Attachments: HIVE-16313.patch
>
>
> TestBeeLineDriver test become flaky:
> {code}
> 28a29 > Acquired the compile lock
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
