Re: [DISCUSS] Properties for scheduling compactions on specific queues

Thanks Janos for the feedback. If I understand well your suggestion is support all of the properties below for table level compactions and treat them as equivalent: * compactor.mapred.job.queue.name * compactor.mapreduce.job.queuename * compactor.hive.compactor.job.queue It is something that cros

RE: [DISCUSS] Properties for scheduling compactions on specific queues

Hi Stamatis, I agree that the [compactor.]*hive.compactor.queue.name * is a better solution as hive now also supports query based compaction, not only MR. ...although I think this needs to be backward compatible! What do you think about a logic similar to this:

Re: [DISCUSS] Properties for scheduling compactions on specific queues

Hi Stamatis, the proposal seems reasonable to me. I think that setting the two properties you mention, independently from the underlying execution engine in use, should lead to the same result. In addition, I also agree that we should deprecate the per-execution engine properties. Best regards,

[DISCUSS] Properties for scheduling compactions on specific queues

Hi all, This email is an attempt to converge on which Hive/Tez/MR properties someone should use in order to schedule a compaction on specific queues. For those who are not familiar with how queues are used the YARN capacity scheduler documentation [1] gives the general idea. Using specific queues