[
https://issues.apache.org/jira/browse/HIVE-26107?focusedWorklogId=763383&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-763383
]
ASF GitHub Bot logged work on HIVE-26107:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 28/Apr/22 09:22
Start Date: 28/Apr/22 09:22
Worklog Time Spent: 10m
Work Description: deniskuzZ commented on code in PR #3172:
URL: https://github.com/apache/hive/pull/3172#discussion_r860674098
##########
ql/src/java/org/apache/hadoop/hive/ql/txn/compactor/Worker.java:
##########
@@ -197,6 +198,9 @@ static void gatherStats(CompactionInfo ci, HiveConf conf,
String userName, Strin
statusUpdaterConf.set(TezConfiguration.TEZ_QUEUE_NAME,
compactionQueueName);
}
SessionState sessionState =
DriverUtils.setUpSessionState(statusUpdaterConf, userName, true);
+ Map<String, String> hiveVariables = sessionState.getHiveVariables();
+ hiveVariables.put(Constants.INSIDE_COMPACTION_TRANSACTION_FLAG,
"true");
+ sessionState.setHiveVariables(hiveVariables);
Review Comment:
could we create sessionState.setHiveVariable() method in SessionState?
Issue Time Tracking
-------------------
Worklog Id: (was: 763383)
Time Spent: 1h 40m (was: 1.5h)
> Worker shouldn't inject duplicate entries in `ready for cleaning` state into
> the compaction queue
> -------------------------------------------------------------------------------------------------
>
> Key: HIVE-26107
> URL: https://issues.apache.org/jira/browse/HIVE-26107
> Project: Hive
> Issue Type: Improvement
> Reporter: László Végh
> Assignee: László Végh
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> How to reproduce:
> 1) create an acid table and load some data ;
> 2) manually trigger the compaction for the table several times;
> 4) inspect compaction_queue: There are multiple entries in 'ready for
> cleaning' state for the same table.
>
> Expected behavior: All compaction request after the first one should be
> rejected until the table is changed again.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)