[ 
https://issues.apache.org/jira/browse/HIVE-13696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828642#comment-15828642
 ] 

Sushanth Sowmyan edited comment on HIVE-13696 at 1/18/17 7:48 PM:
------------------------------------------------------------------

[~ychena]/ [~sseth] - I'm still having issues after patching in HIVE-15615 
where a simple insert job is not working any more on a default apache tarball 
setup - see 
https://issues.apache.org/jira/browse/HIVE-15615?focusedCommentId=15828578#comment-15828578
 . Was that breakage caused by this patch, and what is the simple tarball 
usecase expected to be after this patch?

-Can we config-gate this feature to not do the restrictions unless configured 
to do so?-

Update edit : Looks like it is config-gated by 
hive.server2.map.fair.scheduler.queue, and setting that to false makes the job 
work, but that is set to true by default in HiveConf. [~sseth]/[~ychena], 
should true be the default for that if without this patch it wasn't submitting 
to various user queues, and with this patch, the default tarball usecase for 
people is broken? 


was (Author: sushanth):
[~ychena]/ [~sseth] - I'm still having issues after patching in HIVE-15615 
where a simple insert job is not working any more on a default apache tarball 
setup - see 
https://issues.apache.org/jira/browse/HIVE-15615?focusedCommentId=15828578#comment-15828578
 . Was that breakage caused by this patch, and what is the simple tarball 
usecase expected to be after this patch?

Can we config-gate this feature to not do the restrictions unless configured to 
do so?

> Monitor fair-scheduler.xml and automatically update/validate jobs submitted 
> to fair-scheduler
> ---------------------------------------------------------------------------------------------
>
>                 Key: HIVE-13696
>                 URL: https://issues.apache.org/jira/browse/HIVE-13696
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Reuben Kuhnert
>            Assignee: Reuben Kuhnert
>             Fix For: 2.2.0
>
>         Attachments: HIVE-13696.01.patch, HIVE-13696.02.patch, 
> HIVE-13696.06.patch, HIVE-13696.08.patch, HIVE-13696.11.patch, 
> HIVE-13696.13.patch, HIVE-13696.14.patch
>
>
> Ensure that jobs are placed into the correct queue according to 
> {{fair-scheduler.xml}}. Jobs should be placed into the correct queue, and 
> users should not be able to submit jobs to queues they do not have access to.
> This patch builds on the existing functionality in {{FairSchedulerShim}} to 
> route jobs to user-specific queue based on {{fair-scheduler.xml}} 
> configuration (leveraging the Yarn {{QueuePlacementPolicy}} class). In 
> addition to configuring job routing at session connect (current behavior), 
> the routing is validated per submission to yarn (when impersonation is off). 
> A {{FileSystemWatcher}} class is included to monitor changes in the 
> {{fair-scheduler.xml}} file (so updates are automatically reloaded when the 
> file pointed to by {{yarn.scheduler.fair.allocation.file}} is changed).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to