[jira] [Created] (OOZIE-3047) Support "jobtype=spark" in REST API
James Kinley created OOZIE-3047: --- Summary: Support "jobtype=spark" in REST API Key: OOZIE-3047 URL: https://issues.apache.org/jira/browse/OOZIE-3047 Project: Oozie Issue Type: New Feature Affects Versions: 4.3.0 Reporter: James Kinley The REST API should accept direct submission of Spark applications using the jobtype parameter to remove the need to upload Spark workflow definitions to HDFS. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OOZIE-2855) Add ability to set "X-Priority" header in email action
James Kinley created OOZIE-2855: --- Summary: Add ability to set "X-Priority" header in email action Key: OOZIE-2855 URL: https://issues.apache.org/jira/browse/OOZIE-2855 Project: Oozie Issue Type: New Feature Components: action Reporter: James Kinley Assignee: James Kinley -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (OOZIE-2252) Add HDFS extended ACL support in FS action
James Kinley created OOZIE-2252: --- Summary: Add HDFS extended ACL support in FS action Key: OOZIE-2252 URL: https://issues.apache.org/jira/browse/OOZIE-2252 Project: Oozie Issue Type: Improvement Components: action Reporter: James Kinley Priority: Minor Add support for the 'setfacl' command in the FS action. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OOZIE-1696) Document how to get the action conf in the Java action
[
https://issues.apache.org/jira/browse/OOZIE-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Kinley updated OOZIE-1696:
Attachment: OOZIE-1696.patch
Document how to get the action conf in the Java action
--
Key: OOZIE-1696
URL: https://issues.apache.org/jira/browse/OOZIE-1696
Project: Oozie
Issue Type: Sub-task
Components: docs
Affects Versions: trunk
Reporter: Robert Kanter
Assignee: James Kinley
Labels: newbie
Attachments: OOZIE-1696.patch
The Java action doesn't get a lot of the magic that we do in the other
actions, so things don't always behave right for users using the Java action
to launch MapReduce jobs. We've seen some confusion where these jobs were
picking up the mapred-default properties and not working because of it. It
would be great if we could document how to use the job conf prepared by
Oozie, which includes the proper mapred-site.xml (and other site files), plus
anything in the {{configuration}} section of the Java action.
Basically, they just need to create their job conf with something like this
(taken from MapReduceMain.java):
{code:java}
Configuration actionConf = new Configuration(false);
actionConf.addResource(new Path(file:///,
System.getProperty(oozie.action.conf.xml)));
{code}
We can put it next to the already documented snippet about the delegation
token propagation here:
http://oozie.apache.org/docs/4.0.0/WorkflowFunctionalSpec.html#a3.2.7_Java_Action
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-891) Add pagination for coordinator actions - Oozie web console
[ https://issues.apache.org/jira/browse/OOZIE-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13597048#comment-13597048 ] James Kinley commented on OOZIE-891: Agreed. This was the expedient option to prevent having to change the API. I will take another look at it. Add pagination for coordinator actions - Oozie web console -- Key: OOZIE-891 URL: https://issues.apache.org/jira/browse/OOZIE-891 Project: Oozie Issue Type: Bug Components: coordinator Affects Versions: 3.3.0 Reporter: Mona Chitnis Assignee: James Kinley Priority: Minor Labels: patch Fix For: trunk Attachments: OOZIE-891.patch Original Estimate: 72h Remaining Estimate: 72h -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OOZIE-967) Coordinator action window in web UI never finishes refreshing
[ https://issues.apache.org/jira/browse/OOZIE-967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Kinley updated OOZIE-967: --- Attachment: OOZIE-967.patch Added patch to simply remove the paging toolbar for now. This is more consistent with the workflow popup panel, and it never would have worked in it's current implementation without the job web service being changed. I think we should change OOZIE-891 to add pagination for all popup panels which will encompass the web service changes too. Coordinator action window in web UI never finishes refreshing - Key: OOZIE-967 URL: https://issues.apache.org/jira/browse/OOZIE-967 Project: Oozie Issue Type: Bug Reporter: Jonathan Natkins Assignee: James Kinley Attachments: OOZIE-967.patch When the detailed info for a coordinator workflow is brought up in the web UI, it has a smaller pane which displays info about the associated actions. Clicking the refresh button for that pane causes the UI to attempt to refresh (the spinner comes up and starts spinning), but the pane never reloads. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OOZIE-891) Add pagination for coordinator actions - Oozie web console
[ https://issues.apache.org/jira/browse/OOZIE-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13474890#comment-13474890 ] James Kinley commented on OOZIE-891: Suggest we change this to include pagination on all popup panels (workflow, coord, bundle). Add pagination for coordinator actions - Oozie web console -- Key: OOZIE-891 URL: https://issues.apache.org/jira/browse/OOZIE-891 Project: Oozie Issue Type: Bug Components: coordinator Affects Versions: 3.3.0 Reporter: Mona Chitnis Assignee: Mona Chitnis Priority: Minor Fix For: trunk Original Estimate: 72h Remaining Estimate: 72h -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OOZIE-967) Coordinator action window in web UI never finishes refreshing
[
https://issues.apache.org/jira/browse/OOZIE-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13474283#comment-13474283
]
James Kinley commented on OOZIE-967:
I'm not sure why this panel has a paging toolbar because the dataset that backs
it is fixed on panel load, which is why it gets stuck in the refresh state.
If you take a look at:
{code}
src/main/webapp/oozie-console.js
{code}
The main panels for Workflow jobs, Coordinator jobs, etc (not the popups),
have a paging toolbar that is backed by a {{Ext.data.JsonStore}} that is
proxied back to the {{/oozie/v1/jobs}} web services. The jobs web services
respond with the {{total}} json tag which enables the paging toolbar to be
rendered correctly.
On the other hand, the popup panel for Workflow jobs does not have a paging
toolbar at the bottom of the panel because the {{Ext.data.JsonStore}} used by
the panel is fixed on load and it simply lists all of the actions.
The popup panel for Coordinator jobs has a paging toolbar, but its
{{Ext.data.JsonStore}} is fixed in the same way as the Workflow jobs popup
and is not proxied back to the {{/oozie/v1/job}} web services - and therefore
doesn't work and gets stuck when you hit the refresh button. If you had enough
workflows in the list (50) the paging would also not work correctly.
I have tried to get it working by changing the {{Ext.data.JsonStore}} to
request its data from {{/oozie/v1/job}}, but the web service doesn't respond
with the {{total}} json tag causing the paging toolbar to render incorrectly.
I could change the {{/oozie/v1/job}} web services and all of the
{{Ext.data.JsonStore}}'s in the popup panels, which would require a bit of a
rewrite. Or I could simply remove the paging toolbar from the Coordinator
jobs panel altogether, which would be more consistent with the Workflow jobs
panel.
Coordinator action window in web UI never finishes refreshing
-
Key: OOZIE-967
URL: https://issues.apache.org/jira/browse/OOZIE-967
Project: Oozie
Issue Type: Bug
Reporter: Jonathan Natkins
Assignee: James Kinley
When the detailed info for a coordinator workflow is brought up in the web
UI, it has a smaller pane which displays info about the associated actions.
Clicking the refresh button for that pane causes the UI to attempt to refresh
(the spinner comes up and starts spinning), but the pane never reloads.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OOZIE-949) Allow the user to set 'mapred.job.name'
[
https://issues.apache.org/jira/browse/OOZIE-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13469230#comment-13469230
]
James Kinley commented on OOZIE-949:
Hi Alejandro,
To override the launcher job name you do still have to use
{{oozie.launcher.mapred.job.name}}.
The reason I check for the existence of {{mapred.job.name}} when setting up the
launcher configuration is because in {{setupLauncherConf}}, and specifically
{{injectLauncherProperties}} which it calls, it sets {{mapred.job.name}} to
{{oozie.launcher.mapred.job.name}}.
All I am doing is checking whether this has been set in the configuration, if
it has do nothing else, if it hasn't set to the default -
{{oozie:launcher:T={0}:W={1}:A={2}:ID={3}}}
Because the launcher job creates its own configuration instance
{{mapred.job.name}} is not shared between the launcher and action so unless the
user explicitly sets them to the same name, they will be different.
Allow the user to set 'mapred.job.name'
---
Key: OOZIE-949
URL: https://issues.apache.org/jira/browse/OOZIE-949
Project: Oozie
Issue Type: Improvement
Components: action, core
Affects Versions: 3.1.3
Reporter: James Kinley
Priority: Minor
Labels: patch
Fix For: trunk
Attachments: OOZIE-949.patch, OOZIE-949-v2.patch, OOZIE-949-v3.patch
Give user the ability to set {{mapred.job.name}} in their workflow job
configuration and not have Oozie override it in
{{JavaActionExecutor#submitLauncher()}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OOZIE-949) Allow the user to set 'mapred.job.name'
[
https://issues.apache.org/jira/browse/OOZIE-949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Kinley updated OOZIE-949:
---
Attachment: (was: OOZIE-949-v3.patch)
Allow the user to set 'mapred.job.name'
---
Key: OOZIE-949
URL: https://issues.apache.org/jira/browse/OOZIE-949
Project: Oozie
Issue Type: Improvement
Components: action, core
Affects Versions: 3.1.3
Reporter: James Kinley
Priority: Minor
Labels: patch
Fix For: trunk
Attachments: OOZIE-949.patch, OOZIE-949-v2.patch
Give user the ability to set {{mapred.job.name}} in their workflow job
configuration and not have Oozie override it in
{{JavaActionExecutor#submitLauncher()}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OOZIE-949) Allow the user to set 'mapred.job.name'
[
https://issues.apache.org/jira/browse/OOZIE-949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Kinley updated OOZIE-949:
---
Attachment: (was: OOZIE-949-v3.patch)
Allow the user to set 'mapred.job.name'
---
Key: OOZIE-949
URL: https://issues.apache.org/jira/browse/OOZIE-949
Project: Oozie
Issue Type: Improvement
Components: action, core
Affects Versions: 3.1.3
Reporter: James Kinley
Priority: Minor
Labels: patch
Fix For: trunk
Attachments: OOZIE-949.patch, OOZIE-949-v2.patch, OOZIE-949-v3.patch
Give user the ability to set {{mapred.job.name}} in their workflow job
configuration and not have Oozie override it in
{{JavaActionExecutor#submitLauncher()}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OOZIE-949) Allow the user to set 'mapred.job.name'
[
https://issues.apache.org/jira/browse/OOZIE-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13456718#comment-13456718
]
James Kinley commented on OOZIE-949:
I cannot see a line with a trailing space, so I don't know why the QA is
failing. I also cannot see in the jenkins logs which line is causing the
problem. Is there any way to tell which line jenkins thinks has a trailing
space?
Allow the user to set 'mapred.job.name'
---
Key: OOZIE-949
URL: https://issues.apache.org/jira/browse/OOZIE-949
Project: Oozie
Issue Type: Improvement
Components: action, core
Affects Versions: 3.1.3
Reporter: James Kinley
Priority: Minor
Labels: patch
Fix For: trunk
Attachments: OOZIE-949.patch, OOZIE-949-v2.patch, OOZIE-949-v3.patch
Give user the ability to set {{mapred.job.name}} in their workflow job
configuration and not have Oozie override it in
{{JavaActionExecutor#submitLauncher()}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
