[jira] [Resolved] (AMBARI-25424) Failed to edit workflow from Ambari workflow Manager while accessing Ambari UI over Knox
[
https://issues.apache.org/jira/browse/AMBARI-25424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
venkat resolved AMBARI-25424.
-
Resolution: Fixed
> Failed to edit workflow from Ambari workflow Manager while accessing Ambari
> UI over Knox
>
>
> Key: AMBARI-25424
> URL: https://issues.apache.org/jira/browse/AMBARI-25424
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.7.3
>Reporter: amarnath reddy pappu
>Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Ambari workflow manager view is accessed over knox, editing the workflow from
> the view will fail as knox fails to identify/parse the xml format.
> Exception in knox logs
> {code:java|bgColor=#f5f5f5}
> ==> gateway.log <==
> 2018-03-28 10:16:25,542 ERROR hadoop.gateway
> (AbstractGatewayFilter.java:doFilter(63)) - Failed to execute filter:
> com.fasterxml.jackson.core.JsonParseException: Unexpected character ('<'
> (code 60)): expected a valid value (number, String, array, object, 'true',
> 'false' or 'null')
> at [Source: java.io.InputStreamReader@254359d8; line: 1, column: 2]
> 2018-03-28 10:16:25,542 ERROR hadoop.gateway
> (AbstractGatewayFilter.java:doFilter(63)) - Failed to execute filter:
> com.fasterxml.jackson.core.JsonParseException: Unexpected character ('<'
> (code 60)): expected a valid value (number, String, array, object, 'true',
> 'false' or 'null')
> at [Source: java.io.InputStreamReader@254359d8; line: 1, column: 2]
> 2018-03-28 10:16:25,542 ERROR hadoop.gateway
> (AbstractGatewayFilter.java:doFilter(63)) - Failed to execute filter:
> com.fasterxml.jackson.core.JsonParseException: Unexpected character ('<'
> (code 60)): expected a valid value (number, String, array, object, 'true',
> 'false' or 'null')
> at [Source: java.io.InputStreamReader@254359d8; line: 1, column: 2]
> 2018-03-28 10:16:25,543 ERROR hadoop.gateway
> (GatewayFilter.java:doFilter(141)) - Gateway processing failed:
> com.fasterxml.jackson.core.JsonParseException: Unexpected character ('<'
> (code 60)): expected a valid value (number, String, array, object, 'true',
> 'false' or 'null')
> at [Source: java.io.InputStreamReader@254359d8; line: 1, column: 2]
> com.fasterxml.jackson.core.JsonParseException: Unexpected character ('<'
> (code 60)): expected a valid value (number, String, array, object, 'true',
> 'false' or 'null')
> at [Source: java.io.InputStreamReader@254359d8; line: 1, column: 2]
> at
> com.fasterxml.jackson.core.JsonParser._constructError(JsonParser.java:1369)
> at
> com.fasterxml.jackson.core.base.ParserMinimalBase._reportError(ParserMinimalBase.java:599)
> at
> com.fasterxml.jackson.core.base.ParserMinimalBase._reportUnexpectedChar(ParserMinimalBase.java:520)
> at
> com.fasterxml.jackson.core.json.ReaderBasedJsonParser._handleUnexpectedValue(ReaderBasedJsonParser.java:1379)
> at
> com.fasterxml.jackson.core.json.ReaderBasedJsonParser.nextToken(ReaderBasedJsonParser.java:669)
> at
> org.apache.hadoop.gateway.filter.rewrite.impl.json.JsonFilterReader.read(JsonFilterReader.java:89)
> at
> org.apache.hadoop.gateway.filter.rewrite.impl.json.JsonUrlRewriteFilterReader.read(JsonUrlRewriteFilterReader.java:32)
> at
> org.apache.commons.io.input.ReaderInputStream.fillBuffer(ReaderInputStream.java:198)
> at
> org.apache.commons.io.input.ReaderInputStream.read(ReaderInputStream.java:242)
> {code}
> {code:java|bgColor=#f5f5f5}
> ==> gateway-audit.log <==
> 18/03/28 10:16:25
> ||6e7f841c-3aa9-4d8f-a71f-bfbc6138dedf|audit|10.200.4.250|AMBARI|anonymous|||access|uri|/gateway/ui/ambari/api/v1/views/WORKFLOW_MANAGER/versions/1.0.0/instances/wfm/resources/proxy/readWorkflow?workflowPath=/user/admin/workflow.xml=WORKFLOW|failure|
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (AMBARI-21352) Workflow Manager view build failure
[ https://issues.apache.org/jira/browse/AMBARI-21352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat resolved AMBARI-21352. - Resolution: Fixed > Workflow Manager view build failure > --- > > Key: AMBARI-21352 > URL: https://issues.apache.org/jira/browse/AMBARI-21352 > Project: Ambari > Issue Type: Bug >Reporter: venkat >Assignee: venkat >Priority: Major > Attachments: AMBARI-21352-trunk-01.patch, AMBARI-21352-trunk.patch > > > Workflow Manager build failure with MVN commands -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (AMBARI-25190) "Global Configurations" defined in workflow XML are being lost during Import workflow (or) during "Reset workflow"
[ https://issues.apache.org/jira/browse/AMBARI-25190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat resolved AMBARI-25190. - Resolution: Fixed > "Global Configurations" defined in workflow XML are being lost during Import > workflow (or) during "Reset workflow" > -- > > Key: AMBARI-25190 > URL: https://issues.apache.org/jira/browse/AMBARI-25190 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: venkat >Assignee: venkat >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25190) "Global Configurations" defined in workflow XML are being lost during Import workflow (or) during "Reset workflow"
venkat created AMBARI-25190: --- Summary: "Global Configurations" defined in workflow XML are being lost during Import workflow (or) during "Reset workflow" Key: AMBARI-25190 URL: https://issues.apache.org/jira/browse/AMBARI-25190 Project: Ambari Issue Type: Bug Components: ambari-views Reporter: venkat Assignee: venkat -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24152) Ambari Workflow Manager (wfmanager) sends plaintext content over API. JSON is expected.
[ https://issues.apache.org/jira/browse/AMBARI-24152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat resolved AMBARI-24152. - Resolution: Fixed > Ambari Workflow Manager (wfmanager) sends plaintext content over API. JSON is > expected. > --- > > Key: AMBARI-24152 > URL: https://issues.apache.org/jira/browse/AMBARI-24152 > Project: Ambari > Issue Type: Bug > Components: ambari-views, contrib >Affects Versions: 2.6.2, 2.7.0 >Reporter: Sean Roberts >Assignee: venkat >Priority: Major > Labels: pull-request-available > Time Spent: 2h 40m > Remaining Estimate: 0h > > The Ambari API is expected to respond with JSON content. > However the wfmanager's /resources/proxy/getCurrentUserName returns plaintext > content. > This is breaking Knox proxying of the UI and is likely to break other > proxies/clients who expect the API to respond with JSON. > https://github.com/apache/ambari/blob/trunk/contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/OozieProxyImpersonator.java#L154-L158 > Full API url would be: > /api/v1/views/WORKFLOW_MANAGER/versions/1.0.0/instances/instance_name/resources/proxy/getCurrentUserName > How to reproduce: > # GET > http://hostname:8080/api/v1/views/WORKFLOW_MANAGER/versions/1.0.0/instances/instance_name/resources/proxy/getCurrentUserName > # Notice that it responds with a username only which is plaintext not JSON. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-25152) Workflow Manager view Nominal Start and End Date Filter doesn't work
[ https://issues.apache.org/jira/browse/AMBARI-25152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat resolved AMBARI-25152. - Resolution: Fixed > Workflow Manager view Nominal Start and End Date Filter doesn't work > > > Key: AMBARI-25152 > URL: https://issues.apache.org/jira/browse/AMBARI-25152 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: venkat >Assignee: venkat >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25152) Workflow Manager view Nominal Start and End Date Filter doesn't work
venkat created AMBARI-25152: --- Summary: Workflow Manager view Nominal Start and End Date Filter doesn't work Key: AMBARI-25152 URL: https://issues.apache.org/jira/browse/AMBARI-25152 Project: Ambari Issue Type: Bug Components: ambari-views Reporter: venkat Assignee: venkat -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24152) Ambari Workflow Manager (wfmanager) sends plaintext content over API. JSON is expected.
[ https://issues.apache.org/jira/browse/AMBARI-24152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16751946#comment-16751946 ] venkat commented on AMBARI-24152: - [~hegand]Submitted the PR in branch-2.6. Waiting for code review. This should fix the issue. > Ambari Workflow Manager (wfmanager) sends plaintext content over API. JSON is > expected. > --- > > Key: AMBARI-24152 > URL: https://issues.apache.org/jira/browse/AMBARI-24152 > Project: Ambari > Issue Type: Bug > Components: ambari-views, contrib >Affects Versions: 2.6.2, 2.7.0 >Reporter: Sean Roberts >Assignee: venkat >Priority: Major > Labels: pull-request-available > Time Spent: 2h > Remaining Estimate: 0h > > The Ambari API is expected to respond with JSON content. > However the wfmanager's /resources/proxy/getCurrentUserName returns plaintext > content. > This is breaking Knox proxying of the UI and is likely to break other > proxies/clients who expect the API to respond with JSON. > https://github.com/apache/ambari/blob/trunk/contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/OozieProxyImpersonator.java#L154-L158 > Full API url would be: > /api/v1/views/WORKFLOW_MANAGER/versions/1.0.0/instances/instance_name/resources/proxy/getCurrentUserName > How to reproduce: > # GET > http://hostname:8080/api/v1/views/WORKFLOW_MANAGER/versions/1.0.0/instances/instance_name/resources/proxy/getCurrentUserName > # Notice that it responds with a username only which is plaintext not JSON. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24819) do not allow creation of new hive actions in WFM
[ https://issues.apache.org/jira/browse/AMBARI-24819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-24819: Status: Patch Available (was: Open) > do not allow creation of new hive actions in WFM > - > > Key: AMBARI-24819 > URL: https://issues.apache.org/jira/browse/AMBARI-24819 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: venkat >Assignee: venkat >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24819) do not allow creation of new hive actions in WFM
venkat created AMBARI-24819: --- Summary: do not allow creation of new hive actions in WFM Key: AMBARI-24819 URL: https://issues.apache.org/jira/browse/AMBARI-24819 Project: Ambari Issue Type: Bug Components: ambari-views Reporter: venkat Assignee: venkat Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24491) Workflow Manager should add ${nameNone}/ string to the beginning of app path
venkat created AMBARI-24491:
---
Summary: Workflow Manager should add ${nameNone}/ string to the
beginning of app path
Key: AMBARI-24491
URL: https://issues.apache.org/jira/browse/AMBARI-24491
Project: Ambari
Issue Type: Bug
Components: ambari-views
Reporter: venkat
Assignee: venkat
When I use Workflow Manager to create a workflow for Oozie and add a spark
action and provide *Application* path using the *Browse* button, Ambari WFM
only inserts the app path in this form: */path/to/app*
In this case the result is a FileNotFoundException in Oozie.
*Workaround*:
When I modify the app path to *${nameNode}/path/to/app* then the job will run
successfully.
Please see tag of the attached generated good and bad workflow xmls.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24266) Error in Validating And Submitting Workflow With Node as Hive
venkat created AMBARI-24266: --- Summary: Error in Validating And Submitting Workflow With Node as Hive Key: AMBARI-24266 URL: https://issues.apache.org/jira/browse/AMBARI-24266 Project: Ambari Issue Type: Bug Components: ambari-views Reporter: venkat Assignee: venkat Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-24152) Ambari Workflow Manager (wfmanager) sends plaintext content over API. JSON is expected.
[ https://issues.apache.org/jira/browse/AMBARI-24152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat reassigned AMBARI-24152: --- Assignee: venkat > Ambari Workflow Manager (wfmanager) sends plaintext content over API. JSON is > expected. > --- > > Key: AMBARI-24152 > URL: https://issues.apache.org/jira/browse/AMBARI-24152 > Project: Ambari > Issue Type: Bug > Components: ambari-views, contrib >Affects Versions: 2.6.2, 2.7.0 >Reporter: Sean Roberts >Assignee: venkat >Priority: Major > > The Ambari API is expected to respond with JSON content. > However the wfmanager's /resources/proxy/getCurrentUserName returns plaintext > content. > This is breaking Knox proxying of the UI and is likely to break other > proxies/clients who expect the API to respond with JSON. > https://github.com/apache/ambari/blob/trunk/contrib/views/wfmanager/src/main/java/org/apache/oozie/ambari/view/OozieProxyImpersonator.java#L154-L158 > Full API url would be: > /api/v1/views/WORKFLOW_MANAGER/versions/1.0.0/instances/instance_name/resources/proxy/getCurrentUserName > How to reproduce: > # GET > http://hostname:8080/api/v1/views/WORKFLOW_MANAGER/versions/1.0.0/instances/instance_name/resources/proxy/getCurrentUserName > # Notice that it responds with a username only which is plaintext not JSON. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-9016) Ambari API uses HTTP Header Content-Type:text/plain when the content is JSON.
[
https://issues.apache.org/jira/browse/AMBARI-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
venkat reassigned AMBARI-9016:
--
Assignee: venkat
> Ambari API uses HTTP Header Content-Type:text/plain when the content is JSON.
> -
>
> Key: AMBARI-9016
> URL: https://issues.apache.org/jira/browse/AMBARI-9016
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 1.7.0, 2.6.2
>Reporter: Sean Roberts
>Assignee: venkat
>Priority: Blocker
> Labels: newbie
>
> Ambari responds with a *Content-Type:text/plain* when the content is actually
> JSON.
> And the API only accepts (PUT/POST) JSON content, but fails when
> "Content-Type:application/json" is used.
> This breaks most HTTP/Restful clients, including the Knox UI proxy.
> Here is a GET showing JSON content with the wrong "Content-Type" (with some
> headers redacted):
> {code}
> $ curl -i http://localhost:8080/api/v1/clusters
> HTTP/1.1 200 OK
> Content-Type: text/plain
> {
> "href" : "http://localhost:8080/api/v1/clusters;,
> "items" : [
> {
> "href" : "http://localhost:8080/api/v1/clusters/clustername;,
> "Clusters" : {
> "cluster_name" : "clustername",
> "version" : "HDP-2.4"
> }
> }
> ]
> }
> {code}
> Attempt to send JSON with Content-Type:application/json fails and it although
> it responds with JSON data, it says its "text/plain".
> {code}
> $ curl -v -u admin\
> -H "Content-Type: application/json" -H x-requested-by:useless \
> http://localhost:8080/api/v1/stacks/HDP/versions/2.4/recommendations -d
> @temp.json
> < HTTP/1.1 500 Server Error
> < Content-Type: text/plain; charset=ISO-8859-1
> {
> "status": 500,
> "message": "Server Error"
> }
> {code}
> It accepts JSON with Content-Type:text/plain:
> {code}
> $ curl -v -u admin\
> -H "Content-Type: test/plain" -H x-requested-by:useless \
> http://localhost:8080/api/v1/stacks/HDP/versions/2.4/recommendations -d
> @temp.json
> > POST /api/v1/stacks/HDP/versions/2.4/recommendations HTTP/1.1
> > Content-Type: test/plain
> < HTTP/1.1 200 OK
> < Content-Type: text/plain
> {
> "resources" : [
> {
> "href" :
> "http://localhost:8080/api/v1/stacks/HDP/versions/2.4/recommendations/8;,
> ... snipped the rest of the JSON since it's not needed ...
> {code}
> This is the file that was sent:
> {code}
> $ cat temp.json
> {
> "recommend" : "configurations",
> "services" : [
> "AMBARI_METRICS","HDFS","HIVE","MAPREDUCE2","PIG","TEZ","YARN","ZOOKEEPER" ],
> "hosts" : [
> "ip-10-0-1-159.ec2.internal","ip-10-0-1-31.ec2.internal","ip-10-0-1-32.ec2.internal","ip-10-0-1-33.ec2.internal"
> ]
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (AMBARI-24008) Unable to import oozie workflow from ambari wf manager view if the workflow uses
[ https://issues.apache.org/jira/browse/AMBARI-24008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat reassigned AMBARI-24008: --- Assignee: venkat (was: Akhil S Naik) > Unable to import oozie workflow from ambari wf manager view if the workflow > uses > - > > Key: AMBARI-24008 > URL: https://issues.apache.org/jira/browse/AMBARI-24008 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.2 >Reporter: Akhil S Naik >Assignee: venkat >Priority: Major > Attachments: Screen Shot 2018-05-31 at 6.08.28 PM.png, workflow.xml > > > Unable to import oozie workflow from ambari wf manager view if the workflow > uses > but the same xml works well in oozie if tried directly > Attached the workflow.xml file : [^workflow.xml] > there is a script error exists when try to import , attached the script error > : !Screen Shot 2018-05-31 at 6.08.28 PM.png! -- 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 ] venkat 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] [Updated] (AMBARI-22927) Hive View 1.5 Upload Table - not able to change datatype from the dropdown for a wide file
[ https://issues.apache.org/jira/browse/AMBARI-22927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-22927: Resolution: Fixed Status: Resolved (was: Patch Available) > Hive View 1.5 Upload Table - not able to change datatype from the dropdown > for a wide file > -- > > Key: AMBARI-22927 > URL: https://issues.apache.org/jira/browse/AMBARI-22927 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat >Priority: Blocker > Labels: pull-request-available > Fix For: 2.5.2 > > Time Spent: 3h > Remaining Estimate: 0h > > Steps: > # Go to Hive view 1.5, > # Select type CSV > # Upload the attached file > # Try to change the datatype of last column > # The UI comes back to the leftmost column, showing the first few columns -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22927) Hive View 1.5 Upload Table - not able to change datatype from the dropdown for a wide file
[ https://issues.apache.org/jira/browse/AMBARI-22927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-22927: Status: Patch Available (was: Open) > Hive View 1.5 Upload Table - not able to change datatype from the dropdown > for a wide file > -- > > Key: AMBARI-22927 > URL: https://issues.apache.org/jira/browse/AMBARI-22927 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat >Priority: Blocker > Labels: pull-request-available > Fix For: 2.5.2 > > Time Spent: 1.5h > Remaining Estimate: 0h > > Steps: > # Go to Hive view 1.5, > # Select type CSV > # Upload the attached file > # Try to change the datatype of last column > # The UI comes back to the leftmost column, showing the first few columns -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22927) Hive View 1.5 Upload Table - not able to change datatype from the dropdown for a wide file
venkat created AMBARI-22927: --- Summary: Hive View 1.5 Upload Table - not able to change datatype from the dropdown for a wide file Key: AMBARI-22927 URL: https://issues.apache.org/jira/browse/AMBARI-22927 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.2 Reporter: venkat Assignee: venkat Fix For: 2.5.2 Steps: # Go to Hive view 1.5, # Select type CSV # Upload the attached file # Try to change the datatype of last column # The UI comes back to the leftmost column, showing the first few columns -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22759) [Hive Views 2.0] Deleting a Saved query is Buggy when Mutliple Queries exist in same Name
[ https://issues.apache.org/jira/browse/AMBARI-22759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-22759: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > [Hive Views 2.0] Deleting a Saved query is Buggy when Mutliple Queries exist > in same Name > - > > Key: AMBARI-22759 > URL: https://issues.apache.org/jira/browse/AMBARI-22759 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 > Environment: ambari 2.5.2 >Reporter: Akhil S Naik >Assignee: venkat >Priority: Major > Labels: newbie, patch, pull-request-available, usability > Fix For: 3.0.0 > > Attachments: AMBARI-22759-trunk.patch, > hive_duplicate_saved_query_issue.png > > Time Spent: 40m > Remaining Estimate: 0h > > Reproduction scenario : > Save some queries under same name . > !https://issues.apache.org/jira/secure/attachment/12905639/hive_duplicate_saved_query_issue.png! > delete one of the saved query > *hive views is deleting some other query randomly and the query i deleted > still exists in saved query even after refresh of page.* > Root Cause : > After the Fix of AMBARI-19958, Hive views is querying the saved Queries with > FilterBy queryId and server is responding mutiple queries as all the queries > has same name, > then Web client is deleting the first record from these savedQueries due to > which this issue is happening. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-22759) [Hive Views 2.0] Deleting a Saved query is Buggy when Mutliple Queries exist in same Name
[ https://issues.apache.org/jira/browse/AMBARI-22759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat reassigned AMBARI-22759: --- Assignee: venkat > [Hive Views 2.0] Deleting a Saved query is Buggy when Mutliple Queries exist > in same Name > - > > Key: AMBARI-22759 > URL: https://issues.apache.org/jira/browse/AMBARI-22759 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 > Environment: ambari 2.5.2 >Reporter: Akhil S Naik >Assignee: venkat >Priority: Major > Labels: newbie, patch, pull-request-available, usability > Fix For: 3.0.0 > > Attachments: AMBARI-22759-trunk.patch, > hive_duplicate_saved_query_issue.png > > Time Spent: 40m > Remaining Estimate: 0h > > Reproduction scenario : > Save some queries under same name . > !https://issues.apache.org/jira/secure/attachment/12905639/hive_duplicate_saved_query_issue.png! > delete one of the saved query > *hive views is deleting some other query randomly and the query i deleted > still exists in saved query even after refresh of page.* > Root Cause : > After the Fix of AMBARI-19958, Hive views is querying the saved Queries with > FilterBy queryId and server is responding mutiple queries as all the queries > has same name, > then Web client is deleting the first record from these savedQueries due to > which this issue is happening. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-22759) [Hive Views 2.0] Deleting a Saved query is Buggy when Mutliple Queries exist in same Name
[ https://issues.apache.org/jira/browse/AMBARI-22759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat reassigned AMBARI-22759: --- Assignee: venkat > [Hive Views 2.0] Deleting a Saved query is Buggy when Mutliple Queries exist > in same Name > - > > Key: AMBARI-22759 > URL: https://issues.apache.org/jira/browse/AMBARI-22759 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 > Environment: ambari 2.5.2 >Reporter: Akhil S Naik >Assignee: venkat >Priority: Major > Labels: newbie, patch, pull-request-available, usability > Fix For: 3.0.0 > > Attachments: AMBARI-22759-trunk.patch, > hive_duplicate_saved_query_issue.png > > Time Spent: 40m > Remaining Estimate: 0h > > Reproduction scenario : > Save some queries under same name . > !https://issues.apache.org/jira/secure/attachment/12905639/hive_duplicate_saved_query_issue.png! > delete one of the saved query > *hive views is deleting some other query randomly and the query i deleted > still exists in saved query even after refresh of page.* > Root Cause : > After the Fix of AMBARI-19958, Hive views is querying the saved Queries with > FilterBy queryId and server is responding mutiple queries as all the queries > has same name, > then Web client is deleting the first record from these savedQueries due to > which this issue is happening. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-22759) [Hive Views 2.0] Deleting a Saved query is Buggy when Mutliple Queries exist in same Name
[ https://issues.apache.org/jira/browse/AMBARI-22759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat reassigned AMBARI-22759: --- Assignee: (was: venkat) > [Hive Views 2.0] Deleting a Saved query is Buggy when Mutliple Queries exist > in same Name > - > > Key: AMBARI-22759 > URL: https://issues.apache.org/jira/browse/AMBARI-22759 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 > Environment: ambari 2.5.2 >Reporter: Akhil S Naik >Priority: Major > Labels: newbie, patch, pull-request-available, usability > Fix For: 3.0.0 > > Attachments: AMBARI-22759-trunk.patch, > hive_duplicate_saved_query_issue.png > > Time Spent: 40m > Remaining Estimate: 0h > > Reproduction scenario : > Save some queries under same name . > !https://issues.apache.org/jira/secure/attachment/12905639/hive_duplicate_saved_query_issue.png! > delete one of the saved query > *hive views is deleting some other query randomly and the query i deleted > still exists in saved query even after refresh of page.* > Root Cause : > After the Fix of AMBARI-19958, Hive views is querying the saved Queries with > FilterBy queryId and server is responding mutiple queries as all the queries > has same name, > then Web client is deleting the first record from these savedQueries due to > which this issue is happening. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22806) Unable to delete files from HDFS using Ambari File View when Ambari Views is accessed via Knox
venkat created AMBARI-22806: --- Summary: Unable to delete files from HDFS using Ambari File View when Ambari Views is accessed via Knox Key: AMBARI-22806 URL: https://issues.apache.org/jira/browse/AMBARI-22806 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 3.0.0, 2.5.0, 2.6.0 Environment: Unable to delete files from HDFS using Ambari File View when Ambari Views is accessed via Knox Reporter: venkat Assignee: venkat -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-22703) Ambari WorkFlow manager doesn't work on a standalone ambari server with remove cluster configured and oozie has enabled SSL
[
https://issues.apache.org/jira/browse/AMBARI-22703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
venkat reassigned AMBARI-22703:
---
Assignee: venkat
> Ambari WorkFlow manager doesn't work on a standalone ambari server with
> remove cluster configured and oozie has enabled SSL
> ---
>
> Key: AMBARI-22703
> URL: https://issues.apache.org/jira/browse/AMBARI-22703
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.2
> Environment: Ambari Version : 2.5.1.0
> ssl enabled oozie and standalone ambari with remote cluster
>Reporter: Akhil S Naik
>Assignee: venkat
> Attachments: oozie keeps loading.png, remote cluster config.png
>
>
> We have a standalone ambari server with remote cluster configured,
> If we configure the workflow manager view of remote cluster with oozie is
> enabled with SSL . The Page keeps showing loading dialog
> (attached image of configuration and issue)
> It keeps loading as shown in the image
>
> !https://issues.apache.org/jira/secure/attachment/12903882/oozie%20keeps%20loading.png!
> possible root cause :
> The wfmanager-view.log shows the server pings on port 11000 instead it has to
> access the port 11443
> {code:java}
> 28 Dec 2017 09:29:51,821 INFO [ambari-client-thread-25] [WORKFLOW_MANAGER
> 1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
> http://host6.example.com:11000/oozie/v1/admin/configuration
> 28 Dec 2017 09:29:52,153 INFO [ambari-client-thread-30] [WORKFLOW_MANAGER
> 1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
> http://host6.example.com:11000/oozie/v2/jobs?filter==1=15=wf
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21569) Users randomly getting "HDFS020 Could not write file" exceptions while running query from Hive View
[
https://issues.apache.org/jira/browse/AMBARI-21569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
venkat updated AMBARI-21569:
Attachment: AMBARI-21569-Branch-2.6.patch
AMBARI-21569-trunk-v1.patch
AMBARI-21569-Branch-2.5-v1.patch
> Users randomly getting "HDFS020 Could not write file" exceptions while
> running query from Hive View
> ---
>
> Key: AMBARI-21569
> URL: https://issues.apache.org/jira/browse/AMBARI-21569
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Gaurav Nagar
>Assignee: venkat
> Fix For: 2.6.0
>
> Attachments: AMBARI-21569-Branch-2.5-v1.patch,
> AMBARI-21569-Branch-2.6.patch, AMBARI-21569-trunk-v1.patch,
> AMBARI-21569-trunk.patch, AMBARI-21569.branch-2.5.patch
>
>
> Running queries from Hive View are reporting intermittent issues with the
> Hive view. They get the exceptions as reported below
> {code:java}
> ServiceFormattedException:100 -
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS020 Could not write
> file /user/user/hive/jobs/hive-job-5290-2017-03-22_02-35/logs
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS020 Could not write
> file /user/user/hive/jobs/hive-job-5290-2017-03-22_02-35/logs
> at
> org.apache.ambari.view.utils.hdfs.HdfsUtil.putStringToFile(HdfsUtil.java:51)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobControllerImpl.updateOperationLogs(JobControllerImpl.java:202)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobControllerImpl.update(JobControllerImpl.java:160)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobResourceManager.read(JobResourceManager.java:79)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobResourceManager.readController(JobResourceManager.java:95)
> at
> org.apache.ambari.view.hive.resources.jobs.JobService.getOne(JobService.java:133)
> at sun.reflect.GeneratedMethodAccessor191.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at
[jira] [Updated] (AMBARI-22502) Workflow Manager View - FS node will overwrite internal commands and replace them with blank "move" commands when reopening the node
[ https://issues.apache.org/jira/browse/AMBARI-22502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-22502: Component/s: ambari-views > Workflow Manager View - FS node will overwrite internal commands and replace > them with blank "move" commands when reopening the node > > > Key: AMBARI-22502 > URL: https://issues.apache.org/jira/browse/AMBARI-22502 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: venkat >Assignee: venkat > Fix For: 2.6.1 > > Attachments: AMBARI-22502-trunk.patch > > > STEPS TO REPRODUCE: > 1. Create workflow with FS node > 2. Add a HDFS "Move" command > 3. Save > 4. Exit the browser, clear cache and log back in > 5. Select Recent > 6. Select Saved workflow > 7. Open workflow and check FS node -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22502) Workflow Manager View - FS node will overwrite internal commands and replace them with blank "move" commands when reopening the node
[ https://issues.apache.org/jira/browse/AMBARI-22502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-22502: Fix Version/s: 2.6.1 > Workflow Manager View - FS node will overwrite internal commands and replace > them with blank "move" commands when reopening the node > > > Key: AMBARI-22502 > URL: https://issues.apache.org/jira/browse/AMBARI-22502 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: venkat >Assignee: venkat > Fix For: 2.6.1 > > Attachments: AMBARI-22502-trunk.patch > > > STEPS TO REPRODUCE: > 1. Create workflow with FS node > 2. Add a HDFS "Move" command > 3. Save > 4. Exit the browser, clear cache and log back in > 5. Select Recent > 6. Select Saved workflow > 7. Open workflow and check FS node -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22502) Workflow Manager View - FS node will overwrite internal commands and replace them with blank "move" commands when reopening the node
[ https://issues.apache.org/jira/browse/AMBARI-22502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-22502: Status: Patch Available (was: Open) > Workflow Manager View - FS node will overwrite internal commands and replace > them with blank "move" commands when reopening the node > > > Key: AMBARI-22502 > URL: https://issues.apache.org/jira/browse/AMBARI-22502 > Project: Ambari > Issue Type: Bug >Reporter: venkat >Assignee: venkat > Attachments: AMBARI-22502-trunk.patch > > > STEPS TO REPRODUCE: > 1. Create workflow with FS node > 2. Add a HDFS "Move" command > 3. Save > 4. Exit the browser, clear cache and log back in > 5. Select Recent > 6. Select Saved workflow > 7. Open workflow and check FS node -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22502) Workflow Manager View - FS node will overwrite internal commands and replace them with blank "move" commands when reopening the node
[ https://issues.apache.org/jira/browse/AMBARI-22502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-22502: Attachment: AMBARI-22502-trunk.patch > Workflow Manager View - FS node will overwrite internal commands and replace > them with blank "move" commands when reopening the node > > > Key: AMBARI-22502 > URL: https://issues.apache.org/jira/browse/AMBARI-22502 > Project: Ambari > Issue Type: Bug >Reporter: venkat >Assignee: venkat > Attachments: AMBARI-22502-trunk.patch > > > STEPS TO REPRODUCE: > 1. Create workflow with FS node > 2. Add a HDFS "Move" command > 3. Save > 4. Exit the browser, clear cache and log back in > 5. Select Recent > 6. Select Saved workflow > 7. Open workflow and check FS node -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22502) Workflow Manager View - FS node will overwrite internal commands and replace them with blank "move" commands when reopening the node
venkat created AMBARI-22502: --- Summary: Workflow Manager View - FS node will overwrite internal commands and replace them with blank "move" commands when reopening the node Key: AMBARI-22502 URL: https://issues.apache.org/jira/browse/AMBARI-22502 Project: Ambari Issue Type: Bug Reporter: venkat Assignee: venkat STEPS TO REPRODUCE: 1. Create workflow with FS node 2. Add a HDFS "Move" command 3. Save 4. Exit the browser, clear cache and log back in 5. Select Recent 6. Select Saved workflow 7. Open workflow and check FS node -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22103) HiveView 1.5 is not showing the "Visualization" page when accessed over Knox.
[ https://issues.apache.org/jira/browse/AMBARI-22103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-22103: Status: Patch Available (was: Open) > HiveView 1.5 is not showing the "Visualization" page when accessed over Knox. > - > > Key: AMBARI-22103 > URL: https://issues.apache.org/jira/browse/AMBARI-22103 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.6.0 > > Attachments: AMBARI-22103.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22103) HiveView 1.5 is not showing the "Visualization" page when accessed over Knox.
[ https://issues.apache.org/jira/browse/AMBARI-22103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-22103: Attachment: AMBARI-22103.patch > HiveView 1.5 is not showing the "Visualization" page when accessed over Knox. > - > > Key: AMBARI-22103 > URL: https://issues.apache.org/jira/browse/AMBARI-22103 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.6.0 > > Attachments: AMBARI-22103.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22103) HiveView 1.5 is not showing the "Visualization" page when accessed over Knox.
venkat created AMBARI-22103: --- Summary: HiveView 1.5 is not showing the "Visualization" page when accessed over Knox. Key: AMBARI-22103 URL: https://issues.apache.org/jira/browse/AMBARI-22103 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.6.0 Reporter: venkat Assignee: venkat Fix For: 2.6.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22096) Entries related to hive query are found in RM UI after killing or stopping the execution of the query.
[ https://issues.apache.org/jira/browse/AMBARI-22096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-22096: Attachment: AMBARI-22096-trunk.patch > Entries related to hive query are found in RM UI after killing or stopping > the execution of the query. > -- > > Key: AMBARI-22096 > URL: https://issues.apache.org/jira/browse/AMBARI-22096 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.6.0 > > Attachments: AMBARI-22096-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22096) Entries related to hive query are found in RM UI after killing or stopping the execution of the query.
venkat created AMBARI-22096: --- Summary: Entries related to hive query are found in RM UI after killing or stopping the execution of the query. Key: AMBARI-22096 URL: https://issues.apache.org/jira/browse/AMBARI-22096 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.6.0 Reporter: venkat Assignee: venkat Fix For: 2.6.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22091) Hive view2.0 Jobs worksheets doesn't have hyperlink whereas view1.5 History worksheets had hyperlinks pointing to fetched results
[ https://issues.apache.org/jira/browse/AMBARI-22091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-22091: Attachment: AMBARI-22091.patch > Hive view2.0 Jobs worksheets doesn't have hyperlink whereas view1.5 History > worksheets had hyperlinks pointing to fetched results > - > > Key: AMBARI-22091 > URL: https://issues.apache.org/jira/browse/AMBARI-22091 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.6.0 > > Attachments: AMBARI-22091.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22091) Hive view2.0 Jobs worksheets doesn't have hyperlink whereas view1.5 History worksheets had hyperlinks pointing to fetched results
[ https://issues.apache.org/jira/browse/AMBARI-22091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-22091: Status: Patch Available (was: In Progress) > Hive view2.0 Jobs worksheets doesn't have hyperlink whereas view1.5 History > worksheets had hyperlinks pointing to fetched results > - > > Key: AMBARI-22091 > URL: https://issues.apache.org/jira/browse/AMBARI-22091 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.6.0 > > Attachments: AMBARI-22091.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22091) Hive view2.0 Jobs worksheets doesn't have hyperlink whereas view1.5 History worksheets had hyperlinks pointing to fetched results
venkat created AMBARI-22091: --- Summary: Hive view2.0 Jobs worksheets doesn't have hyperlink whereas view1.5 History worksheets had hyperlinks pointing to fetched results Key: AMBARI-22091 URL: https://issues.apache.org/jira/browse/AMBARI-22091 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.6.0 Reporter: venkat Assignee: venkat Fix For: 2.6.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21890) Ambari Files View - browser going to hung state while opening a HDFS folder which has huge number of files(>10000)
[ https://issues.apache.org/jira/browse/AMBARI-21890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158064#comment-16158064 ] venkat commented on AMBARI-21890: - Committed to trunk and branch-2.6 > Ambari Files View - browser going to hung state while opening a HDFS folder > which has huge number of files(>1) > -- > > Key: AMBARI-21890 > URL: https://issues.apache.org/jira/browse/AMBARI-21890 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.0 >Reporter: venkat >Assignee: venkat >Priority: Blocker > Fix For: 2.6.0 > > Attachments: AMBARI-21890-trunk.patch > > > A configurable limit have been imposed on the no of files being retrieved > from the server and the limit by default is set to 5000. > Search has been provided to find the file faster. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21890) Ambari Files View - browser going to hung state while opening a HDFS folder which has huge number of files(>10000)
[ https://issues.apache.org/jira/browse/AMBARI-21890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21890: Attachment: AMBARI-21890-trunk.patch > Ambari Files View - browser going to hung state while opening a HDFS folder > which has huge number of files(>1) > -- > > Key: AMBARI-21890 > URL: https://issues.apache.org/jira/browse/AMBARI-21890 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.0 >Reporter: venkat >Assignee: venkat >Priority: Blocker > Fix For: 2.6.0 > > Attachments: AMBARI-21890-trunk.patch > > > A configurable limit have been imposed on the no of files being retrieved > from the server and the limit by default is set to 5000. > Search has been provided to find the file faster. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21890) Ambari Files View - browser going to hung state while opening a HDFS folder which has huge number of files(>10000)
venkat created AMBARI-21890: --- Summary: Ambari Files View - browser going to hung state while opening a HDFS folder which has huge number of files(>1) Key: AMBARI-21890 URL: https://issues.apache.org/jira/browse/AMBARI-21890 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.6.0 Reporter: venkat Assignee: venkat Priority: Blocker Fix For: 2.6.0 A configurable limit have been imposed on the no of files being retrieved from the server and the limit by default is set to 5000. Search has been provided to find the file faster. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21569) Users randomly getting "HDFS020 Could not write file" exceptions while running query from Hive View
[
https://issues.apache.org/jira/browse/AMBARI-21569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16138209#comment-16138209
]
venkat commented on AMBARI-21569:
-
Committed to trunk and branch-2.5.
> Users randomly getting "HDFS020 Could not write file" exceptions while
> running query from Hive View
> ---
>
> Key: AMBARI-21569
> URL: https://issues.apache.org/jira/browse/AMBARI-21569
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Gaurav Nagar
>Assignee: venkat
> Attachments: AMBARI-21569.branch-2.5.patch, AMBARI-21569-trunk.patch
>
>
> Running queries from Hive View are reporting intermittent issues with the
> Hive view. They get the exceptions as reported below
> {code:java}
> ServiceFormattedException:100 -
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS020 Could not write
> file /user/user/hive/jobs/hive-job-5290-2017-03-22_02-35/logs
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS020 Could not write
> file /user/user/hive/jobs/hive-job-5290-2017-03-22_02-35/logs
> at
> org.apache.ambari.view.utils.hdfs.HdfsUtil.putStringToFile(HdfsUtil.java:51)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobControllerImpl.updateOperationLogs(JobControllerImpl.java:202)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobControllerImpl.update(JobControllerImpl.java:160)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobResourceManager.read(JobResourceManager.java:79)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobResourceManager.readController(JobResourceManager.java:95)
> at
> org.apache.ambari.view.hive.resources.jobs.JobService.getOne(JobService.java:133)
> at sun.reflect.GeneratedMethodAccessor191.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1507)
[jira] [Updated] (AMBARI-21569) Users randomly getting "HDFS020 Could not write file" exceptions while running query from Hive View
[
https://issues.apache.org/jira/browse/AMBARI-21569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
venkat updated AMBARI-21569:
Status: Patch Available (was: Open)
> Users randomly getting "HDFS020 Could not write file" exceptions while
> running query from Hive View
> ---
>
> Key: AMBARI-21569
> URL: https://issues.apache.org/jira/browse/AMBARI-21569
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Gaurav Nagar
>Assignee: venkat
> Attachments: AMBARI-21569.branch-2.5.patch, AMBARI-21569-trunk.patch
>
>
> Running queries from Hive View are reporting intermittent issues with the
> Hive view. They get the exceptions as reported below
> {code:java}
> ServiceFormattedException:100 -
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS020 Could not write
> file /user/user/hive/jobs/hive-job-5290-2017-03-22_02-35/logs
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS020 Could not write
> file /user/user/hive/jobs/hive-job-5290-2017-03-22_02-35/logs
> at
> org.apache.ambari.view.utils.hdfs.HdfsUtil.putStringToFile(HdfsUtil.java:51)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobControllerImpl.updateOperationLogs(JobControllerImpl.java:202)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobControllerImpl.update(JobControllerImpl.java:160)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobResourceManager.read(JobResourceManager.java:79)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobResourceManager.readController(JobResourceManager.java:95)
> at
> org.apache.ambari.view.hive.resources.jobs.JobService.getOne(JobService.java:133)
> at sun.reflect.GeneratedMethodAccessor191.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1507)
> at
>
[jira] [Updated] (AMBARI-21569) Users randomly getting "HDFS020 Could not write file" exceptions while running query from Hive View
[
https://issues.apache.org/jira/browse/AMBARI-21569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
venkat updated AMBARI-21569:
Attachment: AMBARI-21569-trunk.patch
> Users randomly getting "HDFS020 Could not write file" exceptions while
> running query from Hive View
> ---
>
> Key: AMBARI-21569
> URL: https://issues.apache.org/jira/browse/AMBARI-21569
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Gaurav Nagar
>Assignee: venkat
> Attachments: AMBARI-21569.branch-2.5.patch, AMBARI-21569-trunk.patch
>
>
> Running queries from Hive View are reporting intermittent issues with the
> Hive view. They get the exceptions as reported below
> {code:java}
> ServiceFormattedException:100 -
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS020 Could not write
> file /user/user/hive/jobs/hive-job-5290-2017-03-22_02-35/logs
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS020 Could not write
> file /user/user/hive/jobs/hive-job-5290-2017-03-22_02-35/logs
> at
> org.apache.ambari.view.utils.hdfs.HdfsUtil.putStringToFile(HdfsUtil.java:51)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobControllerImpl.updateOperationLogs(JobControllerImpl.java:202)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobControllerImpl.update(JobControllerImpl.java:160)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobResourceManager.read(JobResourceManager.java:79)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobResourceManager.readController(JobResourceManager.java:95)
> at
> org.apache.ambari.view.hive.resources.jobs.JobService.getOne(JobService.java:133)
> at sun.reflect.GeneratedMethodAccessor191.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1507)
> at
>
[jira] [Updated] (AMBARI-21569) Users randomly getting "HDFS020 Could not write file" exceptions while running query from Hive View
[
https://issues.apache.org/jira/browse/AMBARI-21569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
venkat updated AMBARI-21569:
Attachment: AMBARI-21569.branch-2.5.patch
> Users randomly getting "HDFS020 Could not write file" exceptions while
> running query from Hive View
> ---
>
> Key: AMBARI-21569
> URL: https://issues.apache.org/jira/browse/AMBARI-21569
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Gaurav Nagar
>Assignee: venkat
> Attachments: AMBARI-21569.branch-2.5.patch
>
>
> Running queries from Hive View are reporting intermittent issues with the
> Hive view. They get the exceptions as reported below
> {code:java}
> ServiceFormattedException:100 -
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS020 Could not write
> file /user/user/hive/jobs/hive-job-5290-2017-03-22_02-35/logs
> org.apache.ambari.view.utils.hdfs.HdfsApiException: HDFS020 Could not write
> file /user/user/hive/jobs/hive-job-5290-2017-03-22_02-35/logs
> at
> org.apache.ambari.view.utils.hdfs.HdfsUtil.putStringToFile(HdfsUtil.java:51)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobControllerImpl.updateOperationLogs(JobControllerImpl.java:202)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobControllerImpl.update(JobControllerImpl.java:160)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobResourceManager.read(JobResourceManager.java:79)
> at
> org.apache.ambari.view.hive.resources.jobs.viewJobs.JobResourceManager.readController(JobResourceManager.java:95)
> at
> org.apache.ambari.view.hive.resources.jobs.JobService.getOne(JobService.java:133)
> at sun.reflect.GeneratedMethodAccessor191.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1507)
> at
>
[jira] [Updated] (AMBARI-21352) Workflow Manager view build failure
[ https://issues.apache.org/jira/browse/AMBARI-21352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21352: Attachment: AMBARI-21352-trunk-01.patch > Workflow Manager view build failure > --- > > Key: AMBARI-21352 > URL: https://issues.apache.org/jira/browse/AMBARI-21352 > Project: Ambari > Issue Type: Bug >Reporter: venkat >Assignee: venkat > Attachments: AMBARI-21352-trunk-01.patch, AMBARI-21352-trunk.patch > > > Workflow Manager build failure with MVN commands -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21352) Workflow Manager view build failure
[ https://issues.apache.org/jira/browse/AMBARI-21352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16064622#comment-16064622 ] venkat commented on AMBARI-21352: - Committed to trunk and branch-2.5 > Workflow Manager view build failure > --- > > Key: AMBARI-21352 > URL: https://issues.apache.org/jira/browse/AMBARI-21352 > Project: Ambari > Issue Type: Bug >Reporter: venkat >Assignee: venkat > Attachments: AMBARI-21352-trunk.patch > > > Workflow Manager build failure with MVN commands -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21338) Styling Issues with newly implemented workflow manager file browser
[ https://issues.apache.org/jira/browse/AMBARI-21338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21338: Resolution: Fixed Status: Resolved (was: Patch Available) > Styling Issues with newly implemented workflow manager file browser > > > Key: AMBARI-21338 > URL: https://issues.apache.org/jira/browse/AMBARI-21338 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: Supreeth Sharma >Assignee: venkat > Labels: WFD, WFM > Fix For: 2.5.2 > > Attachments: AMBARI-21338-trunk.patch > > > Issue 1: Input box to provide file input path is not visible as part of file > browser modal window without scrolling. > Need to make it more prominent. > Issue 2 : Folder listing is distorted in firefox browsers. Need to left align > these subdirectories. > Attaching the screenshot. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21338) Styling Issues with newly implemented workflow manager file browser
[ https://issues.apache.org/jira/browse/AMBARI-21338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16064550#comment-16064550 ] venkat commented on AMBARI-21338: - Committed into Trunk and branch-2.5. > Styling Issues with newly implemented workflow manager file browser > > > Key: AMBARI-21338 > URL: https://issues.apache.org/jira/browse/AMBARI-21338 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: Supreeth Sharma >Assignee: venkat > Labels: WFD, WFM > Fix For: 2.5.2 > > Attachments: AMBARI-21338-trunk.patch > > > Issue 1: Input box to provide file input path is not visible as part of file > browser modal window without scrolling. > Need to make it more prominent. > Issue 2 : Folder listing is distorted in firefox browsers. Need to left align > these subdirectories. > Attaching the screenshot. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21338) Styling Issues with newly implemented workflow manager file browser
[ https://issues.apache.org/jira/browse/AMBARI-21338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21338: Status: Patch Available (was: Open) > Styling Issues with newly implemented workflow manager file browser > > > Key: AMBARI-21338 > URL: https://issues.apache.org/jira/browse/AMBARI-21338 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: Supreeth Sharma >Assignee: venkat > Labels: WFD, WFM > Fix For: 2.5.2 > > Attachments: AMBARI-21338-trunk.patch > > > Issue 1: Input box to provide file input path is not visible as part of file > browser modal window without scrolling. > Need to make it more prominent. > Issue 2 : Folder listing is distorted in firefox browsers. Need to left align > these subdirectories. > Attaching the screenshot. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21352) Workflow Manager view build failure
[ https://issues.apache.org/jira/browse/AMBARI-21352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21352: Attachment: AMBARI-21352-trunk.patch > Workflow Manager view build failure > --- > > Key: AMBARI-21352 > URL: https://issues.apache.org/jira/browse/AMBARI-21352 > Project: Ambari > Issue Type: Bug >Reporter: venkat >Assignee: venkat > Attachments: AMBARI-21352-trunk.patch > > > Workflow Manager build failure with MVN commands -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21352) Workflow Manager view build failure
venkat created AMBARI-21352: --- Summary: Workflow Manager view build failure Key: AMBARI-21352 URL: https://issues.apache.org/jira/browse/AMBARI-21352 Project: Ambari Issue Type: Bug Reporter: venkat Assignee: venkat Workflow Manager build failure with MVN commands -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21338) Styling Issues with newly implemented workflow manager file browser
[ https://issues.apache.org/jira/browse/AMBARI-21338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21338: Attachment: AMBARI-21338-trunk.patch > Styling Issues with newly implemented workflow manager file browser > > > Key: AMBARI-21338 > URL: https://issues.apache.org/jira/browse/AMBARI-21338 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: Supreeth Sharma >Assignee: venkat > Labels: WFD, WFM > Fix For: 2.5.2 > > Attachments: AMBARI-21338-trunk.patch > > > Issue 1: Input box to provide file input path is not visible as part of file > browser modal window without scrolling. > Need to make it more prominent. > Issue 2 : Folder listing is distorted in firefox browsers. Need to left align > these subdirectories. > Attaching the screenshot. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-21084) Files view on IE 11- On Concatenating files or downloading, the concatenated or downloaded file occupies the entire UI.
[ https://issues.apache.org/jira/browse/AMBARI-21084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat resolved AMBARI-21084. - Resolution: Fixed > Files view on IE 11- On Concatenating files or downloading, the concatenated > or downloaded file occupies the entire UI. > --- > > Key: AMBARI-21084 > URL: https://issues.apache.org/jira/browse/AMBARI-21084 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.3 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21084-trunk.patch > > > The same behaviour is observed while we are trying to download the file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-21330) Remove slider view from Ambari-3.0.0
[ https://issues.apache.org/jira/browse/AMBARI-21330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat resolved AMBARI-21330. - Resolution: Fixed > Remove slider view from Ambari-3.0.0 > > > Key: AMBARI-21330 > URL: https://issues.apache.org/jira/browse/AMBARI-21330 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21330-trunk.patch > > > 1. Remove Slider View from trunk (Slider View is deprecated as of Ambari > 2.5.0, so it can be removed in 3.0.0) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21255) Remove YARN client mode option from WFM
[ https://issues.apache.org/jira/browse/AMBARI-21255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21255: Resolution: Fixed Status: Resolved (was: Patch Available) > Remove YARN client mode option from WFM > --- > > Key: AMBARI-21255 > URL: https://issues.apache.org/jira/browse/AMBARI-21255 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21255-branch-2.5.2-updated.patch > > > Today, Spark does not support YARN Client mode and hence, WFM/Oozie should > not provide YARN Client mode option. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21264) Integrate new hdfs-file browser in WFD
[ https://issues.apache.org/jira/browse/AMBARI-21264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21264: Resolution: Fixed Status: Resolved (was: Patch Available) > Integrate new hdfs-file browser in WFD > -- > > Key: AMBARI-21264 > URL: https://issues.apache.org/jira/browse/AMBARI-21264 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21264-trunk.patch > > > HDFS directory viewer component used in views which have to be changed from > tree view to list view should be integrated in WFD -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-20139) Need to show data in sorted order in Hive view
[ https://issues.apache.org/jira/browse/AMBARI-20139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-20139: Resolution: Fixed Status: Resolved (was: Patch Available) > Need to show data in sorted order in Hive view > -- > > Key: AMBARI-20139 > URL: https://issues.apache.org/jira/browse/AMBARI-20139 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: venkat > Labels: HiveView2.0 > Attachments: AMBARI-20139-trunk.01.patch, AMBARI-20139-trunk.patch > > > Need to show data in sorted order in Hive view. > Case 1: Tables list view in 'Query' Tab and 'Tables' tab > Tables should be listed in alphabetical order > Case 2: Jobs should be sorted based on Job Id in 'Jobs' tab. I guess > descending order makes sense. > Case 3 : 'Saved Queries' and 'UDFs' tab > Result should be sorted based on user action time. Recent action should come > first. > Case 4: 'Settings' tab : > Lexicographical order based on KEY. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21330) Remove slider view from Ambari-3.0.0
[ https://issues.apache.org/jira/browse/AMBARI-21330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21330: Attachment: AMBARI-21330-trunk.patch > Remove slider view from Ambari-3.0.0 > > > Key: AMBARI-21330 > URL: https://issues.apache.org/jira/browse/AMBARI-21330 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21330-trunk.patch > > > 1. Remove Slider View from trunk (Slider View is deprecated as of Ambari > 2.5.0, so it can be removed in 3.0.0) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21330) Remove slider view from Ambari-3.0.0
venkat created AMBARI-21330: --- Summary: Remove slider view from Ambari-3.0.0 Key: AMBARI-21330 URL: https://issues.apache.org/jira/browse/AMBARI-21330 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.2 Reporter: venkat Assignee: venkat Fix For: 2.5.2 1. Remove Slider View from trunk (Slider View is deprecated as of Ambari 2.5.0, so it can be removed in 3.0.0) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21323) Hive view 2.0-UI issues on IE11 +Win 7
[ https://issues.apache.org/jira/browse/AMBARI-21323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060342#comment-16060342 ] venkat commented on AMBARI-21323: - Committed to trunk and branch-2.5 > Hive view 2.0-UI issues on IE11 +Win 7 > -- > > Key: AMBARI-21323 > URL: https://issues.apache.org/jira/browse/AMBARI-21323 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21323-trunk.patch, hive properties.PNG, > partition.PNG, tablename.PNG, upload.PNG, Views button.PNG > > > 1. Not able to add hive properties-BLOCKER. > [^hive properties.PNG] > 2. Add partition wizard is not shows properly > [^partition.PNG] > 3. Long table name spills from the left pane > [^tablename.PNG] > 4. Upload Table UI is not opening –BLOCKER > [^upload.PNG] > 5. Views button on top RHS, next to admin dropdown is not visible. > [^Views button.PNG] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21323) Hive view 2.0-UI issues on IE11 +Win 7
[ https://issues.apache.org/jira/browse/AMBARI-21323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21323: Status: Patch Available (was: Open) > Hive view 2.0-UI issues on IE11 +Win 7 > -- > > Key: AMBARI-21323 > URL: https://issues.apache.org/jira/browse/AMBARI-21323 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21323-trunk.patch, hive properties.PNG, > partition.PNG, tablename.PNG, upload.PNG, Views button.PNG > > > 1. Not able to add hive properties-BLOCKER. > [^hive properties.PNG] > 2. Add partition wizard is not shows properly > [^partition.PNG] > 3. Long table name spills from the left pane > [^tablename.PNG] > 4. Upload Table UI is not opening –BLOCKER > [^upload.PNG] > 5. Views button on top RHS, next to admin dropdown is not visible. > [^Views button.PNG] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21323) Hive view 2.0-UI issues on IE11 +Win 7
[ https://issues.apache.org/jira/browse/AMBARI-21323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21323: Resolution: Fixed Status: Resolved (was: Patch Available) > Hive view 2.0-UI issues on IE11 +Win 7 > -- > > Key: AMBARI-21323 > URL: https://issues.apache.org/jira/browse/AMBARI-21323 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21323-trunk.patch, hive properties.PNG, > partition.PNG, tablename.PNG, upload.PNG, Views button.PNG > > > 1. Not able to add hive properties-BLOCKER. > [^hive properties.PNG] > 2. Add partition wizard is not shows properly > [^partition.PNG] > 3. Long table name spills from the left pane > [^tablename.PNG] > 4. Upload Table UI is not opening –BLOCKER > [^upload.PNG] > 5. Views button on top RHS, next to admin dropdown is not visible. > [^Views button.PNG] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21323) Hive view 2.0-UI issues on IE11 +Win 7
[ https://issues.apache.org/jira/browse/AMBARI-21323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21323: Attachment: AMBARI-21323-trunk.patch > Hive view 2.0-UI issues on IE11 +Win 7 > -- > > Key: AMBARI-21323 > URL: https://issues.apache.org/jira/browse/AMBARI-21323 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21323-trunk.patch, hive properties.PNG, > partition.PNG, tablename.PNG, upload.PNG, Views button.PNG > > > 1. Not able to add hive properties-BLOCKER. > [^hive properties.PNG] > 2. Add partition wizard is not shows properly > [^partition.PNG] > 3. Long table name spills from the left pane > [^tablename.PNG] > 4. Upload Table UI is not opening –BLOCKER > [^upload.PNG] > 5. Views button on top RHS, next to admin dropdown is not visible. > [^Views button.PNG] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21323) Hive view 2.0-UI issues on IE11 +Win 7
[ https://issues.apache.org/jira/browse/AMBARI-21323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21323: Description: 1. Not able to add hive properties-BLOCKER. [^hive properties.PNG] 2. Add partition wizard is not shows properly [^partition.PNG] 3. Long table name spills from the left pane [^tablename.PNG] 4. Upload Table UI is not opening –BLOCKER [^upload.PNG] 5. Views button on top RHS, next to admin dropdown is not visible. [^Views button.PNG] > Hive view 2.0-UI issues on IE11 +Win 7 > -- > > Key: AMBARI-21323 > URL: https://issues.apache.org/jira/browse/AMBARI-21323 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: hive properties.PNG, partition.PNG, tablename.PNG, > upload.PNG, Views button.PNG > > > 1. Not able to add hive properties-BLOCKER. > [^hive properties.PNG] > 2. Add partition wizard is not shows properly > [^partition.PNG] > 3. Long table name spills from the left pane > [^tablename.PNG] > 4. Upload Table UI is not opening –BLOCKER > [^upload.PNG] > 5. Views button on top RHS, next to admin dropdown is not visible. > [^Views button.PNG] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21323) Hive view 2.0-UI issues on IE11 +Win 7
[ https://issues.apache.org/jira/browse/AMBARI-21323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21323: Attachment: hive properties.PNG partition.PNG tablename.PNG upload.PNG Views button.PNG > Hive view 2.0-UI issues on IE11 +Win 7 > -- > > Key: AMBARI-21323 > URL: https://issues.apache.org/jira/browse/AMBARI-21323 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: hive properties.PNG, partition.PNG, tablename.PNG, > upload.PNG, Views button.PNG > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21323) Hive view 2.0-UI issues on IE11 +Win 7
venkat created AMBARI-21323: --- Summary: Hive view 2.0-UI issues on IE11 +Win 7 Key: AMBARI-21323 URL: https://issues.apache.org/jira/browse/AMBARI-21323 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.2 Reporter: venkat Assignee: venkat Fix For: 2.5.2 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21292) Convert Slider View to use yarn package manager
[ https://issues.apache.org/jira/browse/AMBARI-21292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21292: Resolution: Fixed Status: Resolved (was: Patch Available) > Convert Slider View to use yarn package manager > --- > > Key: AMBARI-21292 > URL: https://issues.apache.org/jira/browse/AMBARI-21292 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21292-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21292) Convert Slider View to use yarn package manager
[ https://issues.apache.org/jira/browse/AMBARI-21292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21292: Status: Patch Available (was: Open) > Convert Slider View to use yarn package manager > --- > > Key: AMBARI-21292 > URL: https://issues.apache.org/jira/browse/AMBARI-21292 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21292-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21292) Convert Slider View to use yarn package manager
[ https://issues.apache.org/jira/browse/AMBARI-21292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16058859#comment-16058859 ] venkat commented on AMBARI-21292: - Committed to trunk and branch-2.5. > Convert Slider View to use yarn package manager > --- > > Key: AMBARI-21292 > URL: https://issues.apache.org/jira/browse/AMBARI-21292 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21292-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21252) Namenode variable should be auto populated for FS action node
[ https://issues.apache.org/jira/browse/AMBARI-21252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16058856#comment-16058856 ] venkat commented on AMBARI-21252: - Committed to trunk and branch-2.5. > Namenode variable should be auto populated for FS action node > - > > Key: AMBARI-21252 > URL: https://issues.apache.org/jira/browse/AMBARI-21252 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21252-branch-2.5.2.patch, > AMBARI-21252-branch-2.5.2-updated.patch, AMBARI-21252-trunk-updated.patch > > > Namenode variable should be auto populated for FS action node. Right now this > field is coming as blank and FS action fails on submission of the workflow. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21252) Namenode variable should be auto populated for FS action node
[ https://issues.apache.org/jira/browse/AMBARI-21252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21252: Resolution: Fixed Status: Resolved (was: Patch Available) > Namenode variable should be auto populated for FS action node > - > > Key: AMBARI-21252 > URL: https://issues.apache.org/jira/browse/AMBARI-21252 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21252-branch-2.5.2.patch, > AMBARI-21252-branch-2.5.2-updated.patch, AMBARI-21252-trunk-updated.patch > > > Namenode variable should be auto populated for FS action node. Right now this > field is coming as blank and FS action fails on submission of the workflow. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21252) Namenode variable should be auto populated for FS action node
[ https://issues.apache.org/jira/browse/AMBARI-21252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21252: Status: Patch Available (was: Open) > Namenode variable should be auto populated for FS action node > - > > Key: AMBARI-21252 > URL: https://issues.apache.org/jira/browse/AMBARI-21252 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21252-branch-2.5.2.patch, > AMBARI-21252-branch-2.5.2-updated.patch, AMBARI-21252-trunk-updated.patch > > > Namenode variable should be auto populated for FS action node. Right now this > field is coming as blank and FS action fails on submission of the workflow. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21266) Workflow submission fails when action node names contain white space
[ https://issues.apache.org/jira/browse/AMBARI-21266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21266: Resolution: Fixed Status: Resolved (was: Patch Available) > Workflow submission fails when action node names contain white space > > > Key: AMBARI-21266 > URL: https://issues.apache.org/jira/browse/AMBARI-21266 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21266-trunk.patch > > > Workflow submission fails when action node names contain white space. So > workflow designer should check for white space in action node name and prompt > appropriate error. > If action node name is not proper, user should not be allowed preview xml, > validate or submit the workflow. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21266) Workflow submission fails when action node names contain white space
[ https://issues.apache.org/jira/browse/AMBARI-21266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16058848#comment-16058848 ] venkat commented on AMBARI-21266: - Committed to trunk and branch-2.5. > Workflow submission fails when action node names contain white space > > > Key: AMBARI-21266 > URL: https://issues.apache.org/jira/browse/AMBARI-21266 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21266-trunk.patch > > > Workflow submission fails when action node names contain white space. So > workflow designer should check for white space in action node name and prompt > appropriate error. > If action node name is not proper, user should not be allowed preview xml, > validate or submit the workflow. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21266) Workflow submission fails when action node names contain white space
[ https://issues.apache.org/jira/browse/AMBARI-21266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21266: Status: Patch Available (was: Open) > Workflow submission fails when action node names contain white space > > > Key: AMBARI-21266 > URL: https://issues.apache.org/jira/browse/AMBARI-21266 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21266-trunk.patch > > > Workflow submission fails when action node names contain white space. So > workflow designer should check for white space in action node name and prompt > appropriate error. > If action node name is not proper, user should not be allowed preview xml, > validate or submit the workflow. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21255) Remove YARN client mode option from WFM
[ https://issues.apache.org/jira/browse/AMBARI-21255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21255: Status: Patch Available (was: Open) > Remove YARN client mode option from WFM > --- > > Key: AMBARI-21255 > URL: https://issues.apache.org/jira/browse/AMBARI-21255 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21255-branch-2.5.2-updated.patch > > > Today, Spark does not support YARN Client mode and hence, WFM/Oozie should > not provide YARN Client mode option. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21264) Integrate new hdfs-file browser in WFD
[ https://issues.apache.org/jira/browse/AMBARI-21264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21264: Component/s: ambari-views > Integrate new hdfs-file browser in WFD > -- > > Key: AMBARI-21264 > URL: https://issues.apache.org/jira/browse/AMBARI-21264 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21264-trunk.patch > > > HDFS directory viewer component used in views which have to be changed from > tree view to list view should be integrated in WFD -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21264) Integrate new hdfs-file browser in WFD
[ https://issues.apache.org/jira/browse/AMBARI-21264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21264: Fix Version/s: 2.5.2 > Integrate new hdfs-file browser in WFD > -- > > Key: AMBARI-21264 > URL: https://issues.apache.org/jira/browse/AMBARI-21264 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21264-trunk.patch > > > HDFS directory viewer component used in views which have to be changed from > tree view to list view should be integrated in WFD -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21264) Integrate new hdfs-file browser in WFD
[ https://issues.apache.org/jira/browse/AMBARI-21264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21264: Affects Version/s: 2.5.2 > Integrate new hdfs-file browser in WFD > -- > > Key: AMBARI-21264 > URL: https://issues.apache.org/jira/browse/AMBARI-21264 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21264-trunk.patch > > > HDFS directory viewer component used in views which have to be changed from > tree view to list view should be integrated in WFD -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21255) Remove YARN client mode option from WFM
[ https://issues.apache.org/jira/browse/AMBARI-21255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16058840#comment-16058840 ] venkat commented on AMBARI-21255: - Committed to trunk and branch-2.5. > Remove YARN client mode option from WFM > --- > > Key: AMBARI-21255 > URL: https://issues.apache.org/jira/browse/AMBARI-21255 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21255-branch-2.5.2-updated.patch > > > Today, Spark does not support YARN Client mode and hence, WFM/Oozie should > not provide YARN Client mode option. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21264) Integrate new hdfs-file browser in WFD
[ https://issues.apache.org/jira/browse/AMBARI-21264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16058835#comment-16058835 ] venkat commented on AMBARI-21264: - Committed to trunk and branch-2.5. > Integrate new hdfs-file browser in WFD > -- > > Key: AMBARI-21264 > URL: https://issues.apache.org/jira/browse/AMBARI-21264 > Project: Ambari > Issue Type: Bug >Reporter: venkat >Assignee: venkat > Attachments: AMBARI-21264-trunk.patch > > > HDFS directory viewer component used in views which have to be changed from > tree view to list view should be integrated in WFD -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21264) Integrate new hdfs-file browser in WFD
[ https://issues.apache.org/jira/browse/AMBARI-21264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21264: Status: Patch Available (was: Open) > Integrate new hdfs-file browser in WFD > -- > > Key: AMBARI-21264 > URL: https://issues.apache.org/jira/browse/AMBARI-21264 > Project: Ambari > Issue Type: Bug >Reporter: venkat >Assignee: venkat > Attachments: AMBARI-21264-trunk.patch > > > HDFS directory viewer component used in views which have to be changed from > tree view to list view should be integrated in WFD -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21292) Convert Slider View to use yarn package manager
[ https://issues.apache.org/jira/browse/AMBARI-21292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21292: Attachment: AMBARI-21292-trunk.patch > Convert Slider View to use yarn package manager > --- > > Key: AMBARI-21292 > URL: https://issues.apache.org/jira/browse/AMBARI-21292 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21292-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21252) Namenode variable should be auto populated for FS action node
[ https://issues.apache.org/jira/browse/AMBARI-21252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21252: Attachment: AMBARI-21252-trunk-updated.patch > Namenode variable should be auto populated for FS action node > - > > Key: AMBARI-21252 > URL: https://issues.apache.org/jira/browse/AMBARI-21252 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21252-branch-2.5.2.patch, > AMBARI-21252-branch-2.5.2-updated.patch, AMBARI-21252-trunk-updated.patch > > > Namenode variable should be auto populated for FS action node. Right now this > field is coming as blank and FS action fails on submission of the workflow. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21292) Convert Slider View to use yarn package manager
venkat created AMBARI-21292: --- Summary: Convert Slider View to use yarn package manager Key: AMBARI-21292 URL: https://issues.apache.org/jira/browse/AMBARI-21292 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.2 Reporter: venkat Assignee: venkat Fix For: 2.5.2 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21252) Namenode variable should be auto populated for FS action node
[ https://issues.apache.org/jira/browse/AMBARI-21252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21252: Attachment: AMBARI-21252-branch-2.5.2-updated.patch > Namenode variable should be auto populated for FS action node > - > > Key: AMBARI-21252 > URL: https://issues.apache.org/jira/browse/AMBARI-21252 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21252-branch-2.5.2.patch, > AMBARI-21252-branch-2.5.2-updated.patch > > > Namenode variable should be auto populated for FS action node. Right now this > field is coming as blank and FS action fails on submission of the workflow. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21255) Remove YARN client mode option from WFM
[ https://issues.apache.org/jira/browse/AMBARI-21255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21255: Attachment: AMBARI-21255-branch-2.5.2-updated.patch > Remove YARN client mode option from WFM > --- > > Key: AMBARI-21255 > URL: https://issues.apache.org/jira/browse/AMBARI-21255 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21255-branch-2.5.2-updated.patch > > > Today, Spark does not support YARN Client mode and hence, WFM/Oozie should > not provide YARN Client mode option. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21266) Workflow submission fails when action node names contain white space
[ https://issues.apache.org/jira/browse/AMBARI-21266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21266: Attachment: AMBARI-21266-trunk.patch > Workflow submission fails when action node names contain white space > > > Key: AMBARI-21266 > URL: https://issues.apache.org/jira/browse/AMBARI-21266 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21266-trunk.patch > > > Workflow submission fails when action node names contain white space. So > workflow designer should check for white space in action node name and prompt > appropriate error. > If action node name is not proper, user should not be allowed preview xml, > validate or submit the workflow. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21266) Workflow submission fails when action node names contain white space
venkat created AMBARI-21266: --- Summary: Workflow submission fails when action node names contain white space Key: AMBARI-21266 URL: https://issues.apache.org/jira/browse/AMBARI-21266 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.2 Reporter: venkat Assignee: venkat Fix For: 2.5.2 Workflow submission fails when action node names contain white space. So workflow designer should check for white space in action node name and prompt appropriate error. If action node name is not proper, user should not be allowed preview xml, validate or submit the workflow. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21264) Integrate new hdfs-file browser in WFD
[ https://issues.apache.org/jira/browse/AMBARI-21264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21264: Attachment: AMBARI-21264-trunk.patch > Integrate new hdfs-file browser in WFD > -- > > Key: AMBARI-21264 > URL: https://issues.apache.org/jira/browse/AMBARI-21264 > Project: Ambari > Issue Type: Bug >Reporter: venkat >Assignee: venkat > Attachments: AMBARI-21264-trunk.patch > > > HDFS directory viewer component used in views which have to be changed from > tree view to list view should be integrated in WFD -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21264) Integrate new hdfs-file browser in WFD
venkat created AMBARI-21264: --- Summary: Integrate new hdfs-file browser in WFD Key: AMBARI-21264 URL: https://issues.apache.org/jira/browse/AMBARI-21264 Project: Ambari Issue Type: Bug Reporter: venkat Assignee: venkat HDFS directory viewer component used in views which have to be changed from tree view to list view should be integrated in WFD -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21153) Hdfs directory viewer should be changed from tree view to list view.
[ https://issues.apache.org/jira/browse/AMBARI-21153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21153: Resolution: Fixed Status: Resolved (was: Patch Available) > Hdfs directory viewer should be changed from tree view to list view. > > > Key: AMBARI-21153 > URL: https://issues.apache.org/jira/browse/AMBARI-21153 > Project: Ambari > Issue Type: Improvement > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21153-trunk.01.patch, AMBARI-21153-trunk.patch > > > HDFS directory viewer component used in views have to be changed from tree > view to list view. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21153) Hdfs directory viewer should be changed from tree view to list view.
[ https://issues.apache.org/jira/browse/AMBARI-21153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21153: Status: Patch Available (was: Open) > Hdfs directory viewer should be changed from tree view to list view. > > > Key: AMBARI-21153 > URL: https://issues.apache.org/jira/browse/AMBARI-21153 > Project: Ambari > Issue Type: Improvement > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21153-trunk.01.patch, AMBARI-21153-trunk.patch > > > HDFS directory viewer component used in views have to be changed from tree > view to list view. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21153) Hdfs directory viewer should be changed from tree view to list view.
[ https://issues.apache.org/jira/browse/AMBARI-21153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16050345#comment-16050345 ] venkat commented on AMBARI-21153: - Committed to Trunk and branch-2.5. > Hdfs directory viewer should be changed from tree view to list view. > > > Key: AMBARI-21153 > URL: https://issues.apache.org/jira/browse/AMBARI-21153 > Project: Ambari > Issue Type: Improvement > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21153-trunk.01.patch, AMBARI-21153-trunk.patch > > > HDFS directory viewer component used in views have to be changed from tree > view to list view. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21153) Hdfs directory viewer should be changed from tree view to list view.
[ https://issues.apache.org/jira/browse/AMBARI-21153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21153: Attachment: AMBARI-21153-trunk.01.patch > Hdfs directory viewer should be changed from tree view to list view. > > > Key: AMBARI-21153 > URL: https://issues.apache.org/jira/browse/AMBARI-21153 > Project: Ambari > Issue Type: Improvement > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21153-trunk.01.patch, AMBARI-21153-trunk.patch > > > HDFS directory viewer component used in views have to be changed from tree > view to list view. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21255) Remove YARN client mode option from WFM
venkat created AMBARI-21255: --- Summary: Remove YARN client mode option from WFM Key: AMBARI-21255 URL: https://issues.apache.org/jira/browse/AMBARI-21255 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.2 Reporter: venkat Assignee: venkat Fix For: 2.5.2 Today, Spark does not support YARN Client mode and hence, WFM/Oozie should not provide YARN Client mode option. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21252) Namenode variable should be auto populated for FS action node
[ https://issues.apache.org/jira/browse/AMBARI-21252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21252: Attachment: AMBARI-21252-branch-2.5.2.patch > Namenode variable should be auto populated for FS action node > - > > Key: AMBARI-21252 > URL: https://issues.apache.org/jira/browse/AMBARI-21252 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21252-branch-2.5.2.patch > > > Namenode variable should be auto populated for FS action node. Right now this > field is coming as blank and FS action fails on submission of the workflow. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21252) Namenode variable should be auto populated for FS action node
venkat created AMBARI-21252: --- Summary: Namenode variable should be auto populated for FS action node Key: AMBARI-21252 URL: https://issues.apache.org/jira/browse/AMBARI-21252 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.2 Reporter: venkat Assignee: venkat Fix For: 2.5.2 Namenode variable should be auto populated for FS action node. Right now this field is coming as blank and FS action fails on submission of the workflow. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
