[jira] [Assigned] (AMBARI-22868) Expose ability to configure "done-flag" for Coordinator Datasets in Workflow Designer
[ https://issues.apache.org/jira/browse/AMBARI-22868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj reassigned AMBARI-22868: Assignee: venkat > Expose ability to configure "done-flag" for Coordinator Datasets in Workflow > Designer > - > > Key: AMBARI-22868 > URL: https://issues.apache.org/jira/browse/AMBARI-22868 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.2 >Reporter: Brian Goerlitz >Assignee: venkat >Priority: Major > Labels: WFD, WFM, pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > AMBARI-18691 added support for Coordinators to the Workflow Designer, but > does not expose configuration of dataset done-flag in the UI. > > done-flag needs to support the following in generated xml: > * absent > * present, but empty > * present with text value -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-22868) Expose ability to configure "done-flag" for Coordinator Datasets in Workflow Designer
[ https://issues.apache.org/jira/browse/AMBARI-22868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj reassigned AMBARI-22868: Assignee: (was: venkat) > Expose ability to configure "done-flag" for Coordinator Datasets in Workflow > Designer > - > > Key: AMBARI-22868 > URL: https://issues.apache.org/jira/browse/AMBARI-22868 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.2 >Reporter: Brian Goerlitz >Priority: Major > Labels: WFD, WFM, pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > AMBARI-18691 added support for Coordinators to the Workflow Designer, but > does not expose configuration of dataset done-flag in the UI. > > done-flag needs to support the following in generated xml: > * absent > * present, but empty > * present with text value -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-20850) WFM: Clicking search icon in workflow dashboard throws error
[ https://issues.apache.org/jira/browse/AMBARI-20850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20850: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk, branch-2.5 > WFM: Clicking search icon in workflow dashboard throws error > > > Key: AMBARI-20850 > URL: https://issues.apache.org/jira/browse/AMBARI-20850 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20850.patch, AMBARI-20850-updated.patch, > wf-error.jpg > > > Clicking on search icon when the filter is empty in workflow dashboard throws > the error Remote API failed as in screenshot -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20850) WFM: Clicking search icon in workflow dashboard throws error
[ https://issues.apache.org/jira/browse/AMBARI-20850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20850: - Affects Version/s: 2.5.1 Fix Version/s: (was: trunk) 2.5.1 > WFM: Clicking search icon in workflow dashboard throws error > > > Key: AMBARI-20850 > URL: https://issues.apache.org/jira/browse/AMBARI-20850 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20850.patch, AMBARI-20850-updated.patch, > wf-error.jpg > > > Clicking on search icon when the filter is empty in workflow dashboard throws > the error Remote API failed as in screenshot -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20866) Distcp should take a single command rather than list of arguments to make it easier ot use.
[ https://issues.apache.org/jira/browse/AMBARI-20866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20866: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk, branch-2.5 > Distcp should take a single command rather than list of arguments to make it > easier ot use. > --- > > Key: AMBARI-20866 > URL: https://issues.apache.org/jira/browse/AMBARI-20866 > Project: Ambari > Issue Type: Improvement > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20866_trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20867) Cleanup Jsplumb specific code from WFM
[ https://issues.apache.org/jira/browse/AMBARI-20867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20867: - Attachment: (was: AMBARI-20867_trunk.patch) > Cleanup Jsplumb specific code from WFM > -- > > Key: AMBARI-20867 > URL: https://issues.apache.org/jira/browse/AMBARI-20867 > Project: Ambari > Issue Type: Improvement > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20867_trunk.patch > > > Clean up code and dependencies related JSPlumb which is no longer used. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20867) Cleanup Jsplumb specific code from WFM
[ https://issues.apache.org/jira/browse/AMBARI-20867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20867: - Attachment: AMBARI-20867_trunk.patch > Cleanup Jsplumb specific code from WFM > -- > > Key: AMBARI-20867 > URL: https://issues.apache.org/jira/browse/AMBARI-20867 > Project: Ambari > Issue Type: Improvement > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20867_trunk.patch, AMBARI-20867_trunk.patch > > > Clean up code and dependencies related JSPlumb which is no longer used. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20867) Cleanup Jsplumb specific code from WFM
[ https://issues.apache.org/jira/browse/AMBARI-20867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20867: - Status: Patch Available (was: Open) > Cleanup Jsplumb specific code from WFM > -- > > Key: AMBARI-20867 > URL: https://issues.apache.org/jira/browse/AMBARI-20867 > Project: Ambari > Issue Type: Improvement > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20867_trunk.patch, AMBARI-20867_trunk.patch > > > Clean up code and dependencies related JSPlumb which is no longer used. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20867) Cleanup Jsplumb specific code from WFM
[ https://issues.apache.org/jira/browse/AMBARI-20867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20867: - Attachment: AMBARI-20867_trunk.patch > Cleanup Jsplumb specific code from WFM > -- > > Key: AMBARI-20867 > URL: https://issues.apache.org/jira/browse/AMBARI-20867 > Project: Ambari > Issue Type: Improvement > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20867_trunk.patch > > > Clean up code and dependencies related JSPlumb which is no longer used. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20867) Cleanup Jsplumb specific code from WFM
Padma Priya Nagaraj created AMBARI-20867: Summary: Cleanup Jsplumb specific code from WFM Key: AMBARI-20867 URL: https://issues.apache.org/jira/browse/AMBARI-20867 Project: Ambari Issue Type: Improvement Components: ambari-views Affects Versions: 2.5.1 Reporter: Padma Priya Nagaraj Assignee: Padma Priya Nagaraj Fix For: 2.5.1 Clean up code and dependencies related JSPlumb which is no longer used. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20866) Distcp should take a single command rather than list of arguments to make it easier ot use.
[ https://issues.apache.org/jira/browse/AMBARI-20866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20866: - Status: Patch Available (was: Open) > Distcp should take a single command rather than list of arguments to make it > easier ot use. > --- > > Key: AMBARI-20866 > URL: https://issues.apache.org/jira/browse/AMBARI-20866 > Project: Ambari > Issue Type: Improvement > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20866_trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20866) Distcp should take a single command rather than list of arguments to make it easier ot use.
[ https://issues.apache.org/jira/browse/AMBARI-20866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20866: - Attachment: AMBARI-20866_trunk.patch > Distcp should take a single command rather than list of arguments to make it > easier ot use. > --- > > Key: AMBARI-20866 > URL: https://issues.apache.org/jira/browse/AMBARI-20866 > Project: Ambari > Issue Type: Improvement > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20866_trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20866) Distcp should take a single command rather than list of arguments to make it easier ot use.
Padma Priya Nagaraj created AMBARI-20866: Summary: Distcp should take a single command rather than list of arguments to make it easier ot use. Key: AMBARI-20866 URL: https://issues.apache.org/jira/browse/AMBARI-20866 Project: Ambari Issue Type: Improvement Components: ambari-views Affects Versions: 2.5.1 Reporter: Padma Priya Nagaraj Assignee: Padma Priya Nagaraj Fix For: 2.5.1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20838) WFM: Date filter in workflow dashboard is not working properly
[ https://issues.apache.org/jira/browse/AMBARI-20838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984457#comment-15984457 ] Padma Priya Nagaraj commented on AMBARI-20838: -- Committed to trunk, branch-2.5 > WFM: Date filter in workflow dashboard is not working properly > -- > > Key: AMBARI-20838 > URL: https://issues.apache.org/jira/browse/AMBARI-20838 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20838.patch > > > Date filter in workflow dashboard is not filtering the values according to > the date entered. Also AM/PM is not calculated for the time while filtering. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20838) WFM: Date filter in workflow dashboard is not working properly
[ https://issues.apache.org/jira/browse/AMBARI-20838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20838: - Resolution: Fixed Status: Resolved (was: Patch Available) > WFM: Date filter in workflow dashboard is not working properly > -- > > Key: AMBARI-20838 > URL: https://issues.apache.org/jira/browse/AMBARI-20838 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20838.patch > > > Date filter in workflow dashboard is not filtering the values according to > the date entered. Also AM/PM is not calculated for the time while filtering. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20838) WFM: Date filter in workflow dashboard is not working properly
[ https://issues.apache.org/jira/browse/AMBARI-20838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20838: - Labels: WFD WFM (was: ) > WFM: Date filter in workflow dashboard is not working properly > -- > > Key: AMBARI-20838 > URL: https://issues.apache.org/jira/browse/AMBARI-20838 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20838.patch > > > Date filter in workflow dashboard is not filtering the values according to > the date entered. Also AM/PM is not calculated for the time while filtering. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20838) WFM: Date filter in workflow dashboard is not working properly
[ https://issues.apache.org/jira/browse/AMBARI-20838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20838: - Affects Version/s: (was: trunk) 2.5.1 > WFM: Date filter in workflow dashboard is not working properly > -- > > Key: AMBARI-20838 > URL: https://issues.apache.org/jira/browse/AMBARI-20838 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20838.patch > > > Date filter in workflow dashboard is not filtering the values according to > the date entered. Also AM/PM is not calculated for the time while filtering. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20838) WFM: Date filter in workflow dashboard is not working properly
[ https://issues.apache.org/jira/browse/AMBARI-20838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20838: - Fix Version/s: (was: trunk) 2.5.1 > WFM: Date filter in workflow dashboard is not working properly > -- > > Key: AMBARI-20838 > URL: https://issues.apache.org/jira/browse/AMBARI-20838 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20838.patch > > > Date filter in workflow dashboard is not filtering the values according to > the date entered. Also AM/PM is not calculated for the time while filtering. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20838) WFM: Date filter in workflow dashboard is not working properly
[ https://issues.apache.org/jira/browse/AMBARI-20838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20838: - Component/s: ambari-views > WFM: Date filter in workflow dashboard is not working properly > -- > > Key: AMBARI-20838 > URL: https://issues.apache.org/jira/browse/AMBARI-20838 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20838.patch > > > Date filter in workflow dashboard is not filtering the values according to > the date entered. Also AM/PM is not calculated for the time while filtering. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20740) Coordinator Actions(workflows) are empty even when workflows are executed.
[ https://issues.apache.org/jira/browse/AMBARI-20740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20740: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk, branch-2.5 > Coordinator Actions(workflows) are empty even when workflows are executed. > -- > > Key: AMBARI-20740 > URL: https://issues.apache.org/jira/browse/AMBARI-20740 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Belliraj HB >Assignee: M Madhan Mohan Reddy >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20740_trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20718) User should not be allowed to validate/Submit the workflow in case of duplicate action nodes
[ https://issues.apache.org/jira/browse/AMBARI-20718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20718: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk, branch-2.5 > User should not be allowed to validate/Submit the workflow in case of > duplicate action nodes > > > Key: AMBARI-20718 > URL: https://issues.apache.org/jira/browse/AMBARI-20718 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: venkat > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20718-trunk.patch > > > User should not be allowed to validate/Submit the workflow in case of > duplicate action nodes. As of now, workflow manager shows error message > saying that workflow has duplicate action node. But it still allows the user > to submit the workflow and workflow validation/Submission fails. Its better > to prompt the user to correct the workflow before allowing him to > Validate/Submit. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20729) Need way to explicitly ask for workflow name
[ https://issues.apache.org/jira/browse/AMBARI-20729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20729: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk, branch-2.5 > Need way to explicitly ask for workflow name > - > > Key: AMBARI-20729 > URL: https://issues.apache.org/jira/browse/AMBARI-20729 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: venkat >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20729-trunk.patch > > > This is a ask from lot of users where they get confused between workflow name > and workflow xml file name. > Since workflow manager is auto populating workflow name, usually forgets to > enter this manually. > And once he saves the workflow at specific path, he expects the file name to > be workflow name. > This behaviour will also damage the user experience in project manager view. > To avoid this ambiguity, workflow manager should explicitly ask for workflow > name. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20673) For sort/partition operator, if there is only 1 reducer, display just "sort" rather than "sort/partition"
[ https://issues.apache.org/jira/browse/AMBARI-20673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20673: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk, branch-2.5 > For sort/partition operator, if there is only 1 reducer, display just "sort" > rather than "sort/partition" > - > > Key: AMBARI-20673 > URL: https://issues.apache.org/jira/browse/AMBARI-20673 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.1 > > Attachments: AMBARI-20673-trunk.patch > > > For sort/partition operator, if there is only 1 reducer, display just "sort" > rather than "sort/partition" in visual explain graph -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20704) Need a way to indicate the action node type in workflow manager
[ https://issues.apache.org/jira/browse/AMBARI-20704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20704: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk, branch-2.5 > Need a way to indicate the action node type in workflow manager > --- > > Key: AMBARI-20704 > URL: https://issues.apache.org/jira/browse/AMBARI-20704 > Project: Ambari > Issue Type: Improvement > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: venkat > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20704-trunk.patch > > > Currently there's no way for the user to know the action node type from > workflow designer page. > Need to add this ability to indicate the action node type in the designer. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20689) Zooming workflows should happen more smoothly
[ https://issues.apache.org/jira/browse/AMBARI-20689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20689: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk, branch-2.5 > Zooming workflows should happen more smoothly > - > > Key: AMBARI-20689 > URL: https://issues.apache.org/jira/browse/AMBARI-20689 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: M Madhan Mohan Reddy >Assignee: M Madhan Mohan Reddy > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20689_trunk.patch > > > Zooming workflows should happen more smoothly. As of now if user clicks on > +/- , zoom is happening in bigger steps and creates a bad user experience. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20677) Centering workflows for zoom breaks when multiple tabs exists
[ https://issues.apache.org/jira/browse/AMBARI-20677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20677: - Resolution: Fixed Status: Resolved (was: Patch Available) Committer to trunk, branch-2.5 > Centering workflows for zoom breaks when multiple tabs exists > - > > Key: AMBARI-20677 > URL: https://issues.apache.org/jira/browse/AMBARI-20677 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: M Madhan Mohan Reddy >Assignee: M Madhan Mohan Reddy > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20677_trunk.patch > > > If multiple tabs exists, only the tab that got highlighted at the end has the > workflow at center. In remaining tabs, workflow is not at the center. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20676) User should be able to visualize inherited properties while submitting the workflow
[ https://issues.apache.org/jira/browse/AMBARI-20676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20676: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk, branch-2.5 > User should be able to visualize inherited properties while submitting the > workflow > --- > > Key: AMBARI-20676 > URL: https://issues.apache.org/jira/browse/AMBARI-20676 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: M Madhan Mohan Reddy >Assignee: M Madhan Mohan Reddy > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20676_trunk.patch > > > User should be able to visualize inherited properties while submitting the > workflow. > As asked by one of the user (Artem) its better to show inherited properties > like “queueName”, “resourceManager”, “namenode” etc which are added by > workflow designer by default. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20413) The Zoom feature in WFM, hides the WF completely either with Maximum and Min
[ https://issues.apache.org/jira/browse/AMBARI-20413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20413: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk, branch-2.5 > The Zoom feature in WFM, hides the WF completely either with Maximum and Min > > > Key: AMBARI-20413 > URL: https://issues.apache.org/jira/browse/AMBARI-20413 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: M Madhan Mohan Reddy >Assignee: M Madhan Mohan Reddy > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20413_trunk.patch > > > Steps to repro: > Create a WF and add a action > Now use the Zoom feature and Maximize it completely and return to normal. You > will not be able to see the WF information. > The same is applied for complete Minimize as well. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20662) Need to auto populate the workflow parameters if its already defined in the global space
[ https://issues.apache.org/jira/browse/AMBARI-20662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20662: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk, branch-2.5 > Need to auto populate the workflow parameters if its already defined in the > global space > > > Key: AMBARI-20662 > URL: https://issues.apache.org/jira/browse/AMBARI-20662 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: M Madhan Mohan Reddy >Assignee: M Madhan Mohan Reddy > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20662_trunk.patch > > > Need to auto populate the workflow parameters if its already defined in the > global space. > ie If user has already specified workflow parameters in the global space then > while submitting the > workflow, these parameters should be auto populated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20659) Notification widgets position have been fixed and size have been reduced
[ https://issues.apache.org/jira/browse/AMBARI-20659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20659: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk, branch-2.5 > Notification widgets position have been fixed and size have been reduced > > > Key: AMBARI-20659 > URL: https://issues.apache.org/jira/browse/AMBARI-20659 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.1 > > Attachments: AMBARI-20659-trunk.patch > > > Notification will not be visible when we are the bottom of page -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20658) Click of "NEW JOB" button doesn't create new worksheet tab
[ https://issues.apache.org/jira/browse/AMBARI-20658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20658: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk, branch-2.5 > Click of "NEW JOB" button doesn't create new worksheet tab > -- > > Key: AMBARI-20658 > URL: https://issues.apache.org/jira/browse/AMBARI-20658 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.1 > > Attachments: AMBARI-20658-trunk.patch > > > Click on NEW JOB button doesn't create new worksheet tab -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20656) Coordinator and bundle should retain job.properties in submission modal window
[ https://issues.apache.org/jira/browse/AMBARI-20656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20656: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk, branch-2.5 > Coordinator and bundle should retain job.properties in submission modal window > -- > > Key: AMBARI-20656 > URL: https://issues.apache.org/jira/browse/AMBARI-20656 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: M Madhan Mohan Reddy >Assignee: M Madhan Mohan Reddy > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20656_trunk.patch > > > Coordinator should retain job.properties in submission modal window. If user > is submitting the same coordinator second time, then initially provided > details should be auto populated in the submission modal window. And also > similar behavior for bundle too. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20653) Bad user experience in workflow credential creation
[ https://issues.apache.org/jira/browse/AMBARI-20653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20653: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk, branch-2.5 > Bad user experience in workflow credential creation > --- > > Key: AMBARI-20653 > URL: https://issues.apache.org/jira/browse/AMBARI-20653 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: M Madhan Mohan Reddy >Assignee: M Madhan Mohan Reddy > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20653_trunk.patch > > > While adding workflow credentials, 'Add' button is not at all visible in the > modal window and only 'Save' button is visible. > Since even after adding all the credential configs 'Add' button is not > visible, user is tend to click on Save button and modal window just closes. > This give the user the wrong impression that credential is created. > Need to change this behavior and make it more intuitive. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20655) Need to improve the grouping of the nodes available in transition section of WFM
[ https://issues.apache.org/jira/browse/AMBARI-20655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20655: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk, branch-2.5 > Need to improve the grouping of the nodes available in transition section of > WFM > > > Key: AMBARI-20655 > URL: https://issues.apache.org/jira/browse/AMBARI-20655 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: M Madhan Mohan Reddy >Assignee: M Madhan Mohan Reddy > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20655_trunk.patch > > > Need to improve the grouping of the nodes available in transition > section(Error To and OK to) of WFM. As of now its grouped under 'Kill Nodes' > and 'Other Nodes' > But 'Kill Nodes' and 'Other Nodes' look like list items available for > selection. > Need to make it more intuitive. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20654) Workflow should retain job.properties in submission modal window
[ https://issues.apache.org/jira/browse/AMBARI-20654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20654: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk, branch-2.5 > Workflow should retain job.properties in submission modal window > > > Key: AMBARI-20654 > URL: https://issues.apache.org/jira/browse/AMBARI-20654 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 >Reporter: M Madhan Mohan Reddy >Assignee: M Madhan Mohan Reddy > Labels: WFD, WFM > Fix For: 2.5.1 > > Attachments: AMBARI-20654_trunk.patch > > > Workflow should retain job.properties in submission modal window. If user is > submitting the same workflow second time, then initially provided details > should be auto populated in the submission modal window. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20475) Issue with cut/copy functionality in workflow manager
[ https://issues.apache.org/jira/browse/AMBARI-20475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20475: - Status: Patch Available (was: Open) > Issue with cut/copy functionality in workflow manager > - > > Key: AMBARI-20475 > URL: https://issues.apache.org/jira/browse/AMBARI-20475 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Padma Priya Nagaraj >Priority: Blocker > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20475_trunk.patch > > > Action node configurations are getting copied across copied nodes even after > pasting the original node. > Steps to reproduce : > 1) Create an action node. > 2) Copy the node > 3) Create a new node of the same type in the workflow by pasting the node. > 4) Now modify the configurations for one node. Then configuration is also > getting changed for the second node. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20475) Issue with cut/copy functionality in workflow manager
[ https://issues.apache.org/jira/browse/AMBARI-20475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20475: - Attachment: AMBARI-20475_trunk.patch > Issue with cut/copy functionality in workflow manager > - > > Key: AMBARI-20475 > URL: https://issues.apache.org/jira/browse/AMBARI-20475 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Padma Priya Nagaraj >Priority: Blocker > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20475_trunk.patch > > > Action node configurations are getting copied across copied nodes even after > pasting the original node. > Steps to reproduce : > 1) Create an action node. > 2) Copy the node > 3) Create a new node of the same type in the workflow by pasting the node. > 4) Now modify the configurations for one node. Then configuration is also > getting changed for the second node. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20475) Issue with cut/copy functionality in workflow manager
[ https://issues.apache.org/jira/browse/AMBARI-20475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj reassigned AMBARI-20475: Assignee: Padma Priya Nagaraj > Issue with cut/copy functionality in workflow manager > - > > Key: AMBARI-20475 > URL: https://issues.apache.org/jira/browse/AMBARI-20475 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Padma Priya Nagaraj >Priority: Blocker > Labels: WFD, WFM > Fix For: 2.5.0 > > > Action node configurations are getting copied across copied nodes even after > pasting the original node. > Steps to reproduce : > 1) Create an action node. > 2) Copy the node > 3) Create a new node of the same type in the workflow by pasting the node. > 4) Now modify the configurations for one node. Then configuration is also > getting changed for the second node. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20383) Not able to view the error log details on UI
[
https://issues.apache.org/jira/browse/AMBARI-20383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Padma Priya Nagaraj updated AMBARI-20383:
-
Assignee: Padma Priya Nagaraj
Status: Patch Available (was: Open)
> Not able to view the error log details on UI
> -
>
> Key: AMBARI-20383
> URL: https://issues.apache.org/jira/browse/AMBARI-20383
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: Padma Priya Nagaraj
>Priority: Critical
> Labels: WFD, WFM
> Fix For: 2.5.0
>
> Attachments: AMBARI-20383_trunk.patch
>
>
> Not able to view the error logs on UI. When user clicks on 'Details' link, UI
> is failing with below error:
> {code}
> Uncaught TypeError: Cannot read property 'nodes' of null
> at n.isWorkflowValid
> (http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-89dda89e1533d3f32ee5166954811095.js:8:25204)
> at n.validate
> (http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-89dda89e1533d3f32ee5166954811095.js:58:12130)
> at
> http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:65:30047
> at Array.map (native)
> at n.
> (http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:65:29848)
> at n.
> (http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:65:24894)
> at d.p.get
> (http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:9:31289)
> at s
> (http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:11:3104)
> at c
> (http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:11:3694)
> at s
> (http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:11:3093)
> {code}
> Steps to reproduce :
> 1) Try to import a workflow which user doesn't have read permission.
> 2) 'Permission Denied' message is shown on the UI. But when user clicks on
> 'Details' link, UI is failing.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20383) Not able to view the error log details on UI
[
https://issues.apache.org/jira/browse/AMBARI-20383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Padma Priya Nagaraj updated AMBARI-20383:
-
Attachment: AMBARI-20383_trunk.patch
> Not able to view the error log details on UI
> -
>
> Key: AMBARI-20383
> URL: https://issues.apache.org/jira/browse/AMBARI-20383
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Priority: Critical
> Labels: WFD, WFM
> Fix For: 2.5.0
>
> Attachments: AMBARI-20383_trunk.patch
>
>
> Not able to view the error logs on UI. When user clicks on 'Details' link, UI
> is failing with below error:
> {code}
> Uncaught TypeError: Cannot read property 'nodes' of null
> at n.isWorkflowValid
> (http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-89dda89e1533d3f32ee5166954811095.js:8:25204)
> at n.validate
> (http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-89dda89e1533d3f32ee5166954811095.js:58:12130)
> at
> http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:65:30047
> at Array.map (native)
> at n.
> (http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:65:29848)
> at n.
> (http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:65:24894)
> at d.p.get
> (http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:9:31289)
> at s
> (http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:11:3104)
> at c
> (http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:11:3694)
> at s
> (http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:11:3093)
> {code}
> Steps to reproduce :
> 1) Try to import a workflow which user doesn't have read permission.
> 2) 'Permission Denied' message is shown on the UI. But when user clicks on
> 'Details' link, UI is failing.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20381) User is not able to import workflows, coordinators and bundles
[
https://issues.apache.org/jira/browse/AMBARI-20381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Padma Priya Nagaraj updated AMBARI-20381:
-
Attachment: AMBARI-20381_trunk.patch
> User is not able to import workflows, coordinators and bundles
> --
>
> Key: AMBARI-20381
> URL: https://issues.apache.org/jira/browse/AMBARI-20381
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: Padma Priya Nagaraj
>Priority: Blocker
> Labels: WFD, WFM
> Fix For: 2.5.0
>
> Attachments: AMBARI-20381_trunk.patch
>
>
> User is not able to import workflows, coordinators and bundles. Seeing below
> error in UI console.log
> {code}
> TypeError: Cannot read property 'workflow-app' of null
> at n.processWorkflowXml (oozie-designer-89dda89….js:9)
> at n.importWorkflow (oozie-designer-89dda89….js:9)
> at n.importWorkflowFromString (oozie-designer-89dda89….js:3)
> at n. (oozie-designer-89dda89….js:3)
> at y (vendor-b25c8db….js:19)
> at b (vendor-b25c8db….js:19)
> at g (vendor-b25c8db….js:19)
> at vendor-b25c8db….js:13
> at invoke (vendor-b25c8db….js:5)
> at n.flush (vendor-b25c8db….js:5)
> {code}
> Facing the same issue while importing the asset from hdfs as well.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20381) User is not able to import workflows, coordinators and bundles
[
https://issues.apache.org/jira/browse/AMBARI-20381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Padma Priya Nagaraj updated AMBARI-20381:
-
Status: Patch Available (was: Open)
> User is not able to import workflows, coordinators and bundles
> --
>
> Key: AMBARI-20381
> URL: https://issues.apache.org/jira/browse/AMBARI-20381
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: Padma Priya Nagaraj
>Priority: Blocker
> Labels: WFD, WFM
> Fix For: 2.5.0
>
> Attachments: AMBARI-20381_trunk.patch
>
>
> User is not able to import workflows, coordinators and bundles. Seeing below
> error in UI console.log
> {code}
> TypeError: Cannot read property 'workflow-app' of null
> at n.processWorkflowXml (oozie-designer-89dda89….js:9)
> at n.importWorkflow (oozie-designer-89dda89….js:9)
> at n.importWorkflowFromString (oozie-designer-89dda89….js:3)
> at n. (oozie-designer-89dda89….js:3)
> at y (vendor-b25c8db….js:19)
> at b (vendor-b25c8db….js:19)
> at g (vendor-b25c8db….js:19)
> at vendor-b25c8db….js:13
> at invoke (vendor-b25c8db….js:5)
> at n.flush (vendor-b25c8db….js:5)
> {code}
> Facing the same issue while importing the asset from hdfs as well.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (AMBARI-20381) User is not able to import workflows, coordinators and bundles
[
https://issues.apache.org/jira/browse/AMBARI-20381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Padma Priya Nagaraj reassigned AMBARI-20381:
Assignee: Padma Priya Nagaraj
> User is not able to import workflows, coordinators and bundles
> --
>
> Key: AMBARI-20381
> URL: https://issues.apache.org/jira/browse/AMBARI-20381
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: Padma Priya Nagaraj
>Priority: Blocker
> Labels: WFD, WFM
> Fix For: 2.5.0
>
>
> User is not able to import workflows, coordinators and bundles. Seeing below
> error in UI console.log
> {code}
> TypeError: Cannot read property 'workflow-app' of null
> at n.processWorkflowXml (oozie-designer-89dda89….js:9)
> at n.importWorkflow (oozie-designer-89dda89….js:9)
> at n.importWorkflowFromString (oozie-designer-89dda89….js:3)
> at n. (oozie-designer-89dda89….js:3)
> at y (vendor-b25c8db….js:19)
> at b (vendor-b25c8db….js:19)
> at g (vendor-b25c8db….js:19)
> at vendor-b25c8db….js:13
> at invoke (vendor-b25c8db….js:5)
> at n.flush (vendor-b25c8db….js:5)
> {code}
> Facing the same issue while importing the asset from hdfs as well.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20342) WFM:Performance improvement for adding node on a decision node in large workflow.
[ https://issues.apache.org/jira/browse/AMBARI-20342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20342: - Attachment: AMBARI-20342_trunk.patch > WFM:Performance improvement for adding node on a decision node in large > workflow. > - > > Key: AMBARI-20342 > URL: https://issues.apache.org/jira/browse/AMBARI-20342 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20342_trunk.patch > > > Performance improvement on adding node to large workflow on lower part of > decision path. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20342) WFM:Performance improvement for adding node on a decision node in large workflow.
[ https://issues.apache.org/jira/browse/AMBARI-20342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20342: - Status: Patch Available (was: Open) > WFM:Performance improvement for adding node on a decision node in large > workflow. > - > > Key: AMBARI-20342 > URL: https://issues.apache.org/jira/browse/AMBARI-20342 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20342_trunk.patch > > > Performance improvement on adding node to large workflow on lower part of > decision path. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20342) WFM:Performance improvement for adding node on a decision node in large workflow.
Padma Priya Nagaraj created AMBARI-20342: Summary: WFM:Performance improvement for adding node on a decision node in large workflow. Key: AMBARI-20342 URL: https://issues.apache.org/jira/browse/AMBARI-20342 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Padma Priya Nagaraj Assignee: Padma Priya Nagaraj Priority: Critical Fix For: 2.5.0 Performance improvement on adding node to large workflow on lower part of decision path. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20296) Workflow Manger support for pointing to kill node in decision editor.
[ https://issues.apache.org/jira/browse/AMBARI-20296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20296: - Status: Patch Available (was: Open) > Workflow Manger support for pointing to kill node in decision editor. > -- > > Key: AMBARI-20296 > URL: https://issues.apache.org/jira/browse/AMBARI-20296 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20296_trunk.patch > > > Workflow Manger support for pointing to kill node in decision editor.. > In decision editor , the user should be able to point to a different node for > a condition than the pre configured ones. > Also in case of condition-node combination pointing to an structural error in > workflow, user should be warned . -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20296) Workflow Manger support for pointing to kill node in decision editor.
[ https://issues.apache.org/jira/browse/AMBARI-20296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20296: - Attachment: AMBARI-20296_trunk.patch > Workflow Manger support for pointing to kill node in decision editor. > -- > > Key: AMBARI-20296 > URL: https://issues.apache.org/jira/browse/AMBARI-20296 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20296_trunk.patch > > > Workflow Manger support for pointing to kill node in decision editor.. > In decision editor , the user should be able to point to a different node for > a condition than the pre configured ones. > Also in case of condition-node combination pointing to an structural error in > workflow, user should be warned . -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20296) Workflow Manger support for pointing to kill node in decision editor.
Padma Priya Nagaraj created AMBARI-20296: Summary: Workflow Manger support for pointing to kill node in decision editor. Key: AMBARI-20296 URL: https://issues.apache.org/jira/browse/AMBARI-20296 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Padma Priya Nagaraj Assignee: Padma Priya Nagaraj Fix For: 2.5.0 Workflow Manger support for pointing to kill node in decision editor.. In decision editor , the user should be able to point to a different node for a condition than the pre configured ones. Also in case of condition-node combination pointing to an structural error in workflow, user should be warned . -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20268) WFM generates duplicate kill nodes in XML if decision paths have multiple transition to kill node.
[ https://issues.apache.org/jira/browse/AMBARI-20268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20268: - Attachment: AMBARI-20268_trunk.patch > WFM generates duplicate kill nodes in XML if decision paths have multiple > transition to kill node. > -- > > Key: AMBARI-20268 > URL: https://issues.apache.org/jira/browse/AMBARI-20268 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20268_trunk.patch > > > The generate XML contains duplicate kill nodes if decision paths have > multiple transition to kill node. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20268) WFM generates duplicate kill nodes in XML if decision paths have multiple transition to kill node.
Padma Priya Nagaraj created AMBARI-20268: Summary: WFM generates duplicate kill nodes in XML if decision paths have multiple transition to kill node. Key: AMBARI-20268 URL: https://issues.apache.org/jira/browse/AMBARI-20268 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Padma Priya Nagaraj Assignee: Padma Priya Nagaraj Fix For: 2.5.0 The generate XML contains duplicate kill nodes if decision paths have multiple transition to kill node. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20266) Duplicate node error is shown if kill node transition exists from decision node in WFM
[ https://issues.apache.org/jira/browse/AMBARI-20266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20266: - Status: Patch Available (was: In Progress) > Duplicate node error is shown if kill node transition exists from decision > node in WFM > -- > > Key: AMBARI-20266 > URL: https://issues.apache.org/jira/browse/AMBARI-20266 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20266_trunk.patch > > > If there's a transition to kill node from a decision node, node already > exists error is shown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20266) Duplicate node error is shown if kill node transition exists from decision node in WFM
[ https://issues.apache.org/jira/browse/AMBARI-20266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20266: - Attachment: AMBARI-20266_trunk.patch > Duplicate node error is shown if kill node transition exists from decision > node in WFM > -- > > Key: AMBARI-20266 > URL: https://issues.apache.org/jira/browse/AMBARI-20266 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20266_trunk.patch > > > If there's a transition to kill node from a decision node, node already > exists error is shown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20266) Duplicate node error is shown if kill node transition exists from decision node in WFM
Padma Priya Nagaraj created AMBARI-20266: Summary: Duplicate node error is shown if kill node transition exists from decision node in WFM Key: AMBARI-20266 URL: https://issues.apache.org/jira/browse/AMBARI-20266 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Padma Priya Nagaraj Assignee: Padma Priya Nagaraj Fix For: 2.5.0 If there's a transition to kill node from a decision node, node already exists error is shown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20246) Not able to preview the xml for coordinator
[ https://issues.apache.org/jira/browse/AMBARI-20246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20246: - Status: Patch Available (was: Open) > Not able to preview the xml for coordinator > --- > > Key: AMBARI-20246 > URL: https://issues.apache.org/jira/browse/AMBARI-20246 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Padma Priya Nagaraj >Priority: Blocker > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20246_trunk.patch > > > Issue 1: > Not able to preview the xml for coordinator. I am not seeing any error in UI > console log. > Steps to reproduce : > 1) Import the coordinator. > 2) Import the coordinator. > 3) Try to preview the coordinator and UI is not showing preview. > Issue 2: > After issue 1 is encountered, if user tries to perform any other operations, > then UI is getting hung. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20246) Not able to preview the xml for coordinator
[ https://issues.apache.org/jira/browse/AMBARI-20246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20246: - Attachment: AMBARI-20246_trunk.patch > Not able to preview the xml for coordinator > --- > > Key: AMBARI-20246 > URL: https://issues.apache.org/jira/browse/AMBARI-20246 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Padma Priya Nagaraj >Priority: Blocker > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20246_trunk.patch > > > Issue 1: > Not able to preview the xml for coordinator. I am not seeing any error in UI > console log. > Steps to reproduce : > 1) Import the coordinator. > 2) Import the coordinator. > 3) Try to preview the coordinator and UI is not showing preview. > Issue 2: > After issue 1 is encountered, if user tries to perform any other operations, > then UI is getting hung. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20246) Not able to preview the xml for coordinator
[ https://issues.apache.org/jira/browse/AMBARI-20246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj reassigned AMBARI-20246: Assignee: Padma Priya Nagaraj > Not able to preview the xml for coordinator > --- > > Key: AMBARI-20246 > URL: https://issues.apache.org/jira/browse/AMBARI-20246 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Padma Priya Nagaraj >Priority: Blocker > Labels: WFD, WFM > Fix For: 2.5.0 > > > Issue 1: > Not able to preview the xml for coordinator. I am not seeing any error in UI > console log. > Steps to reproduce : > 1) Import the coordinator. > 2) Import the coordinator. > 3) Try to preview the coordinator and UI is not showing preview. > Issue 2: > After issue 1 is encountered, if user tries to perform any other operations, > then UI is getting hung. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20206) Workflow manager is allowing to have empty action node
[ https://issues.apache.org/jira/browse/AMBARI-20206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20206: - Attachment: AMBARI-20206_trunk.patch > Workflow manager is allowing to have empty action node > -- > > Key: AMBARI-20206 > URL: https://issues.apache.org/jira/browse/AMBARI-20206 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20206_trunk.patch > > > Workflow manager is allowing to have empty action node. > Steps to reproduce : > 1) Add a new node to the workflow > 2) Delete node name and keep it empty. > 3) Workflow manager is not complaining about empty node name. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20206) Workflow manager is allowing to have empty action node
[ https://issues.apache.org/jira/browse/AMBARI-20206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20206: - Status: Patch Available (was: Open) > Workflow manager is allowing to have empty action node > -- > > Key: AMBARI-20206 > URL: https://issues.apache.org/jira/browse/AMBARI-20206 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20206_trunk.patch > > > Workflow manager is allowing to have empty action node. > Steps to reproduce : > 1) Add a new node to the workflow > 2) Delete node name and keep it empty. > 3) Workflow manager is not complaining about empty node name. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20131) Workflow details are lost upon refreshing the browser
[ https://issues.apache.org/jira/browse/AMBARI-20131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20131: - Status: Patch Available (was: Open) > Workflow details are lost upon refreshing the browser > - > > Key: AMBARI-20131 > URL: https://issues.apache.org/jira/browse/AMBARI-20131 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Padma Priya Nagaraj >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20131_trunk.patch > > > Workflow details are lost upon refreshing the browser. > Steps to reproduce : > 1) Create a new workflow. > 2) Now refresh the browser. > 3) Upon refreshing, the previous workflow tab is not displayed and all the > unsaved works are lost. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20131) Workflow details are lost upon refreshing the browser
[ https://issues.apache.org/jira/browse/AMBARI-20131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20131: - Attachment: AMBARI-20131_trunk.patch > Workflow details are lost upon refreshing the browser > - > > Key: AMBARI-20131 > URL: https://issues.apache.org/jira/browse/AMBARI-20131 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Padma Priya Nagaraj >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20131_trunk.patch > > > Workflow details are lost upon refreshing the browser. > Steps to reproduce : > 1) Create a new workflow. > 2) Now refresh the browser. > 3) Upon refreshing, the previous workflow tab is not displayed and all the > unsaved works are lost. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20131) Workflow details are lost upon refreshing the browser
[ https://issues.apache.org/jira/browse/AMBARI-20131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj reassigned AMBARI-20131: Assignee: Padma Priya Nagaraj > Workflow details are lost upon refreshing the browser > - > > Key: AMBARI-20131 > URL: https://issues.apache.org/jira/browse/AMBARI-20131 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Padma Priya Nagaraj >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > > Workflow details are lost upon refreshing the browser. > Steps to reproduce : > 1) Create a new workflow. > 2) Now refresh the browser. > 3) Upon refreshing, the previous workflow tab is not displayed and all the > unsaved works are lost. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20166) Workflow Manager. Nominal time should accept variables.
[ https://issues.apache.org/jira/browse/AMBARI-20166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20166: - Status: Patch Available (was: Open) > Workflow Manager. Nominal time should accept variables. > --- > > Key: AMBARI-20166 > URL: https://issues.apache.org/jira/browse/AMBARI-20166 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Belliraj HB >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20166_trunk.patch > > > Workflow Manager. Nominal time should accept variables. > currently nominal time accepts time only from date picker. it should allow > user to enter variables as wel. > Reported by ArtemErvits -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20166) Workflow Manager. Nominal time should accept variables.
[ https://issues.apache.org/jira/browse/AMBARI-20166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20166: - Attachment: AMBARI-20166_trunk.patch > Workflow Manager. Nominal time should accept variables. > --- > > Key: AMBARI-20166 > URL: https://issues.apache.org/jira/browse/AMBARI-20166 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Belliraj HB >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20166_trunk.patch > > > Workflow Manager. Nominal time should accept variables. > currently nominal time accepts time only from date picker. it should allow > user to enter variables as wel. > Reported by ArtemErvits -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20166) Workflow Manager. Nominal time should accept variables.
[ https://issues.apache.org/jira/browse/AMBARI-20166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20166: - Attachment: (was: AMBARI-20166_trunk.patch) > Workflow Manager. Nominal time should accept variables. > --- > > Key: AMBARI-20166 > URL: https://issues.apache.org/jira/browse/AMBARI-20166 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Belliraj HB >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > > Workflow Manager. Nominal time should accept variables. > currently nominal time accepts time only from date picker. it should allow > user to enter variables as wel. > Reported by ArtemErvits -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20166) Workflow Manager. Nominal time should accept variables.
[ https://issues.apache.org/jira/browse/AMBARI-20166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20166: - Attachment: AMBARI-20166_trunk.patch > Workflow Manager. Nominal time should accept variables. > --- > > Key: AMBARI-20166 > URL: https://issues.apache.org/jira/browse/AMBARI-20166 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Belliraj HB >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20166_trunk.patch > > > Workflow Manager. Nominal time should accept variables. > currently nominal time accepts time only from date picker. it should allow > user to enter variables as wel. > Reported by ArtemErvits -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20166) Workflow Manager. Nominal time should accept variables.
[ https://issues.apache.org/jira/browse/AMBARI-20166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20166: - Attachment: (was: AMBARI-20166_trunk.patch) > Workflow Manager. Nominal time should accept variables. > --- > > Key: AMBARI-20166 > URL: https://issues.apache.org/jira/browse/AMBARI-20166 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Belliraj HB >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > > Workflow Manager. Nominal time should accept variables. > currently nominal time accepts time only from date picker. it should allow > user to enter variables as wel. > Reported by ArtemErvits -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20166) Workflow Manager. Nominal time should accept variables.
[ https://issues.apache.org/jira/browse/AMBARI-20166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20166: - Attachment: AMBARI-20166_trunk.patch > Workflow Manager. Nominal time should accept variables. > --- > > Key: AMBARI-20166 > URL: https://issues.apache.org/jira/browse/AMBARI-20166 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Belliraj HB >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20166_trunk.patch > > > Workflow Manager. Nominal time should accept variables. > currently nominal time accepts time only from date picker. it should allow > user to enter variables as wel. > Reported by ArtemErvits -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20164) Kill a workflow jumps to another tab in WFM
Padma Priya Nagaraj created AMBARI-20164: Summary: Kill a workflow jumps to another tab in WFM Key: AMBARI-20164 URL: https://issues.apache.org/jira/browse/AMBARI-20164 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Padma Priya Nagaraj Assignee: Padma Priya Nagaraj Priority: Critical Fix For: 2.5.0 Steps: 1. log into ambari ui 2. go to wfm 3. select an existing workflow. e.g.Workflow10 4. choose edit workflow 5. choose the "dashboard" tab to go back to the workflow list 6. select the existing workflow and choose "action->kill" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20164) Kill a workflow jumps to another tab in WFM
[ https://issues.apache.org/jira/browse/AMBARI-20164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20164: - Status: Patch Available (was: Open) > Kill a workflow jumps to another tab in WFM > --- > > Key: AMBARI-20164 > URL: https://issues.apache.org/jira/browse/AMBARI-20164 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20164_trunk.patch > > > Steps: > 1. log into ambari ui > 2. go to wfm > 3. select an existing workflow. e.g.Workflow10 > 4. choose edit workflow > 5. choose the "dashboard" tab to go back to the workflow list > 6. select the existing workflow and choose "action->kill" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20164) Kill a workflow jumps to another tab in WFM
[ https://issues.apache.org/jira/browse/AMBARI-20164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20164: - Attachment: AMBARI-20164_trunk.patch > Kill a workflow jumps to another tab in WFM > --- > > Key: AMBARI-20164 > URL: https://issues.apache.org/jira/browse/AMBARI-20164 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20164_trunk.patch > > > Steps: > 1. log into ambari ui > 2. go to wfm > 3. select an existing workflow. e.g.Workflow10 > 4. choose edit workflow > 5. choose the "dashboard" tab to go back to the workflow list > 6. select the existing workflow and choose "action->kill" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20161) Workflow Manager-mapred action contains duplicates in editor if user saves and reopens editor
[ https://issues.apache.org/jira/browse/AMBARI-20161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20161: - Status: Patch Available (was: Open) > Workflow Manager-mapred action contains duplicates in editor if user saves > and reopens editor > - > > Key: AMBARI-20161 > URL: https://issues.apache.org/jira/browse/AMBARI-20161 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Belliraj HB >Assignee: Padma Priya Nagaraj >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20161_trunk.patch > > > Open a Map-Red editor. > Fill in details and Save. > Reopen the editor. you will see the configuration in both general and > advanced section. > Preview xml looks fine though. > Expected: > the configuration should be not duplicated. > Reported by ArtemErvits -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20161) Workflow Manager-mapred action contains duplicates in editor if user saves and reopens editor
[ https://issues.apache.org/jira/browse/AMBARI-20161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20161: - Attachment: AMBARI-20161_trunk.patch > Workflow Manager-mapred action contains duplicates in editor if user saves > and reopens editor > - > > Key: AMBARI-20161 > URL: https://issues.apache.org/jira/browse/AMBARI-20161 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Belliraj HB >Assignee: Padma Priya Nagaraj >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20161_trunk.patch > > > Open a Map-Red editor. > Fill in details and Save. > Reopen the editor. you will see the configuration in both general and > advanced section. > Preview xml looks fine though. > Expected: > the configuration should be not duplicated. > Reported by ArtemErvits -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20161) Workflow Manager-mapred action contains duplicates in editor if user saves and reopens editor
[ https://issues.apache.org/jira/browse/AMBARI-20161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20161: - Summary: Workflow Manager-mapred action contains duplicates in editor if user saves and reopens editor (was: Workflow Manager-mapred action contains duplicates in editor if user saves and reopen editor) > Workflow Manager-mapred action contains duplicates in editor if user saves > and reopens editor > - > > Key: AMBARI-20161 > URL: https://issues.apache.org/jira/browse/AMBARI-20161 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Belliraj HB >Assignee: Padma Priya Nagaraj >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > > Open a Map-Red editor. > Fill in details and Save. > Reopen the editor. you will see the configuration in both general and > advanced section. > Preview xml looks fine though. > Expected: > the configuration should be not duplicated. > Reported by ArtemErvits -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20141) Command text lost when toggling from Command to Args on sqoop in Workflow manager.
[ https://issues.apache.org/jira/browse/AMBARI-20141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20141: - Status: Patch Available (was: Open) > Command text lost when toggling from Command to Args on sqoop in Workflow > manager. > -- > > Key: AMBARI-20141 > URL: https://issues.apache.org/jira/browse/AMBARI-20141 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20141_trunk.patch > > > Command text lost when toggling from Command to Args on sqoop action. > Pressing cancel and opening the configure dialog again restores the settings > but this is inconvenient if you had several changes or you haven’t saved the > settings yet. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20141) Command text lost when toggling from Command to Args on sqoop in Workflow manager.
[ https://issues.apache.org/jira/browse/AMBARI-20141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20141: - Attachment: AMBARI-20141_trunk.patch > Command text lost when toggling from Command to Args on sqoop in Workflow > manager. > -- > > Key: AMBARI-20141 > URL: https://issues.apache.org/jira/browse/AMBARI-20141 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20141_trunk.patch > > > Command text lost when toggling from Command to Args on sqoop action. > Pressing cancel and opening the configure dialog again restores the settings > but this is inconvenient if you had several changes or you haven’t saved the > settings yet. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20141) Command text lost when toggling from Command to Args on sqoop in Workflow manager.
Padma Priya Nagaraj created AMBARI-20141: Summary: Command text lost when toggling from Command to Args on sqoop in Workflow manager. Key: AMBARI-20141 URL: https://issues.apache.org/jira/browse/AMBARI-20141 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Padma Priya Nagaraj Assignee: Padma Priya Nagaraj Fix For: 2.5.0 Command text lost when toggling from Command to Args on sqoop action. Pressing cancel and opening the configure dialog again restores the settings but this is inconvenient if you had several changes or you haven’t saved the settings yet. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20107) Action node shows unsupported properties even though there are none in workflow manager.
[ https://issues.apache.org/jira/browse/AMBARI-20107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20107: - Attachment: AMBARI-20107_trunk.patch > Action node shows unsupported properties even though there are none in > workflow manager. > > > Key: AMBARI-20107 > URL: https://issues.apache.org/jira/browse/AMBARI-20107 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20107_trunk.patch > > > Action node during edit shows unsupported properties. But in unsupported > properties you see empty text. > Expected. > Unsupported properties should not be shown if there are no unsupported > properties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20107) Action node shows unsupported properties even though there are none in workflow manager.
[ https://issues.apache.org/jira/browse/AMBARI-20107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20107: - Attachment: (was: AMBARI-20107_trunk.patch) > Action node shows unsupported properties even though there are none in > workflow manager. > > > Key: AMBARI-20107 > URL: https://issues.apache.org/jira/browse/AMBARI-20107 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20107_trunk.patch > > > Action node during edit shows unsupported properties. But in unsupported > properties you see empty text. > Expected. > Unsupported properties should not be shown if there are no unsupported > properties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20107) Action node shows unsupported properties even though there are none in workflow manager.
[ https://issues.apache.org/jira/browse/AMBARI-20107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20107: - Status: Patch Available (was: Open) > Action node shows unsupported properties even though there are none in > workflow manager. > > > Key: AMBARI-20107 > URL: https://issues.apache.org/jira/browse/AMBARI-20107 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20107_trunk.patch > > > Action node during edit shows unsupported properties. But in unsupported > properties you see empty text. > Expected. > Unsupported properties should not be shown if there are no unsupported > properties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20107) Action node shows unsupported properties even though there are none in workflow manager.
[ https://issues.apache.org/jira/browse/AMBARI-20107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20107: - Attachment: AMBARI-20107_trunk.patch > Action node shows unsupported properties even though there are none in > workflow manager. > > > Key: AMBARI-20107 > URL: https://issues.apache.org/jira/browse/AMBARI-20107 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20107_trunk.patch > > > Action node during edit shows unsupported properties. But in unsupported > properties you see empty text. > Expected. > Unsupported properties should not be shown if there are no unsupported > properties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20107) Action node shows unsupported properties even though there are none in workflow manager.
Padma Priya Nagaraj created AMBARI-20107: Summary: Action node shows unsupported properties even though there are none in workflow manager. Key: AMBARI-20107 URL: https://issues.apache.org/jira/browse/AMBARI-20107 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Padma Priya Nagaraj Assignee: Padma Priya Nagaraj Fix For: 2.5.0 Action node during edit shows unsupported properties. But in unsupported properties you see empty text. Expected. Unsupported properties should not be shown if there are no unsupported properties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20090) On submit of bundle, if any coordinator path contains variables, user should be notified about custom variables.
[ https://issues.apache.org/jira/browse/AMBARI-20090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20090: - Status: Patch Available (was: Open) > On submit of bundle, if any coordinator path contains variables, user should > be notified about custom variables. > > > Key: AMBARI-20090 > URL: https://issues.apache.org/jira/browse/AMBARI-20090 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20090_trunk.patch > > > If there is a variable in file path, it becomes difficult to deduce variables > as we don't know the actual workflow that the bundle or coordinator uses. The > fix is to just prompt the user the variables cannot be auto detected as path > is not known. > In bundle submit, we parse though all coordinator paths and their respective > workflows to find the variables to be entered. But in case any of these paths > contain "variable" section,WFD wont be able to auto prompt these variables . > In this scenario, WFD has to notify the user to fill the variables manually > using custom variables. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20090) On submit of bundle, if any coordinator path contains variables, user should be notified about custom variables.
[ https://issues.apache.org/jira/browse/AMBARI-20090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20090: - Attachment: AMBARI-20090_trunk.patch > On submit of bundle, if any coordinator path contains variables, user should > be notified about custom variables. > > > Key: AMBARI-20090 > URL: https://issues.apache.org/jira/browse/AMBARI-20090 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20090_trunk.patch > > > If there is a variable in file path, it becomes difficult to deduce variables > as we don't know the actual workflow that the bundle or coordinator uses. The > fix is to just prompt the user the variables cannot be auto detected as path > is not known. > In bundle submit, we parse though all coordinator paths and their respective > workflows to find the variables to be entered. But in case any of these paths > contain "variable" section,WFD wont be able to auto prompt these variables . > In this scenario, WFD has to notify the user to fill the variables manually > using custom variables. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20090) On submit of bundle, if any coordinator path contains variables, user should be notified about custom variables.
Padma Priya Nagaraj created AMBARI-20090: Summary: On submit of bundle, if any coordinator path contains variables, user should be notified about custom variables. Key: AMBARI-20090 URL: https://issues.apache.org/jira/browse/AMBARI-20090 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Padma Priya Nagaraj Assignee: Padma Priya Nagaraj Fix For: 2.5.0 If there is a variable in file path, it becomes difficult to deduce variables as we don't know the actual workflow that the bundle or coordinator uses. The fix is to just prompt the user the variables cannot be auto detected as path is not known. In bundle submit, we parse though all coordinator paths and their respective workflows to find the variables to be entered. But in case any of these paths contain "variable" section,WFD wont be able to auto prompt these variables . In this scenario, WFD has to notify the user to fill the variables manually using custom variables. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20084) Cut Node feature is broken in workflow manager
[
https://issues.apache.org/jira/browse/AMBARI-20084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Padma Priya Nagaraj updated AMBARI-20084:
-
Status: Patch Available (was: Open)
> Cut Node feature is broken in workflow manager
> --
>
> Key: AMBARI-20084
> URL: https://issues.apache.org/jira/browse/AMBARI-20084
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: Padma Priya Nagaraj
>Priority: Critical
> Labels: WFD, WFM
> Fix For: 2.5.0
>
> Attachments: AMBARI-20084_trunk.patch
>
>
> Cut Node feature is broken in workflow manager. While cutting the node I am
> seeing below error in UI console.
> {code}
> TypeError: t is undefined
> d<.deleteNode()
> oozie-designer-67b1e2c50d1397066ce78c6858be68c4.js:9
> e.default<.deleteWorkflowNode()
> oozie-designer-67b1e2c50d1397066ce78c6858be68c4.js:3
> e.default<.cutNode()
> oozie-designer-67b1e2c50d1397066ce78c6858be68c4.js:3
> a<._addEvents/<()
> oozie-designer-67b1e2c50d1397066ce78c6858be68c4.js:8
> J.event.dispatch()
> vendor-415a6fd6db11ecd27aa07f5115312174.js:4
> J.event.add/g.handle()
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20084) Cut Node feature is broken in workflow manager
[
https://issues.apache.org/jira/browse/AMBARI-20084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Padma Priya Nagaraj updated AMBARI-20084:
-
Attachment: AMBARI-20084_trunk.patch
> Cut Node feature is broken in workflow manager
> --
>
> Key: AMBARI-20084
> URL: https://issues.apache.org/jira/browse/AMBARI-20084
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: Padma Priya Nagaraj
>Priority: Critical
> Labels: WFD, WFM
> Fix For: 2.5.0
>
> Attachments: AMBARI-20084_trunk.patch
>
>
> Cut Node feature is broken in workflow manager. While cutting the node I am
> seeing below error in UI console.
> {code}
> TypeError: t is undefined
> d<.deleteNode()
> oozie-designer-67b1e2c50d1397066ce78c6858be68c4.js:9
> e.default<.deleteWorkflowNode()
> oozie-designer-67b1e2c50d1397066ce78c6858be68c4.js:3
> e.default<.cutNode()
> oozie-designer-67b1e2c50d1397066ce78c6858be68c4.js:3
> a<._addEvents/<()
> oozie-designer-67b1e2c50d1397066ce78c6858be68c4.js:8
> J.event.dispatch()
> vendor-415a6fd6db11ecd27aa07f5115312174.js:4
> J.event.add/g.handle()
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (AMBARI-20084) Cut Node feature is broken in workflow manager
[
https://issues.apache.org/jira/browse/AMBARI-20084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Padma Priya Nagaraj reassigned AMBARI-20084:
Assignee: Padma Priya Nagaraj
> Cut Node feature is broken in workflow manager
> --
>
> Key: AMBARI-20084
> URL: https://issues.apache.org/jira/browse/AMBARI-20084
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: Padma Priya Nagaraj
>Priority: Critical
> Labels: WFD, WFM
> Fix For: 2.5.0
>
>
> Cut Node feature is broken in workflow manager. While cutting the node I am
> seeing below error in UI console.
> {code}
> TypeError: t is undefined
> d<.deleteNode()
> oozie-designer-67b1e2c50d1397066ce78c6858be68c4.js:9
> e.default<.deleteWorkflowNode()
> oozie-designer-67b1e2c50d1397066ce78c6858be68c4.js:3
> e.default<.cutNode()
> oozie-designer-67b1e2c50d1397066ce78c6858be68c4.js:3
> a<._addEvents/<()
> oozie-designer-67b1e2c50d1397066ce78c6858be68c4.js:8
> J.event.dispatch()
> vendor-415a6fd6db11ecd27aa07f5115312174.js:4
> J.event.add/g.handle()
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20080) WFM does not issue confirmation message when workflow is suspended or killed
[ https://issues.apache.org/jira/browse/AMBARI-20080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20080: - Status: Patch Available (was: Open) > WFM does not issue confirmation message when workflow is suspended or killed > > > Key: AMBARI-20080 > URL: https://issues.apache.org/jira/browse/AMBARI-20080 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20080_trunk.patch > > > Steps: > 1. log into ambari ui > 2. go to wfm > 3. upload workflow from file system: > 4. submit the workflow > 5. kill or suspend the workflow from WFM ui > Issue: > workflow ui is not giving any confirmation message when wf is killed or > suspended -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20080) WFM does not issue confirmation message when workflow is suspended or killed
[ https://issues.apache.org/jira/browse/AMBARI-20080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20080: - Attachment: AMBARI-20080_trunk.patch > WFM does not issue confirmation message when workflow is suspended or killed > > > Key: AMBARI-20080 > URL: https://issues.apache.org/jira/browse/AMBARI-20080 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20080_trunk.patch > > > Steps: > 1. log into ambari ui > 2. go to wfm > 3. upload workflow from file system: > 4. submit the workflow > 5. kill or suspend the workflow from WFM ui > Issue: > workflow ui is not giving any confirmation message when wf is killed or > suspended -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20079) Unable to filter by job id
[ https://issues.apache.org/jira/browse/AMBARI-20079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20079: - Status: Patch Available (was: Open) > Unable to filter by job id > -- > > Key: AMBARI-20079 > URL: https://issues.apache.org/jira/browse/AMBARI-20079 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20079_trunk.patch, Screen Shot 2017-02-16.png > > > After attempting to resume a random SUSPENDED existing workflow > 078-170215133231623-oozie-oozi-W (ran by the nightly system tests via > hrt_qa user), the workflow went into RUNNING state. I wanted to see that > workflow by itself on the dashboard, so I used filter criteria with the > following syntax: > jobid=078-170215133231623-oozie-oozi-W > jobid:078-170215133231623-oozie-oozi-W > The first one returned: > Remote api failed > The second one showed the same error message but also a perptual animated > busy loading icon. > I expected that if my syntax was incorrect, it would say so like "jobid:..." > is not correct, do you mean "Job Id=" or something to that effect. Also, for > the second case, there should be a fast fail, rather than a perpetual hanging. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20080) WFM does not issue confirmation message when workflow is suspended or killed
Padma Priya Nagaraj created AMBARI-20080: Summary: WFM does not issue confirmation message when workflow is suspended or killed Key: AMBARI-20080 URL: https://issues.apache.org/jira/browse/AMBARI-20080 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Padma Priya Nagaraj Assignee: Padma Priya Nagaraj Priority: Critical Fix For: 2.5.0 Steps: 1. log into ambari ui 2. go to wfm 3. upload workflow from file system: 4. submit the workflow 5. kill or suspend the workflow from WFM ui Issue: workflow ui is not giving any confirmation message when wf is killed or suspended -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20079) Unable to filter by job id
[ https://issues.apache.org/jira/browse/AMBARI-20079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20079: - Labels: WFD WFM (was: ) > Unable to filter by job id > -- > > Key: AMBARI-20079 > URL: https://issues.apache.org/jira/browse/AMBARI-20079 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20079_trunk.patch, Screen Shot 2017-02-16.png > > > After attempting to resume a random SUSPENDED existing workflow > 078-170215133231623-oozie-oozi-W (ran by the nightly system tests via > hrt_qa user), the workflow went into RUNNING state. I wanted to see that > workflow by itself on the dashboard, so I used filter criteria with the > following syntax: > jobid=078-170215133231623-oozie-oozi-W > jobid:078-170215133231623-oozie-oozi-W > The first one returned: > Remote api failed > The second one showed the same error message but also a perptual animated > busy loading icon. > I expected that if my syntax was incorrect, it would say so like "jobid:..." > is not correct, do you mean "Job Id=" or something to that effect. Also, for > the second case, there should be a fast fail, rather than a perpetual hanging. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20079) Unable to filter by job id
[ https://issues.apache.org/jira/browse/AMBARI-20079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20079: - Attachment: AMBARI-20079_trunk.patch > Unable to filter by job id > -- > > Key: AMBARI-20079 > URL: https://issues.apache.org/jira/browse/AMBARI-20079 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20079_trunk.patch, Screen Shot 2017-02-16.png > > > After attempting to resume a random SUSPENDED existing workflow > 078-170215133231623-oozie-oozi-W (ran by the nightly system tests via > hrt_qa user), the workflow went into RUNNING state. I wanted to see that > workflow by itself on the dashboard, so I used filter criteria with the > following syntax: > jobid=078-170215133231623-oozie-oozi-W > jobid:078-170215133231623-oozie-oozi-W > The first one returned: > Remote api failed > The second one showed the same error message but also a perptual animated > busy loading icon. > I expected that if my syntax was incorrect, it would say so like "jobid:..." > is not correct, do you mean "Job Id=" or something to that effect. Also, for > the second case, there should be a fast fail, rather than a perpetual hanging. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20079) Unable to filter by job id
[ https://issues.apache.org/jira/browse/AMBARI-20079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20079: - Attachment: Screen Shot 2017-02-16.png > Unable to filter by job id > -- > > Key: AMBARI-20079 > URL: https://issues.apache.org/jira/browse/AMBARI-20079 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj >Priority: Critical > Fix For: 2.5.0 > > Attachments: Screen Shot 2017-02-16.png > > > After attempting to resume a random SUSPENDED existing workflow > 078-170215133231623-oozie-oozi-W (ran by the nightly system tests via > hrt_qa user), the workflow went into RUNNING state. I wanted to see that > workflow by itself on the dashboard, so I used filter criteria with the > following syntax: > jobid=078-170215133231623-oozie-oozi-W > jobid:078-170215133231623-oozie-oozi-W > The first one returned: > Remote api failed > The second one showed the same error message but also a perptual animated > busy loading icon. > I expected that if my syntax was incorrect, it would say so like "jobid:..." > is not correct, do you mean "Job Id=" or something to that effect. Also, for > the second case, there should be a fast fail, rather than a perpetual hanging. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20079) Unable to filter by job id
Padma Priya Nagaraj created AMBARI-20079: Summary: Unable to filter by job id Key: AMBARI-20079 URL: https://issues.apache.org/jira/browse/AMBARI-20079 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Padma Priya Nagaraj Assignee: Padma Priya Nagaraj Priority: Critical Fix For: 2.5.0 After attempting to resume a random SUSPENDED existing workflow 078-170215133231623-oozie-oozi-W (ran by the nightly system tests via hrt_qa user), the workflow went into RUNNING state. I wanted to see that workflow by itself on the dashboard, so I used filter criteria with the following syntax: jobid=078-170215133231623-oozie-oozi-W jobid:078-170215133231623-oozie-oozi-W The first one returned: Remote api failed The second one showed the same error message but also a perptual animated busy loading icon. I expected that if my syntax was incorrect, it would say so like "jobid:..." is not correct, do you mean "Job Id=" or something to that effect. Also, for the second case, there should be a fast fail, rather than a perpetual hanging. LOGS: http://qelog.hortonworks.com/log/bugbash-r6-oozie-unsecure/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20079) Unable to filter by job id
[ https://issues.apache.org/jira/browse/AMBARI-20079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20079: - Description: After attempting to resume a random SUSPENDED existing workflow 078-170215133231623-oozie-oozi-W (ran by the nightly system tests via hrt_qa user), the workflow went into RUNNING state. I wanted to see that workflow by itself on the dashboard, so I used filter criteria with the following syntax: jobid=078-170215133231623-oozie-oozi-W jobid:078-170215133231623-oozie-oozi-W The first one returned: Remote api failed The second one showed the same error message but also a perptual animated busy loading icon. I expected that if my syntax was incorrect, it would say so like "jobid:..." is not correct, do you mean "Job Id=" or something to that effect. Also, for the second case, there should be a fast fail, rather than a perpetual hanging. was: After attempting to resume a random SUSPENDED existing workflow 078-170215133231623-oozie-oozi-W (ran by the nightly system tests via hrt_qa user), the workflow went into RUNNING state. I wanted to see that workflow by itself on the dashboard, so I used filter criteria with the following syntax: jobid=078-170215133231623-oozie-oozi-W jobid:078-170215133231623-oozie-oozi-W The first one returned: Remote api failed The second one showed the same error message but also a perptual animated busy loading icon. I expected that if my syntax was incorrect, it would say so like "jobid:..." is not correct, do you mean "Job Id=" or something to that effect. Also, for the second case, there should be a fast fail, rather than a perpetual hanging. LOGS: http://qelog.hortonworks.com/log/bugbash-r6-oozie-unsecure/ > Unable to filter by job id > -- > > Key: AMBARI-20079 > URL: https://issues.apache.org/jira/browse/AMBARI-20079 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj >Priority: Critical > Fix For: 2.5.0 > > > After attempting to resume a random SUSPENDED existing workflow > 078-170215133231623-oozie-oozi-W (ran by the nightly system tests via > hrt_qa user), the workflow went into RUNNING state. I wanted to see that > workflow by itself on the dashboard, so I used filter criteria with the > following syntax: > jobid=078-170215133231623-oozie-oozi-W > jobid:078-170215133231623-oozie-oozi-W > The first one returned: > Remote api failed > The second one showed the same error message but also a perptual animated > busy loading icon. > I expected that if my syntax was incorrect, it would say so like "jobid:..." > is not correct, do you mean "Job Id=" or something to that effect. Also, for > the second case, there should be a fast fail, rather than a perpetual hanging. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20078) When uploading a file using the WFM, need a message to say that either the file upload succeeded or failed
[ https://issues.apache.org/jira/browse/AMBARI-20078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20078: - Status: Patch Available (was: Open) > When uploading a file using the WFM, need a message to say that either the > file upload succeeded or failed > -- > > Key: AMBARI-20078 > URL: https://issues.apache.org/jira/browse/AMBARI-20078 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20078_trunk.patch > > > Steps to repo: > 1. Create a WF > 2. Add a java action > 3. Go to Advanced Properties, and under File - click on Browse and use the > File Browser to upload a file from local machine. > 4. Need to receive a message whether the file upload is successful or failed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20078) When uploading a file using the WFM, need a message to say that either the file upload succeeded or failed
[ https://issues.apache.org/jira/browse/AMBARI-20078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20078: - Attachment: AMBARI-20078_trunk.patch > When uploading a file using the WFM, need a message to say that either the > file upload succeeded or failed > -- > > Key: AMBARI-20078 > URL: https://issues.apache.org/jira/browse/AMBARI-20078 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20078_trunk.patch > > > Steps to repo: > 1. Create a WF > 2. Add a java action > 3. Go to Advanced Properties, and under File - click on Browse and use the > File Browser to upload a file from local machine. > 4. Need to receive a message whether the file upload is successful or failed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20078) When uploading a file using the WFM, need a message to say that either the file upload succeeded or failed
Padma Priya Nagaraj created AMBARI-20078: Summary: When uploading a file using the WFM, need a message to say that either the file upload succeeded or failed Key: AMBARI-20078 URL: https://issues.apache.org/jira/browse/AMBARI-20078 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Padma Priya Nagaraj Assignee: Padma Priya Nagaraj Priority: Critical Fix For: 2.5.0 Steps to repo: 1. Create a WF 2. Add a java action 3. Go to Advanced Properties, and under File - click on Browse and use the File Browser to upload a file from local machine. 4. Need to receive a message whether the file upload is successful or failed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
