[
https://issues.apache.org/jira/browse/HIVE-20723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17482124#comment-17482124
]
Stamatis Zampetakis commented on HIVE-20723:
--------------------------------------------
It seems that it was possible to select a queue per table without implementing
the change here by using {{compactor.mapred.job.queue.name}} inside table
properties.
[~ekoifman] [~saurabhseth] is there any particular reason of why you chose to
do it via the {{compactor.hive.compactor.job.queue}} property? The problem is
that with the change in this JIRA the old property gets overwritten and doesn't
have the desired effect so it kinda breaks backward compatibility.
> Allow per table specification of compaction yarn queue
> ------------------------------------------------------
>
> Key: HIVE-20723
> URL: https://issues.apache.org/jira/browse/HIVE-20723
> Project: Hive
> Issue Type: New Feature
> Components: Transactions
> Affects Versions: 2.0.0
> Reporter: Eugene Koifman
> Assignee: Saurabh Seth
> Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-20723.patch
>
>
> Currently compactions of full CRUD transactional tables are Map-Reduce jobs
> submitted to a yarn queue defined by hive.compactor.job.queue property.
> If would be useful to be able to override this on per table basis by putting
> it into table properties so that compactions for different tables can use
> different queues.
>
> There is already ability to override other compaction related configs via
> table props, though this will need additional handling to set the queue name
> {{CompactorMr.createBaseJobConf}}
> [https://cwiki.apache.org/confluence/display/Hive/Hive+Transactions#HiveTransactions-TableProperties]
>
> See {{CopactorMR.COMPACTOR_PREFIX}} and
> {{Initiator.COMPACTORTHRESHOLD_PREFIX}}
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
