[jira] [Updated] (AMBARI-20135) Hive view 2.0 : Hanging query - no cancel available
[ https://issues.apache.org/jira/browse/AMBARI-20135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20135: -- Attachment: AMBARI-20135.1_branch-2.5.patch > Hive view 2.0 : Hanging query - no cancel available > --- > > Key: AMBARI-20135 > URL: https://issues.apache.org/jira/browse/AMBARI-20135 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.0 > > Attachments: AMBARI-20135.1_branch-2.5.patch, > AMBARI-20135_branch-2.5.patch > > > In Hive View 2.0 there is no way to cancel the current running job. > Need to have a cancel job button to stop current running job. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20133) Changes/Overwrites to Bundles and Coordinators Show as Workflow, Not able to select text from worflow 'Definition' tab
[ https://issues.apache.org/jira/browse/AMBARI-20133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15880046#comment-15880046 ] Hudson commented on AMBARI-20133: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1066 (See [https://builds.apache.org/job/Ambari-branch-2.5/1066/]) AMBARI-20133. Changes/Overwrites to Bundles and Coordinators Show as (pallavkul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4c613754c0610fe0624bfaa896a3588d0a7b489b]) * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/save-wf.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/styles/app.less * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/save-wf.hbs > Changes/Overwrites to Bundles and Coordinators Show as Workflow, Not able to > select text from worflow 'Definition' tab > -- > > Key: AMBARI-20133 > URL: https://issues.apache.org/jira/browse/AMBARI-20133 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-20133.branch-2.5.patch > > > When saving and/or overwriting coordinator or bundle files, UI appears to > have a typo. States that "Workflow" has been saved instead. > Not able to select text from workflow 'Definition' tab. > Dashboard - Select Workflow - Definition Tab - try selecting text. (browser: > chrome) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20134) Improper action node name after importing the asset
[ https://issues.apache.org/jira/browse/AMBARI-20134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15880045#comment-15880045 ] Hudson commented on AMBARI-20134: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1066 (See [https://builds.apache.org/job/Ambari-branch-2.5/1066/]) AMBARI-20134. Improper action node name after importing the asset (pallavkul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=bb568139d6d27bedc64f3a82ad05456cb4b4a255]) * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/workflow.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/flow-designer.js > Improper action node name after importing the asset > --- > > Key: AMBARI-20134 > URL: https://issues.apache.org/jira/browse/AMBARI-20134 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-20134.branch-2.5.patch > > > Action node name is not proper after importing asset. Once user imports the > asset, the node name is displayed as _undefined. > Instead of this, if there are no other action nodes of this type, then just > show the actual node name. > And if there are already existing nodes of this type, then show > _. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20127) Hive 2: "insert udf" opens empty drop down
[ https://issues.apache.org/jira/browse/AMBARI-20127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15880043#comment-15880043 ] Hudson commented on AMBARI-20127: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6822 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6822/]) AMBARI-20127. Hive 2: "insert udf" opens empty drop down (pallavkul) (pallavkul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=03d0587e2e29d7f9b28844b7dfe2042813947dd6]) * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/queries/query.js * (edit) contrib/views/hive20/src/main/resources/ui/app/templates/queries/query.hbs > Hive 2: "insert udf" opens empty drop down > -- > > Key: AMBARI-20127 > URL: https://issues.apache.org/jira/browse/AMBARI-20127 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Pallav Kulshreshtha > Fix For: 2.5.0 > > Attachments: AMBARI-20127-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20133) Changes/Overwrites to Bundles and Coordinators Show as Workflow, Not able to select text from worflow 'Definition' tab
[ https://issues.apache.org/jira/browse/AMBARI-20133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-20133: - Resolution: Fixed Status: Resolved (was: Patch Available) > Changes/Overwrites to Bundles and Coordinators Show as Workflow, Not able to > select text from worflow 'Definition' tab > -- > > Key: AMBARI-20133 > URL: https://issues.apache.org/jira/browse/AMBARI-20133 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-20133.branch-2.5.patch > > > When saving and/or overwriting coordinator or bundle files, UI appears to > have a typo. States that "Workflow" has been saved instead. > Not able to select text from workflow 'Definition' tab. > Dashboard - Select Workflow - Definition Tab - try selecting text. (browser: > chrome) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20135) Hive view 2.0 : Hanging query - no cancel available
[ https://issues.apache.org/jira/browse/AMBARI-20135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20135: -- Status: Patch Available (was: Open) > Hive view 2.0 : Hanging query - no cancel available > --- > > Key: AMBARI-20135 > URL: https://issues.apache.org/jira/browse/AMBARI-20135 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.0 > > Attachments: AMBARI-20135_branch-2.5.patch > > > In Hive View 2.0 there is no way to cancel the current running job. > Need to have a cancel job button to stop current running job. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20136) Services should be able to specify that credential store is always enabled
[
https://issues.apache.org/jira/browse/AMBARI-20136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-20136:
---
Status: Patch Available (was: Open)
> Services should be able to specify that credential store is always enabled
> --
>
> Key: AMBARI-20136
> URL: https://issues.apache.org/jira/browse/AMBARI-20136
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20136.patch
>
>
> At this point, credential store can be enabled or disabled for a service.
> Some services, such as Ranger and LogSearch should be able to indicate that
> CS cannot be disabled. The eventual goal is to always have CS enabled for all
> services that support credential store.
> Current metainfo.xml has the following section
> {code}
>
> true
> false
>
> {code}
> We need to add a notion of required. A third element called "required" may be
> added. We can potentially, create an enum for a new field "supportType" and
> collapse "supported" and "required" but that, while succinct, does not help
> much in readability.
> {code}
>
> true
> false
> false
>
> {code}
> The above means, CS is supported, not required, and not enabled. "false" is
> the default for *required*.
> For services that require CS support
> {code}
>
> true
> true
> true
>
> {code}
> Service create logic should set the CS-enabled flag to be true if *required*
> is true independent of what *enabled* says. *required* flag is not needed in
> the service resource REST API but the stacks API should provide access to
> this flag.
> API to disable CS should throw an error if *required* is true.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20136) Services should be able to specify that credential store is always enabled
[
https://issues.apache.org/jira/browse/AMBARI-20136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-20136:
---
Attachment: AMBARI-20136.patch
> Services should be able to specify that credential store is always enabled
> --
>
> Key: AMBARI-20136
> URL: https://issues.apache.org/jira/browse/AMBARI-20136
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20136.patch
>
>
> At this point, credential store can be enabled or disabled for a service.
> Some services, such as Ranger and LogSearch should be able to indicate that
> CS cannot be disabled. The eventual goal is to always have CS enabled for all
> services that support credential store.
> Current metainfo.xml has the following section
> {code}
>
> true
> false
>
> {code}
> We need to add a notion of required. A third element called "required" may be
> added. We can potentially, create an enum for a new field "supportType" and
> collapse "supported" and "required" but that, while succinct, does not help
> much in readability.
> {code}
>
> true
> false
> false
>
> {code}
> The above means, CS is supported, not required, and not enabled. "false" is
> the default for *required*.
> For services that require CS support
> {code}
>
> true
> true
> true
>
> {code}
> Service create logic should set the CS-enabled flag to be true if *required*
> is true independent of what *enabled* says. *required* flag is not needed in
> the service resource REST API but the stacks API should provide access to
> this flag.
> API to disable CS should throw an error if *required* is true.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20136) Services should be able to specify that credential store is always enabled
[
https://issues.apache.org/jira/browse/AMBARI-20136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-20136:
---
Issue Type: Task (was: Bug)
> Services should be able to specify that credential store is always enabled
> --
>
> Key: AMBARI-20136
> URL: https://issues.apache.org/jira/browse/AMBARI-20136
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.0
>
>
> At this point, credential store can be enabled or disabled for a service.
> Some services, such as Ranger and LogSearch should be able to indicate that
> CS cannot be disabled. The eventual goal is to always have CS enabled for all
> services that support credential store.
> Current metainfo.xml has the following section
> {code}
>
> true
> false
>
> {code}
> We need to add a notion of required. A third element called "required" may be
> added. We can potentially, create an enum for a new field "supportType" and
> collapse "supported" and "required" but that, while succinct, does not help
> much in readability.
> {code}
>
> true
> false
> false
>
> {code}
> The above means, CS is supported, not required, and not enabled. "false" is
> the default for *required*.
> For services that require CS support
> {code}
>
> true
> true
> true
>
> {code}
> Service create logic should set the CS-enabled flag to be true if *required*
> is true independent of what *enabled* says. *required* flag is not needed in
> the service resource REST API but the stacks API should provide access to
> this flag.
> API to disable CS should throw an error if *required* is true.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20127) Hive 2: "insert udf" opens empty drop down
[ https://issues.apache.org/jira/browse/AMBARI-20127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15880030#comment-15880030 ] Hudson commented on AMBARI-20127: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1065 (See [https://builds.apache.org/job/Ambari-branch-2.5/1065/]) AMBARI-20127. Hive 2: "insert udf" opens empty drop down (pallavkul) (pallavkul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b24585f62f852ba1491e623bf241908bc54424f1]) * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/queries/query.js * (edit) contrib/views/hive20/src/main/resources/ui/app/templates/queries/query.hbs > Hive 2: "insert udf" opens empty drop down > -- > > Key: AMBARI-20127 > URL: https://issues.apache.org/jira/browse/AMBARI-20127 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Pallav Kulshreshtha > Fix For: 2.5.0 > > Attachments: AMBARI-20127-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20135) Hive view 2.0 : Hanging query - no cancel available
[ https://issues.apache.org/jira/browse/AMBARI-20135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20135: -- Component/s: ambari-views > Hive view 2.0 : Hanging query - no cancel available > --- > > Key: AMBARI-20135 > URL: https://issues.apache.org/jira/browse/AMBARI-20135 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.0 > > Attachments: AMBARI-20135_branch-2.5.patch > > > In Hive View 2.0 there is no way to cancel the current running job. > Need to have a cancel job button to stop current running job. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20136) Services should be able to specify that credential store is always enabled
Sumit Mohanty created AMBARI-20136:
--
Summary: Services should be able to specify that credential store
is always enabled
Key: AMBARI-20136
URL: https://issues.apache.org/jira/browse/AMBARI-20136
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.0
Reporter: Sumit Mohanty
Assignee: Sumit Mohanty
Priority: Critical
Fix For: 2.5.0
At this point, credential store can be enabled or disabled for a service. Some
services, such as Ranger and LogSearch should be able to indicate that CS
cannot be disabled. The eventual goal is to always have CS enabled for all
services that support credential store.
Current metainfo.xml has the following section
{code}
true
false
{code}
We need to add a notion of required. A third element called "required" may be
added. We can potentially, create an enum for a new field "supportType" and
collapse "supported" and "required" but that, while succinct, does not help
much in readability.
{code}
true
false
false
{code}
The above means, CS is supported, not required, and not enabled. "false" is the
default for *required*.
For services that require CS support
{code}
true
true
true
{code}
Service create logic should set the CS-enabled flag to be true if *required* is
true independent of what *enabled* says. *required* flag is not needed in the
service resource REST API but the stacks API should provide access to this flag.
API to disable CS should throw an error if *required* is true.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20135) Hive view 2.0 : Hanging query - no cancel available
[ https://issues.apache.org/jira/browse/AMBARI-20135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20135: -- Attachment: AMBARI-20135_branch-2.5.patch > Hive view 2.0 : Hanging query - no cancel available > --- > > Key: AMBARI-20135 > URL: https://issues.apache.org/jira/browse/AMBARI-20135 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: 2.5.0 > > Attachments: AMBARI-20135_branch-2.5.patch > > > In Hive View 2.0 there is no way to cancel the current running job. > Need to have a cancel job button to stop current running job. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20133) Changes/Overwrites to Bundles and Coordinators Show as Workflow, Not able to select text from worflow 'Definition' tab
[ https://issues.apache.org/jira/browse/AMBARI-20133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-20133: Status: Patch Available (was: Open) > Changes/Overwrites to Bundles and Coordinators Show as Workflow, Not able to > select text from worflow 'Definition' tab > -- > > Key: AMBARI-20133 > URL: https://issues.apache.org/jira/browse/AMBARI-20133 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-20133.branch-2.5.patch > > > When saving and/or overwriting coordinator or bundle files, UI appears to > have a typo. States that "Workflow" has been saved instead. > Not able to select text from workflow 'Definition' tab. > Dashboard - Select Workflow - Definition Tab - try selecting text. (browser: > chrome) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20135) Hive view 2.0 : Hanging query - no cancel available
Gaurav Nagar created AMBARI-20135: - Summary: Hive view 2.0 : Hanging query - no cancel available Key: AMBARI-20135 URL: https://issues.apache.org/jira/browse/AMBARI-20135 Project: Ambari Issue Type: Bug Affects Versions: 2.5.0 Reporter: Gaurav Nagar Assignee: Gaurav Nagar Fix For: 2.5.0 In Hive View 2.0 there is no way to cancel the current running job. Need to have a cancel job button to stop current running job. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20134) Improper action node name after importing the asset
[ https://issues.apache.org/jira/browse/AMBARI-20134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-20134: - Resolution: Fixed Status: Resolved (was: Patch Available) > Improper action node name after importing the asset > --- > > Key: AMBARI-20134 > URL: https://issues.apache.org/jira/browse/AMBARI-20134 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-20134.branch-2.5.patch > > > Action node name is not proper after importing asset. Once user imports the > asset, the node name is displayed as _undefined. > Instead of this, if there are no other action nodes of this type, then just > show the actual node name. > And if there are already existing nodes of this type, then show > _. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20134) Improper action node name after importing the asset
[ https://issues.apache.org/jira/browse/AMBARI-20134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-20134: - Status: Patch Available (was: Open) > Improper action node name after importing the asset > --- > > Key: AMBARI-20134 > URL: https://issues.apache.org/jira/browse/AMBARI-20134 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-20134.branch-2.5.patch > > > Action node name is not proper after importing asset. Once user imports the > asset, the node name is displayed as _undefined. > Instead of this, if there are no other action nodes of this type, then just > show the actual node name. > And if there are already existing nodes of this type, then show > _. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20134) Improper action node name after importing the asset
[ https://issues.apache.org/jira/browse/AMBARI-20134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-20134: Attachment: AMBARI-20134.branch-2.5.patch > Improper action node name after importing the asset > --- > > Key: AMBARI-20134 > URL: https://issues.apache.org/jira/browse/AMBARI-20134 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-20134.branch-2.5.patch > > > Action node name is not proper after importing asset. Once user imports the > asset, the node name is displayed as _undefined. > Instead of this, if there are no other action nodes of this type, then just > show the actual node name. > And if there are already existing nodes of this type, then show > _. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20134) Improper action node name after importing the asset
venkat created AMBARI-20134: --- Summary: Improper action node name after importing the asset Key: AMBARI-20134 URL: https://issues.apache.org/jira/browse/AMBARI-20134 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: venkat Assignee: venkat Fix For: 2.5.0 Action node name is not proper after importing asset. Once user imports the asset, the node name is displayed as _undefined. Instead of this, if there are no other action nodes of this type, then just show the actual node name. And if there are already existing nodes of this type, then show _. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20093) Cannot edit join node name in Workflow Manager
[ https://issues.apache.org/jira/browse/AMBARI-20093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879986#comment-15879986 ] Hudson commented on AMBARI-20093: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1064 (See [https://builds.apache.org/job/Ambari-branch-2.5/1064/]) AMBARI-20093. Cannot edit join node name in Workflow Manager.(Belliraj (grvngr: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7152be6e5b7f59eddb98fb5bd250aa0f54331178]) * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/cytoscape-flow-renderer.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/cytoscape-style.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/flow-designer.hbs > Cannot edit join node name in Workflow Manager > -- > > Key: AMBARI-20093 > URL: https://issues.apache.org/jira/browse/AMBARI-20093 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Belliraj HB >Assignee: Belliraj HB >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20093_trunk.patch > > > After create a fork node, the join node will generated automatically. But, I > cannot edit the name of the join node. Only action I can take to that join > node is delete. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20093) Cannot edit join node name in Workflow Manager
[ https://issues.apache.org/jira/browse/AMBARI-20093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879975#comment-15879975 ] Hudson commented on AMBARI-20093: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6821 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6821/]) AMBARI-20093. Cannot edit join node name in Workflow Manager.(Belliraj (grvngr: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5186db06659916148229fbd02aa742b7caeaa2f9]) * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/flow-designer.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/cytoscape-style.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/domain/cytoscape-flow-renderer.js > Cannot edit join node name in Workflow Manager > -- > > Key: AMBARI-20093 > URL: https://issues.apache.org/jira/browse/AMBARI-20093 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Belliraj HB >Assignee: Belliraj HB >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20093_trunk.patch > > > After create a fork node, the join node will generated automatically. But, I > cannot edit the name of the join node. Only action I can take to that join > node is delete. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20133) Changes/Overwrites to Bundles and Coordinators Show as Workflow, Not able to select text from worflow 'Definition' tab
[ https://issues.apache.org/jira/browse/AMBARI-20133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-20133: Attachment: AMBARI-20133.branch-2.5.patch > Changes/Overwrites to Bundles and Coordinators Show as Workflow, Not able to > select text from worflow 'Definition' tab > -- > > Key: AMBARI-20133 > URL: https://issues.apache.org/jira/browse/AMBARI-20133 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: AMBARI-20133.branch-2.5.patch > > > When saving and/or overwriting coordinator or bundle files, UI appears to > have a typo. States that "Workflow" has been saved instead. > Not able to select text from workflow 'Definition' tab. > Dashboard - Select Workflow - Definition Tab - try selecting text. (browser: > chrome) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20133) Changes/Overwrites to Bundles and Coordinators Show as Workflow, Not able to select text from worflow 'Definition' tab
venkat created AMBARI-20133: --- Summary: Changes/Overwrites to Bundles and Coordinators Show as Workflow, Not able to select text from worflow 'Definition' tab Key: AMBARI-20133 URL: https://issues.apache.org/jira/browse/AMBARI-20133 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: venkat Assignee: venkat Fix For: 2.5.0 When saving and/or overwriting coordinator or bundle files, UI appears to have a typo. States that "Workflow" has been saved instead. Not able to select text from workflow 'Definition' tab. Dashboard - Select Workflow - Definition Tab - try selecting text. (browser: chrome) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20109) HDP stack - enable shuffle connection keep-alive
[ https://issues.apache.org/jira/browse/AMBARI-20109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated AMBARI-20109: Status: Open (was: Patch Available) Cancelling the patch for now. The config changes need some more behaviour verification. > HDP stack - enable shuffle connection keep-alive > > > Key: AMBARI-20109 > URL: https://issues.apache.org/jira/browse/AMBARI-20109 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > Attachments: AMBARI-20109.01.patch, AMBARI-20109.02.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20127) Hive 2: "insert udf" opens empty drop down
[
https://issues.apache.org/jira/browse/AMBARI-20127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879946#comment-15879946
]
Hadoop QA commented on AMBARI-20127:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12854125/AMBARI-20127-trunk.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10699//console
This message is automatically generated.
> Hive 2: "insert udf" opens empty drop down
> --
>
> Key: AMBARI-20127
> URL: https://issues.apache.org/jira/browse/AMBARI-20127
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Pallav Kulshreshtha
> Fix For: 2.5.0
>
> Attachments: AMBARI-20127-trunk.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20127) Hive 2: "insert udf" opens empty drop down
[ https://issues.apache.org/jira/browse/AMBARI-20127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-20127: - Resolution: Fixed Status: Resolved (was: Patch Available) > Hive 2: "insert udf" opens empty drop down > -- > > Key: AMBARI-20127 > URL: https://issues.apache.org/jira/browse/AMBARI-20127 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Pallav Kulshreshtha > Fix For: 2.5.0 > > Attachments: AMBARI-20127-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20109) HDP stack - enable shuffle connection keep-alive
[
https://issues.apache.org/jira/browse/AMBARI-20109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879943#comment-15879943
]
Hadoop QA commented on AMBARI-20109:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12854137/AMBARI-20109.02.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10698//console
This message is automatically generated.
> HDP stack - enable shuffle connection keep-alive
>
>
> Key: AMBARI-20109
> URL: https://issues.apache.org/jira/browse/AMBARI-20109
> Project: Ambari
> Issue Type: Task
> Components: stacks
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Fix For: 2.5.0
>
> Attachments: AMBARI-20109.01.patch, AMBARI-20109.02.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20107) Action node shows unsupported properties even though there are none in workflow manager.
[ https://issues.apache.org/jira/browse/AMBARI-20107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879939#comment-15879939 ] Hudson commented on AMBARI-20107: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1063 (See [https://builds.apache.org/job/Ambari-branch-2.5/1063/]) AMBARI-20107. Action node shows unsupported properties even though there (grvngr: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a0cfe6a7f0d57daa6c96feb90a1ea6ef362e74a6]) * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/workflow-action-editor.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/workflow-action-editor.js > Action node shows unsupported properties even though there are none in > workflow manager. > > > Key: AMBARI-20107 > URL: https://issues.apache.org/jira/browse/AMBARI-20107 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20107_trunk.patch > > > Action node during edit shows unsupported properties. But in unsupported > properties you see empty text. > Expected. > Unsupported properties should not be shown if there are no unsupported > properties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20093) Cannot edit join node name in Workflow Manager
[ https://issues.apache.org/jira/browse/AMBARI-20093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20093: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Cannot edit join node name in Workflow Manager > -- > > Key: AMBARI-20093 > URL: https://issues.apache.org/jira/browse/AMBARI-20093 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Belliraj HB >Assignee: Belliraj HB >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20093_trunk.patch > > > After create a fork node, the join node will generated automatically. But, I > cannot edit the name of the join node. Only action I can take to that join > node is delete. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20109) HDP stack - enable shuffle connection keep-alive
[ https://issues.apache.org/jira/browse/AMBARI-20109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated AMBARI-20109: Attachment: AMBARI-20109.02.patch Thanks for taking a look [~sumitmohanty], [~jonathan.hurley] Updated patch to address the review comments. Tests pass locally. Other than the fixes in the patch, I'd still like to make sure that these are the correct sections to put the configs. The configs affefct the NodeManagers, but are changed in mapred-site. After an upgrade - the configs need to be in place before the NM restarts. Since they affect the NodeManagers, I put them into a NM section. (Maybe they could have been in the RM section, or even a MapReduce section). > HDP stack - enable shuffle connection keep-alive > > > Key: AMBARI-20109 > URL: https://issues.apache.org/jira/browse/AMBARI-20109 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > Attachments: AMBARI-20109.01.patch, AMBARI-20109.02.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20107) Action node shows unsupported properties even though there are none in workflow manager.
[ https://issues.apache.org/jira/browse/AMBARI-20107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879897#comment-15879897 ] Hudson commented on AMBARI-20107: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6820 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6820/]) AMBARI-20107. Action node shows unsupported properties even though there (grvngr: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ba470c186875be371152e2a3ce37fb3c9a383f5a]) * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/workflow-action-editor.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/workflow-action-editor.hbs > Action node shows unsupported properties even though there are none in > workflow manager. > > > Key: AMBARI-20107 > URL: https://issues.apache.org/jira/browse/AMBARI-20107 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20107_trunk.patch > > > Action node during edit shows unsupported properties. But in unsupported > properties you see empty text. > Expected. > Unsupported properties should not be shown if there are no unsupported > properties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20107) Action node shows unsupported properties even though there are none in workflow manager.
[ https://issues.apache.org/jira/browse/AMBARI-20107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20107: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Action node shows unsupported properties even though there are none in > workflow manager. > > > Key: AMBARI-20107 > URL: https://issues.apache.org/jira/browse/AMBARI-20107 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20107_trunk.patch > > > Action node during edit shows unsupported properties. But in unsupported > properties you see empty text. > Expected. > Unsupported properties should not be shown if there are no unsupported > properties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20132) All the workflow details are getting logged in UI console log
Supreeth Sharma created AMBARI-20132: Summary: All the workflow details are getting logged in UI console log Key: AMBARI-20132 URL: https://issues.apache.org/jira/browse/AMBARI-20132 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Supreeth Sharma Fix For: 2.5.0 All the workflow details are getting logged in UI console log. Is this logging necessary ? Whether it will have performance implications in rendering the workflow ? Steps to reproduce : 1) Create a workflow. 2) Refresh the browser. 3) While loading the workflow, all the details are being logged in the UI console log -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20131) Workflow details are lost upon refreshing the browser
Supreeth Sharma created AMBARI-20131: Summary: Workflow details are lost upon refreshing the browser Key: AMBARI-20131 URL: https://issues.apache.org/jira/browse/AMBARI-20131 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Supreeth Sharma Priority: Critical Fix For: 2.5.0 Workflow details are lost upon refreshing the browser. Steps to reproduce : 1) Create a new workflow. 2) Now refresh the browser. 3) Upon refreshing, the previous workflow tab is not displayed and all the unsaved works are lost. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20130) UI is hung after clicking on error message link
Supreeth Sharma created AMBARI-20130: Summary: UI is hung after clicking on error message link Key: AMBARI-20130 URL: https://issues.apache.org/jira/browse/AMBARI-20130 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Supreeth Sharma Priority: Critical Fix For: 2.5.0 UI is hung after clicking on error message link. Steps to reproduce : 1) Publish an asset . 2) Now try to import the asset. 3) Once import is completed, open the settings for that particular action node. Invalid Error message "Action contains elements that are not currently supported by the designer." Once user clicks on this link, browser gets refreshed and its hung. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20129) Improper action node name after importing the asset
Supreeth Sharma created AMBARI-20129: Summary: Improper action node name after importing the asset Key: AMBARI-20129 URL: https://issues.apache.org/jira/browse/AMBARI-20129 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Supreeth Sharma Fix For: 2.5.0 Action node name is not proper after importing asset. Once user imports the asset, the node name is displayed as _undefined. Instead of this, if there are no other action nodes of this type, then just show the actual node name. And if there are already existing nodes of this type, then show _. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20109) HDP stack - enable shuffle connection keep-alive
[
https://issues.apache.org/jira/browse/AMBARI-20109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879836#comment-15879836
]
Jonathan Hurley commented on AMBARI-20109:
--
It looks like you added a {{pre-upgrade}} tag without a matching
{{pre-downgrade}}
{code}
+++ b/ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml
@@ -681,6 +681,9 @@
+
+
+
{code}
> HDP stack - enable shuffle connection keep-alive
>
>
> Key: AMBARI-20109
> URL: https://issues.apache.org/jira/browse/AMBARI-20109
> Project: Ambari
> Issue Type: Task
> Components: stacks
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Fix For: 2.5.0
>
> Attachments: AMBARI-20109.01.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20109) HDP stack - enable shuffle connection keep-alive
[
https://issues.apache.org/jira/browse/AMBARI-20109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879830#comment-15879830
]
Sumit Mohanty commented on AMBARI-20109:
Can you run unit tests with the patch - it fails
{code}
---
T E S T S
---
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m;
support was removed in 8.0
Running org.apache.ambari.server.state.stack.UpgradePackParsingTest
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.627 sec <<<
FAILURE! - in org.apache.ambari.server.state.stack.UpgradePackParsingTest
findAndValidateUpgradePacks(org.apache.ambari.server.state.stack.UpgradePackParsingTest)
Time elapsed: 1.626 sec <<< ERROR!
javax.xml.bind.UnmarshalException
at
org.apache.ambari.server.state.stack.UpgradePackParsingTest.findAndValidateUpgradePacks(UpgradePackParsingTest.java:86)
Caused by: java.lang.reflect.InvocationTargetException
at
org.apache.ambari.server.state.stack.UpgradePackParsingTest.findAndValidateUpgradePacks(UpgradePackParsingTest.java:86)
Caused by: java.lang.RuntimeException: Upgrade pack must contain pre-downgrade
elements if pre-upgrade exists for processing component YARN/NODEMANAGER
at
org.apache.ambari.server.state.stack.UpgradePackParsingTest.findAndValidateUpgradePacks(UpgradePackParsingTest.java:86)
Results :
Tests in error:
UpgradePackParsingTest.findAndValidateUpgradePacks:86 » Unmarshal
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
{code}
mvn clean install -pl
utility,ambari-views,ambari-metrics/ambari-metrics-common,ambari-server
-Dfindbugs.skip -Dtest=UpgradePackParsingTest -DfailIfNoTests=false
Also, it looks like the following chunk
{code}
mapred-site
{code}
is inside the service section for *OOZIE*. It should be in *YARN*.
You can include [~nc...@hortonworks.com] and [~jonathan.hurley] to review the
upgrade changes.
> HDP stack - enable shuffle connection keep-alive
>
>
> Key: AMBARI-20109
> URL: https://issues.apache.org/jira/browse/AMBARI-20109
> Project: Ambari
> Issue Type: Task
> Components: stacks
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Fix For: 2.5.0
>
> Attachments: AMBARI-20109.01.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20128) Invalid error message while importing asset
Supreeth Sharma created AMBARI-20128: Summary: Invalid error message while importing asset Key: AMBARI-20128 URL: https://issues.apache.org/jira/browse/AMBARI-20128 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Supreeth Sharma Priority: Critical Fix For: 2.5.0 Invalid error message is shown while importing asset. Its happening when user tries to import asset from hdfs as well as from the DB. Steps to reproduce : 1) Publish an asset . 2) Now try to import the asset. 3) Once import is completed, open the settings for that particular action node. Invalid Error message "Action contains elements that are not currently supported by the designer." Since the asset is as per workflow manager specification, this error message should not be shown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (AMBARI-18528) Need a way to escape config values that contain $
[
https://issues.apache.org/jira/browse/AMBARI-18528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15603928#comment-15603928
]
Ted Yu edited comment on AMBARI-18528 at 2/23/17 4:11 AM:
--
Escaping the dollar sign automatically is desirable.
was (Author: yuzhih...@gmail.com):
Escaping the dollar sign automatically is a desirable solution.
> Need a way to escape config values that contain $
> -
>
> Key: AMBARI-18528
> URL: https://issues.apache.org/jira/browse/AMBARI-18528
> Project: Ambari
> Issue Type: Bug
>Reporter: Ted Yu
> Labels: zookeeper
>
> We tried specifying auth_to_local in zookeeper env input box:
> {code}
> export SERVER_JVMFLAGS="$SERVER_JVMFLAGS
> -Dzookeeper.security.auth_to_local=RULE:[2:$1@$0](hb...@c.net)s/.*/hbase/
> -Djava.security.auth.login.config={{zk_server_jaas_file}}"
> {code}
> However, when zookeeper quorum starts, the rule got interrupted with
> zkServer.sh
> We should add the capability of specifying auth_to_local in Ambari UI
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20125) DataNode Storage alert is duplicated
[ https://issues.apache.org/jira/browse/AMBARI-20125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879814#comment-15879814 ] Hudson commented on AMBARI-20125: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1062 (See [https://builds.apache.org/job/Ambari-branch-2.5/1062/]) AMBARI-20125 - DataNode Storage alert is duplicated (rzang) (rzang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=602e0a3e23a3a0cab0ac0dd27bda6374017b1d43]) * (edit) ambari-web/app/controllers/main/service/info/summary.js > DataNode Storage alert is duplicated > > > Key: AMBARI-20125 > URL: https://issues.apache.org/jira/browse/AMBARI-20125 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20125.patch > > > In the HDFS alert popup, "DataNode Storage" item is duplicated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19989) Allow user to view Tez View after executing query
[ https://issues.apache.org/jira/browse/AMBARI-19989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-19989: - Resolution: Fixed Status: Resolved (was: Patch Available) > Allow user to view Tez View after executing query > - > > Key: AMBARI-19989 > URL: https://issues.apache.org/jira/browse/AMBARI-19989 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Labels: hive-view > Fix For: 2.5.0 > > Attachments: AMBARI-19989.01.branch-2.5.patch, > AMBARI-19989.02.branch-2.5..patch, AMBARI-19989.branch-2.5.patch > > > As per the parity with Hive View 1.5, allow user to traverse to tez view from > the query page after executing a query. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20127) Hive 2: "insert udf" opens empty drop down
[ https://issues.apache.org/jira/browse/AMBARI-20127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-20127: - Status: Patch Available (was: Open) > Hive 2: "insert udf" opens empty drop down > -- > > Key: AMBARI-20127 > URL: https://issues.apache.org/jira/browse/AMBARI-20127 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Pallav Kulshreshtha > Fix For: 2.5.0 > > Attachments: AMBARI-20127-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20127) Hive 2: "insert udf" opens empty drop down
[ https://issues.apache.org/jira/browse/AMBARI-20127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-20127: - Attachment: AMBARI-20127-trunk.patch > Hive 2: "insert udf" opens empty drop down > -- > > Key: AMBARI-20127 > URL: https://issues.apache.org/jira/browse/AMBARI-20127 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Pallav Kulshreshtha > Fix For: 2.5.0 > > Attachments: AMBARI-20127-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20127) Hive 2: "insert udf" opens empty drop down
Pallav Kulshreshtha created AMBARI-20127: Summary: Hive 2: "insert udf" opens empty drop down Key: AMBARI-20127 URL: https://issues.apache.org/jira/browse/AMBARI-20127 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Pallav Kulshreshtha Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20125) DataNode Storage alert is duplicated
[ https://issues.apache.org/jira/browse/AMBARI-20125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20125: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and 2.5 602e0a3e23a3a0cab0ac0dd27bda6374017b1d43 > DataNode Storage alert is duplicated > > > Key: AMBARI-20125 > URL: https://issues.apache.org/jira/browse/AMBARI-20125 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20125.patch > > > In the HDFS alert popup, "DataNode Storage" item is duplicated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20120) Error during EU while updating Ranger Log4J service configs
[
https://issues.apache.org/jira/browse/AMBARI-20120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879776#comment-15879776
]
Hadoop QA commented on AMBARI-20120:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12854067/AMBARI-20120.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10697//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10697//console
This message is automatically generated.
> Error during EU while updating Ranger Log4J service configs
> ---
>
> Key: AMBARI-20120
> URL: https://issues.apache.org/jira/browse/AMBARI-20120
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20120.patch
>
>
> Perform an HDP upgrade from 2.3 to 2.4 where Ranger is an installed service.
> *Result*
> Observed errors while updating below Ranger service configs:
> Updating configuration usersync-log4j
> Updating configuration admin-log4j
> {code}
> Server action failed
> Could not find desired config type with name admin-log4j
> {code}
> - Both {{usersync-log4j}} and {{admin-log4j}} appear in Ranger 0.6.0 which is
> first used by HDP 2.5. Therefore, the configuration changes should simply be
> removed from upgrades on stacks before HDP 2.5
> - Additionally, I found {{RANGER_TAGSYNC}} references in HDP 2.3 and HDP 2.4.
> This component also first appeared in Ranger 0.6.0, so it should also be
> removed from earlier upgrade packs.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20125) DataNode Storage alert is duplicated
[ https://issues.apache.org/jira/browse/AMBARI-20125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879773#comment-15879773 ] Hudson commented on AMBARI-20125: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6819 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6819/]) AMBARI-20125 - DataNode Storage alert is duplicated (rzang) (rzang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f936bcfdb3cc6451bd1fa82e0d6e98f2aec285df]) * (edit) ambari-web/app/controllers/main/service/info/summary.js > DataNode Storage alert is duplicated > > > Key: AMBARI-20125 > URL: https://issues.apache.org/jira/browse/AMBARI-20125 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20125.patch > > > In the HDFS alert popup, "DataNode Storage" item is duplicated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20126) Add support for Spark2 upgrade from HDP-2.5
[ https://issues.apache.org/jira/browse/AMBARI-20126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-20126: - Labels: express_upgrade rolling_upgrade (was: ) > Add support for Spark2 upgrade from HDP-2.5 > --- > > Key: AMBARI-20126 > URL: https://issues.apache.org/jira/browse/AMBARI-20126 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Blocker > Labels: express_upgrade, rolling_upgrade > Fix For: trunk, 2.5.0 > > > Support of Spark2 service upgrade (both EU and EU) from HDP-2.5.x to 2.6 need > to be added -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20126) Add support for Spark2 upgrade from HDP-2.5
[ https://issues.apache.org/jira/browse/AMBARI-20126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-20126: - Component/s: ambari-server > Add support for Spark2 upgrade from HDP-2.5 > --- > > Key: AMBARI-20126 > URL: https://issues.apache.org/jira/browse/AMBARI-20126 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Blocker > Fix For: trunk, 2.5.0 > > > Support of Spark2 service upgrade (both EU and EU) from HDP-2.5.x to 2.6 need > to be added -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20126) Add support for Spark2 upgrade from HDP-2.5
[ https://issues.apache.org/jira/browse/AMBARI-20126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-20126: - Fix Version/s: 2.5.0 trunk > Add support for Spark2 upgrade from HDP-2.5 > --- > > Key: AMBARI-20126 > URL: https://issues.apache.org/jira/browse/AMBARI-20126 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Blocker > Fix For: trunk, 2.5.0 > > > Support of Spark2 service upgrade (both EU and EU) from HDP-2.5.x to 2.6 need > to be added -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20126) Add support for Spark2 upgrade from HDP-2.5
[ https://issues.apache.org/jira/browse/AMBARI-20126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko reassigned AMBARI-20126: Assignee: Dmytro Grinenko > Add support for Spark2 upgrade from HDP-2.5 > --- > > Key: AMBARI-20126 > URL: https://issues.apache.org/jira/browse/AMBARI-20126 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.5.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Blocker > > Support of Spark2 service upgrade (both EU and EU) from HDP-2.5.x to 2.6 need > to be added -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20121) Hue Migration Tool: param values getting cached
[
https://issues.apache.org/jira/browse/AMBARI-20121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879731#comment-15879731
]
Hadoop QA commented on AMBARI-20121:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12854072/AMBARI-20121.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
contrib/views/hueambarimigration.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10696//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10696//console
This message is automatically generated.
> Hue Migration Tool: param values getting cached
> ---
>
> Key: AMBARI-20121
> URL: https://issues.apache.org/jira/browse/AMBARI-20121
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
> Fix For: trunk
>
> Attachments: AMBARI-20121.patch
>
>
> When navigating away from a route the values are getting cached on returning
> to the route which is causing unexpected migrations
> hiveView15 is an instance of hive-view version1.5
> hiveView20 is an instance of hive-view version2.0
> 1. Migrate the Hive-history queries (user admin,instance hiveView15,startdate
> :2017-02-21,enddate:2017-02-22)
> 2. Migrate the Hive-saved queries (user admin,instance hiveView15,startdate
> :2017-02-21,enddate:2017-02-22)
> 3. Migrate the Hive-history queries (user admin,instance hiveView20,startdate
> :2017-02-21,enddate:2017-02-22) **different instanceName
> But The UI shows migration to "hiveView20" happened twice. It uses the
> previously cached value in 'admin' for the variable 'username' for migrating
> artifacts.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20126) Add support for Spark2 upgrade from HDP-2.5
[ https://issues.apache.org/jira/browse/AMBARI-20126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-20126: - Description: Support of Spark2 service upgrade (both EU and EU) from HDP-2.5.x to 2.6 need to be added > Add support for Spark2 upgrade from HDP-2.5 > --- > > Key: AMBARI-20126 > URL: https://issues.apache.org/jira/browse/AMBARI-20126 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.5.0 >Reporter: Dmytro Grinenko >Priority: Blocker > > Support of Spark2 service upgrade (both EU and EU) from HDP-2.5.x to 2.6 need > to be added -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20126) Add support for Spark2 upgrade from HDP-2.5
[ https://issues.apache.org/jira/browse/AMBARI-20126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-20126: - Affects Version/s: 2.5.0 trunk > Add support for Spark2 upgrade from HDP-2.5 > --- > > Key: AMBARI-20126 > URL: https://issues.apache.org/jira/browse/AMBARI-20126 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.5.0 >Reporter: Dmytro Grinenko >Priority: Blocker > > Support of Spark2 service upgrade (both EU and EU) from HDP-2.5.x to 2.6 need > to be added -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20126) Add support for Spark2 upgrade from HDP-2.5
Dmytro Grinenko created AMBARI-20126: Summary: Add support for Spark2 upgrade from HDP-2.5 Key: AMBARI-20126 URL: https://issues.apache.org/jira/browse/AMBARI-20126 Project: Ambari Issue Type: Bug Reporter: Dmytro Grinenko Priority: Blocker -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-15754) configs.sh expands ***** in config values to a local file list, causing broken config files
[
https://issues.apache.org/jira/browse/AMBARI-15754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879719#comment-15879719
]
Hudson commented on AMBARI-15754:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6818 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6818/])
AMBARI-15754. configs.sh expands * in config values to a local file
(afernandez:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e9c943905721ef431dc09b45abaf4a05312d4fe5])
* (edit) ambari-server/src/main/resources/scripts/configs.sh
> configs.sh expands * in config values to a local file list, causing
> broken config files
> ---
>
> Key: AMBARI-15754
> URL: https://issues.apache.org/jira/browse/AMBARI-15754
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.0.0, 2.0.1, 2.1.0, 2.3.0, 2.0.2, 2.1.1, 2.1.2, trunk,
> 2.0.3, 2.2.0, 2.4.0, 2.2.1, 2.2.2, 2.4.1
>Reporter: Asger Askov Blekinge
>Assignee: Asger Askov Blekinge
> Labels: easyfix, patch
> Fix For: trunk
>
> Attachments: AMBARI-15754.v2.patch
>
>
> When you try to get the value of, say, pig-log4j like this, it outputs
> correctly
> {code}
> curl -k -s -u $AMBARI_USER:$AMBARI_PASSWORD
> "$AMBARI_HOST:$AMBARI_PORT/api/v1/clusters/$CLUSTER_NAME/configurations?type=pig-log4j=version1"
> {code}
> If you use configs.sh to do the same
> {code}
> configs.sh -u $AMBARI_USER -p $AMBARI_PASSWORD -port $AMBARI_PORT get
> $AMBARI_HOST $CLUSTER_NAME pig-log4j
> {code}
> it will have replaced the * with the file list in the working directory
> So,
> {code}
> "content" : "\n#\n#\n# Licensed to the Apache Software Foundation (ASF)
> under one\n# or more contributor license agreements. See the NOTICE file\n#
> distributed with this work for additional information\n# regarding copyright
> ownership. The ASF licenses this file\n# to you under the Apache License,
> Version 2.0 (the\n# \"License\"); you may not use this file except in
> compliance\n# with the License. You may obtain a copy of the License
> at\n#\n# http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required
> by applicable law or agreed to in writing,\n# software distributed under the
> License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR
> CONDITIONS OF ANY\n# KIND, either express or implied. See the License for
> the\n# specific language governing permissions and limitations\n# under the
> License.\n#\n#\n#\n\n# * Set root logger level to DEBUG and its only
> appender to A.\nlog4j.logger.org.apache.pig=info, A\n\n# * A is set to be
> a ConsoleAppender.\nlog4j.appender.A=org.apache.log4j.ConsoleAppender\n#
> * A uses
> PatternLayout.\nlog4j.appender.A.layout=org.apache.log4j.PatternLayout\nlog4j.appender.A.layout.ConversionPattern=%-4r
> [%t] %-5p %c %x - %m%n"
> {code}
> will be output as
> {code}
> "content" : "\n#\n#\n# Licensed to the Apache Software Foundation (ASF) under
> one\n# or more contributor license agreements. See the NOTICE file\n#
> distributed with this work for additional information\n# regarding copyright
> ownership. The ASF licenses this file\n# to you under the Apache License,
> Version 2.0 (the\n# \"License\"); you may not use this file except in
> compliance\n# with the License. You may obtain a copy of the License at\n#\n#
> http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required by
> applicable law or agreed to in writing,\n# software distributed under the
> License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR
> CONDITIONS OF ANY\n# KIND, either express or implied. See the License for
> the\n# specific language governing permissions and limitations\n# under the
> License.\n#\n#\n#\n\n# bigr configs.sh gpfs mmls ssh symphony Set root logger
> level to DEBUG and its only appender to A.\nlog4j.logger.org.apache.pig=info,
> A\n\n# bigr configs.sh gpfs mmls ssh symphony A is set to be a
> ConsoleAppender.\nlog4j.appender.A=org.apache.log4j.ConsoleAppender\n# bigr
> configs.sh gpfs mmls ssh symphony A uses
> PatternLayout.\nlog4j.appender.A.layout=org.apache.log4j.PatternLayout\nlog4j.appender.A.layout.ConversionPattern=%-4r
> [%t] %-5p %c %x - %m%n"
> {code}
> As you can see, there are no * string in the output any longer, but
> instead it has been replaced with "bigr configs.sh gpfs mmls ssh symphony"
> which happened to be the local files in my working dir.
> It all comes from this line in configs.sh, line 241-247
> {code}
> if [ "$propertiesStarted" -gt "0" ]; then
> if [ -z $FILENAME ]; then
> echo $line
> else
> echo $line >> $FILENAME
> fi
> fi
> {code}
> where the echo do not quote the $line to output
--
[jira] [Commented] (AMBARI-20125) DataNode Storage alert is duplicated
[
https://issues.apache.org/jira/browse/AMBARI-20125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879688#comment-15879688
]
Hadoop QA commented on AMBARI-20125:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12854107/AMBARI-20125.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10695//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10695//console
This message is automatically generated.
> DataNode Storage alert is duplicated
>
>
> Key: AMBARI-20125
> URL: https://issues.apache.org/jira/browse/AMBARI-20125
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20125.patch
>
>
> In the HDFS alert popup, "DataNode Storage" item is duplicated.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (AMBARI-15754) configs.sh expands ***** in config values to a local file list, causing broken config files
[
https://issues.apache.org/jira/browse/AMBARI-15754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez resolved AMBARI-15754.
--
Resolution: Fixed
Pushed to trunk, commit e9c943905721ef431dc09b45abaf4a05312d4fe5
> configs.sh expands * in config values to a local file list, causing
> broken config files
> ---
>
> Key: AMBARI-15754
> URL: https://issues.apache.org/jira/browse/AMBARI-15754
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.0.0, 2.0.1, 2.1.0, 2.3.0, 2.0.2, 2.1.1, 2.1.2, trunk,
> 2.0.3, 2.2.0, 2.4.0, 2.2.1, 2.2.2, 2.4.1
>Reporter: Asger Askov Blekinge
>Assignee: Asger Askov Blekinge
> Labels: easyfix, patch
> Fix For: trunk
>
> Attachments: AMBARI-15754.v2.patch
>
>
> When you try to get the value of, say, pig-log4j like this, it outputs
> correctly
> {code}
> curl -k -s -u $AMBARI_USER:$AMBARI_PASSWORD
> "$AMBARI_HOST:$AMBARI_PORT/api/v1/clusters/$CLUSTER_NAME/configurations?type=pig-log4j=version1"
> {code}
> If you use configs.sh to do the same
> {code}
> configs.sh -u $AMBARI_USER -p $AMBARI_PASSWORD -port $AMBARI_PORT get
> $AMBARI_HOST $CLUSTER_NAME pig-log4j
> {code}
> it will have replaced the * with the file list in the working directory
> So,
> {code}
> "content" : "\n#\n#\n# Licensed to the Apache Software Foundation (ASF)
> under one\n# or more contributor license agreements. See the NOTICE file\n#
> distributed with this work for additional information\n# regarding copyright
> ownership. The ASF licenses this file\n# to you under the Apache License,
> Version 2.0 (the\n# \"License\"); you may not use this file except in
> compliance\n# with the License. You may obtain a copy of the License
> at\n#\n# http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required
> by applicable law or agreed to in writing,\n# software distributed under the
> License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR
> CONDITIONS OF ANY\n# KIND, either express or implied. See the License for
> the\n# specific language governing permissions and limitations\n# under the
> License.\n#\n#\n#\n\n# * Set root logger level to DEBUG and its only
> appender to A.\nlog4j.logger.org.apache.pig=info, A\n\n# * A is set to be
> a ConsoleAppender.\nlog4j.appender.A=org.apache.log4j.ConsoleAppender\n#
> * A uses
> PatternLayout.\nlog4j.appender.A.layout=org.apache.log4j.PatternLayout\nlog4j.appender.A.layout.ConversionPattern=%-4r
> [%t] %-5p %c %x - %m%n"
> {code}
> will be output as
> {code}
> "content" : "\n#\n#\n# Licensed to the Apache Software Foundation (ASF) under
> one\n# or more contributor license agreements. See the NOTICE file\n#
> distributed with this work for additional information\n# regarding copyright
> ownership. The ASF licenses this file\n# to you under the Apache License,
> Version 2.0 (the\n# \"License\"); you may not use this file except in
> compliance\n# with the License. You may obtain a copy of the License at\n#\n#
> http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required by
> applicable law or agreed to in writing,\n# software distributed under the
> License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR
> CONDITIONS OF ANY\n# KIND, either express or implied. See the License for
> the\n# specific language governing permissions and limitations\n# under the
> License.\n#\n#\n#\n\n# bigr configs.sh gpfs mmls ssh symphony Set root logger
> level to DEBUG and its only appender to A.\nlog4j.logger.org.apache.pig=info,
> A\n\n# bigr configs.sh gpfs mmls ssh symphony A is set to be a
> ConsoleAppender.\nlog4j.appender.A=org.apache.log4j.ConsoleAppender\n# bigr
> configs.sh gpfs mmls ssh symphony A uses
> PatternLayout.\nlog4j.appender.A.layout=org.apache.log4j.PatternLayout\nlog4j.appender.A.layout.ConversionPattern=%-4r
> [%t] %-5p %c %x - %m%n"
> {code}
> As you can see, there are no * string in the output any longer, but
> instead it has been replaced with "bigr configs.sh gpfs mmls ssh symphony"
> which happened to be the local files in my working dir.
> It all comes from this line in configs.sh, line 241-247
> {code}
> if [ "$propertiesStarted" -gt "0" ]; then
> if [ -z $FILENAME ]; then
> echo $line
> else
> echo $line >> $FILENAME
> fi
> fi
> {code}
> where the echo do not quote the $line to output
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20125) DataNode Storage alert is duplicated
[ https://issues.apache.org/jira/browse/AMBARI-20125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20125: -- Attachment: AMBARI-20125.patch > DataNode Storage alert is duplicated > > > Key: AMBARI-20125 > URL: https://issues.apache.org/jira/browse/AMBARI-20125 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20125.patch > > > In the HDFS alert popup, "DataNode Storage" item is duplicated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20125) DataNode Storage alert is duplicated
[ https://issues.apache.org/jira/browse/AMBARI-20125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20125: -- Status: Patch Available (was: Open) > DataNode Storage alert is duplicated > > > Key: AMBARI-20125 > URL: https://issues.apache.org/jira/browse/AMBARI-20125 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20125.patch > > > In the HDFS alert popup, "DataNode Storage" item is duplicated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20125) DataNode Storage alert is duplicated
[
https://issues.apache.org/jira/browse/AMBARI-20125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879624#comment-15879624
]
Richard Zang commented on AMBARI-20125:
---
When we try to sort alert collection in the order of "critical, warning, ok,
unknown, other", we made modification to original looping collection
"serviceDefinitions" during the forEach loop. Also, alert definition with
multiple alert instances distributed in different categories got pushed
multiple times during the sort. This led to duplicated entries after
processing.
{code}
var property = context.get('componentName') ? 'componentName' :
'serviceName';
var serviceDefinitions =
this.get('controller.content').filterProperty(property, context.get(property));
// definitions should be sorted in order: critical, warning, ok,
unknown, other
var definitionTypes = {
"isCritical": [],
"isWarning": [],
"isOK": [],
"isUnknown": []
};
serviceDefinitions.forEach(function (definition) {
Object.keys(definitionTypes).forEach(function (type) {
if (definition.get(type)) {
definition.set('isCollapsed', true);
definitionTypes[type].push(definition);
serviceDefinitions = serviceDefinitions.without(definition);
}
});
});
serviceDefinitions =
definitionTypes.isCritical.concat(definitionTypes.isWarning,
definitionTypes.isOK, definitionTypes.isUnknown, serviceDefinitions);
return serviceDefinitions;
{code}
> DataNode Storage alert is duplicated
>
>
> Key: AMBARI-20125
> URL: https://issues.apache.org/jira/browse/AMBARI-20125
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
>Priority: Critical
> Fix For: 2.5.0
>
>
> In the HDFS alert popup, "DataNode Storage" item is duplicated.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20125) DataNode Storage alert is duplicated
Richard Zang created AMBARI-20125: - Summary: DataNode Storage alert is duplicated Key: AMBARI-20125 URL: https://issues.apache.org/jira/browse/AMBARI-20125 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Richard Zang Assignee: Richard Zang Priority: Critical Fix For: 2.5.0 In the HDFS alert popup, "DataNode Storage" item is duplicated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20105) When spark thrift server and hive server2 located on different hosts, with kerberos spark thrift server keeps failing
[ https://issues.apache.org/jira/browse/AMBARI-20105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shi Wang reassigned AMBARI-20105: - Assignee: Shi Wang > When spark thrift server and hive server2 located on different hosts, with > kerberos spark thrift server keeps failing > - > > Key: AMBARI-20105 > URL: https://issues.apache.org/jira/browse/AMBARI-20105 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.5.0 >Reporter: Shi Wang >Assignee: Shi Wang > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20106) Additional config changes for HSI - HDP stack
[ https://issues.apache.org/jira/browse/AMBARI-20106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879580#comment-15879580 ] Hudson commented on AMBARI-20106: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6817 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6817/]) AMBARI-20106. Additional config changes for HSI - HDP stack (Siddharth (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f7acf8edd4566ddf9f34419a6b88cf06d9136668]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/hive-interactive-env.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/hive-interactive-site.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/tez-interactive-site.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/hive-interactive-env.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/hive-interactive-site.xml > Additional config changes for HSI - HDP stack > - > > Key: AMBARI-20106 > URL: https://issues.apache.org/jira/browse/AMBARI-20106 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > Attachments: AMBARI-20106.01.patch > > > Timeout changes > GC parameter changes -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-15754) configs.sh expands ***** in config values to a local file list, causing broken config files
[
https://issues.apache.org/jira/browse/AMBARI-15754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879521#comment-15879521
]
Siddharth Wagle commented on AMBARI-15754:
--
[~afernandez] +1 LGTM
> configs.sh expands * in config values to a local file list, causing
> broken config files
> ---
>
> Key: AMBARI-15754
> URL: https://issues.apache.org/jira/browse/AMBARI-15754
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.0.0, 2.0.1, 2.1.0, 2.3.0, 2.0.2, 2.1.1, 2.1.2, trunk,
> 2.0.3, 2.2.0, 2.4.0, 2.2.1, 2.2.2, 2.4.1
>Reporter: Asger Askov Blekinge
>Assignee: Asger Askov Blekinge
> Labels: easyfix, patch
> Fix For: trunk
>
> Attachments: AMBARI-15754.v2.patch
>
>
> When you try to get the value of, say, pig-log4j like this, it outputs
> correctly
> {code}
> curl -k -s -u $AMBARI_USER:$AMBARI_PASSWORD
> "$AMBARI_HOST:$AMBARI_PORT/api/v1/clusters/$CLUSTER_NAME/configurations?type=pig-log4j=version1"
> {code}
> If you use configs.sh to do the same
> {code}
> configs.sh -u $AMBARI_USER -p $AMBARI_PASSWORD -port $AMBARI_PORT get
> $AMBARI_HOST $CLUSTER_NAME pig-log4j
> {code}
> it will have replaced the * with the file list in the working directory
> So,
> {code}
> "content" : "\n#\n#\n# Licensed to the Apache Software Foundation (ASF)
> under one\n# or more contributor license agreements. See the NOTICE file\n#
> distributed with this work for additional information\n# regarding copyright
> ownership. The ASF licenses this file\n# to you under the Apache License,
> Version 2.0 (the\n# \"License\"); you may not use this file except in
> compliance\n# with the License. You may obtain a copy of the License
> at\n#\n# http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required
> by applicable law or agreed to in writing,\n# software distributed under the
> License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR
> CONDITIONS OF ANY\n# KIND, either express or implied. See the License for
> the\n# specific language governing permissions and limitations\n# under the
> License.\n#\n#\n#\n\n# * Set root logger level to DEBUG and its only
> appender to A.\nlog4j.logger.org.apache.pig=info, A\n\n# * A is set to be
> a ConsoleAppender.\nlog4j.appender.A=org.apache.log4j.ConsoleAppender\n#
> * A uses
> PatternLayout.\nlog4j.appender.A.layout=org.apache.log4j.PatternLayout\nlog4j.appender.A.layout.ConversionPattern=%-4r
> [%t] %-5p %c %x - %m%n"
> {code}
> will be output as
> {code}
> "content" : "\n#\n#\n# Licensed to the Apache Software Foundation (ASF) under
> one\n# or more contributor license agreements. See the NOTICE file\n#
> distributed with this work for additional information\n# regarding copyright
> ownership. The ASF licenses this file\n# to you under the Apache License,
> Version 2.0 (the\n# \"License\"); you may not use this file except in
> compliance\n# with the License. You may obtain a copy of the License at\n#\n#
> http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required by
> applicable law or agreed to in writing,\n# software distributed under the
> License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR
> CONDITIONS OF ANY\n# KIND, either express or implied. See the License for
> the\n# specific language governing permissions and limitations\n# under the
> License.\n#\n#\n#\n\n# bigr configs.sh gpfs mmls ssh symphony Set root logger
> level to DEBUG and its only appender to A.\nlog4j.logger.org.apache.pig=info,
> A\n\n# bigr configs.sh gpfs mmls ssh symphony A is set to be a
> ConsoleAppender.\nlog4j.appender.A=org.apache.log4j.ConsoleAppender\n# bigr
> configs.sh gpfs mmls ssh symphony A uses
> PatternLayout.\nlog4j.appender.A.layout=org.apache.log4j.PatternLayout\nlog4j.appender.A.layout.ConversionPattern=%-4r
> [%t] %-5p %c %x - %m%n"
> {code}
> As you can see, there are no * string in the output any longer, but
> instead it has been replaced with "bigr configs.sh gpfs mmls ssh symphony"
> which happened to be the local files in my working dir.
> It all comes from this line in configs.sh, line 241-247
> {code}
> if [ "$propertiesStarted" -gt "0" ]; then
> if [ -z $FILENAME ]; then
> echo $line
> else
> echo $line >> $FILENAME
> fi
> fi
> {code}
> where the echo do not quote the $line to output
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (AMBARI-15754) configs.sh expands ***** in config values to a local file list, causing broken config files
[
https://issues.apache.org/jira/browse/AMBARI-15754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879514#comment-15879514
]
Alejandro Fernandez edited comment on AMBARI-15754 at 2/23/17 12:04 AM:
[~blekinge], I'm redacting your patch in the comments and creating a patch that
I tested with a subset of your changes.
+1 for [^AMBARI-15754.v2.patch]
Unit Tests passed,
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 46:35 min
[INFO] Finished at: 2017-02-22T15:57:39-08:00
[INFO] Final Memory: 211M/5337M
[INFO]
was (Author: afernandez):
[~blekinge], I'm redacting your patch in the comments and creating a patch that
I tested with a subset of your changes.
+1 for [^AMBARI-15754.v2.patch]
> configs.sh expands * in config values to a local file list, causing
> broken config files
> ---
>
> Key: AMBARI-15754
> URL: https://issues.apache.org/jira/browse/AMBARI-15754
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.0.0, 2.0.1, 2.1.0, 2.3.0, 2.0.2, 2.1.1, 2.1.2, trunk,
> 2.0.3, 2.2.0, 2.4.0, 2.2.1, 2.2.2, 2.4.1
>Reporter: Asger Askov Blekinge
>Assignee: Asger Askov Blekinge
> Labels: easyfix, patch
> Fix For: trunk
>
> Attachments: AMBARI-15754.v2.patch
>
>
> When you try to get the value of, say, pig-log4j like this, it outputs
> correctly
> {code}
> curl -k -s -u $AMBARI_USER:$AMBARI_PASSWORD
> "$AMBARI_HOST:$AMBARI_PORT/api/v1/clusters/$CLUSTER_NAME/configurations?type=pig-log4j=version1"
> {code}
> If you use configs.sh to do the same
> {code}
> configs.sh -u $AMBARI_USER -p $AMBARI_PASSWORD -port $AMBARI_PORT get
> $AMBARI_HOST $CLUSTER_NAME pig-log4j
> {code}
> it will have replaced the * with the file list in the working directory
> So,
> {code}
> "content" : "\n#\n#\n# Licensed to the Apache Software Foundation (ASF)
> under one\n# or more contributor license agreements. See the NOTICE file\n#
> distributed with this work for additional information\n# regarding copyright
> ownership. The ASF licenses this file\n# to you under the Apache License,
> Version 2.0 (the\n# \"License\"); you may not use this file except in
> compliance\n# with the License. You may obtain a copy of the License
> at\n#\n# http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required
> by applicable law or agreed to in writing,\n# software distributed under the
> License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR
> CONDITIONS OF ANY\n# KIND, either express or implied. See the License for
> the\n# specific language governing permissions and limitations\n# under the
> License.\n#\n#\n#\n\n# * Set root logger level to DEBUG and its only
> appender to A.\nlog4j.logger.org.apache.pig=info, A\n\n# * A is set to be
> a ConsoleAppender.\nlog4j.appender.A=org.apache.log4j.ConsoleAppender\n#
> * A uses
> PatternLayout.\nlog4j.appender.A.layout=org.apache.log4j.PatternLayout\nlog4j.appender.A.layout.ConversionPattern=%-4r
> [%t] %-5p %c %x - %m%n"
> {code}
> will be output as
> {code}
> "content" : "\n#\n#\n# Licensed to the Apache Software Foundation (ASF) under
> one\n# or more contributor license agreements. See the NOTICE file\n#
> distributed with this work for additional information\n# regarding copyright
> ownership. The ASF licenses this file\n# to you under the Apache License,
> Version 2.0 (the\n# \"License\"); you may not use this file except in
> compliance\n# with the License. You may obtain a copy of the License at\n#\n#
> http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required by
> applicable law or agreed to in writing,\n# software distributed under the
> License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR
> CONDITIONS OF ANY\n# KIND, either express or implied. See the License for
> the\n# specific language governing permissions and limitations\n# under the
> License.\n#\n#\n#\n\n# bigr configs.sh gpfs mmls ssh symphony Set root logger
> level to DEBUG and its only appender to A.\nlog4j.logger.org.apache.pig=info,
> A\n\n# bigr configs.sh gpfs mmls ssh symphony A is set to be a
> ConsoleAppender.\nlog4j.appender.A=org.apache.log4j.ConsoleAppender\n# bigr
> configs.sh gpfs mmls ssh symphony A uses
> PatternLayout.\nlog4j.appender.A.layout=org.apache.log4j.PatternLayout\nlog4j.appender.A.layout.ConversionPattern=%-4r
> [%t] %-5p %c %x - %m%n"
> {code}
> As you can see, there are no * string in the output any longer, but
> instead it has
[jira] [Updated] (AMBARI-15754) configs.sh expands ***** in config values to a local file list, causing broken config files
[
https://issues.apache.org/jira/browse/AMBARI-15754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-15754:
-
Attachment: AMBARI-15754.v2.patch
[~blekinge], I'm redacting your patch in the comments and creating a patch that
I tested with a subset of your changes.
+1 for [^AMBARI-15754.v2.patch]
> configs.sh expands * in config values to a local file list, causing
> broken config files
> ---
>
> Key: AMBARI-15754
> URL: https://issues.apache.org/jira/browse/AMBARI-15754
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.0.0, 2.0.1, 2.1.0, 2.3.0, 2.0.2, 2.1.1, 2.1.2, trunk,
> 2.0.3, 2.2.0, 2.4.0, 2.2.1, 2.2.2, 2.4.1
>Reporter: Asger Askov Blekinge
>Assignee: Asger Askov Blekinge
> Labels: easyfix, patch
> Fix For: trunk
>
> Attachments: AMBARI-15754.v2.patch
>
>
> When you try to get the value of, say, pig-log4j like this, it outputs
> correctly
> {code}
> curl -k -s -u $AMBARI_USER:$AMBARI_PASSWORD
> "$AMBARI_HOST:$AMBARI_PORT/api/v1/clusters/$CLUSTER_NAME/configurations?type=pig-log4j=version1"
> {code}
> If you use configs.sh to do the same
> {code}
> configs.sh -u $AMBARI_USER -p $AMBARI_PASSWORD -port $AMBARI_PORT get
> $AMBARI_HOST $CLUSTER_NAME pig-log4j
> {code}
> it will have replaced the * with the file list in the working directory
> So,
> {code}
> "content" : "\n#\n#\n# Licensed to the Apache Software Foundation (ASF)
> under one\n# or more contributor license agreements. See the NOTICE file\n#
> distributed with this work for additional information\n# regarding copyright
> ownership. The ASF licenses this file\n# to you under the Apache License,
> Version 2.0 (the\n# \"License\"); you may not use this file except in
> compliance\n# with the License. You may obtain a copy of the License
> at\n#\n# http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required
> by applicable law or agreed to in writing,\n# software distributed under the
> License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR
> CONDITIONS OF ANY\n# KIND, either express or implied. See the License for
> the\n# specific language governing permissions and limitations\n# under the
> License.\n#\n#\n#\n\n# * Set root logger level to DEBUG and its only
> appender to A.\nlog4j.logger.org.apache.pig=info, A\n\n# * A is set to be
> a ConsoleAppender.\nlog4j.appender.A=org.apache.log4j.ConsoleAppender\n#
> * A uses
> PatternLayout.\nlog4j.appender.A.layout=org.apache.log4j.PatternLayout\nlog4j.appender.A.layout.ConversionPattern=%-4r
> [%t] %-5p %c %x - %m%n"
> {code}
> will be output as
> {code}
> "content" : "\n#\n#\n# Licensed to the Apache Software Foundation (ASF) under
> one\n# or more contributor license agreements. See the NOTICE file\n#
> distributed with this work for additional information\n# regarding copyright
> ownership. The ASF licenses this file\n# to you under the Apache License,
> Version 2.0 (the\n# \"License\"); you may not use this file except in
> compliance\n# with the License. You may obtain a copy of the License at\n#\n#
> http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required by
> applicable law or agreed to in writing,\n# software distributed under the
> License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR
> CONDITIONS OF ANY\n# KIND, either express or implied. See the License for
> the\n# specific language governing permissions and limitations\n# under the
> License.\n#\n#\n#\n\n# bigr configs.sh gpfs mmls ssh symphony Set root logger
> level to DEBUG and its only appender to A.\nlog4j.logger.org.apache.pig=info,
> A\n\n# bigr configs.sh gpfs mmls ssh symphony A is set to be a
> ConsoleAppender.\nlog4j.appender.A=org.apache.log4j.ConsoleAppender\n# bigr
> configs.sh gpfs mmls ssh symphony A uses
> PatternLayout.\nlog4j.appender.A.layout=org.apache.log4j.PatternLayout\nlog4j.appender.A.layout.ConversionPattern=%-4r
> [%t] %-5p %c %x - %m%n"
> {code}
> As you can see, there are no * string in the output any longer, but
> instead it has been replaced with "bigr configs.sh gpfs mmls ssh symphony"
> which happened to be the local files in my working dir.
> It all comes from this line in configs.sh, line 241-247
> {code}
> if [ "$propertiesStarted" -gt "0" ]; then
> if [ -z $FILENAME ]; then
> echo $line
> else
> echo $line >> $FILENAME
> fi
> fi
> {code}
> where the echo do not quote the $line to output
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-15754) configs.sh expands ***** in config values to a local file list, causing broken config files
[
https://issues.apache.org/jira/browse/AMBARI-15754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-15754:
-
Attachment: (was: AMBARI-15754.v2.patch)
> configs.sh expands * in config values to a local file list, causing
> broken config files
> ---
>
> Key: AMBARI-15754
> URL: https://issues.apache.org/jira/browse/AMBARI-15754
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.0.0, 2.0.1, 2.1.0, 2.3.0, 2.0.2, 2.1.1, 2.1.2, trunk,
> 2.0.3, 2.2.0, 2.4.0, 2.2.1, 2.2.2, 2.4.1
>Reporter: Asger Askov Blekinge
>Assignee: Asger Askov Blekinge
> Labels: easyfix, patch
> Fix For: trunk
>
>
> When you try to get the value of, say, pig-log4j like this, it outputs
> correctly
> {code}
> curl -k -s -u $AMBARI_USER:$AMBARI_PASSWORD
> "$AMBARI_HOST:$AMBARI_PORT/api/v1/clusters/$CLUSTER_NAME/configurations?type=pig-log4j=version1"
> {code}
> If you use configs.sh to do the same
> {code}
> configs.sh -u $AMBARI_USER -p $AMBARI_PASSWORD -port $AMBARI_PORT get
> $AMBARI_HOST $CLUSTER_NAME pig-log4j
> {code}
> it will have replaced the * with the file list in the working directory
> So,
> {code}
> "content" : "\n#\n#\n# Licensed to the Apache Software Foundation (ASF)
> under one\n# or more contributor license agreements. See the NOTICE file\n#
> distributed with this work for additional information\n# regarding copyright
> ownership. The ASF licenses this file\n# to you under the Apache License,
> Version 2.0 (the\n# \"License\"); you may not use this file except in
> compliance\n# with the License. You may obtain a copy of the License
> at\n#\n# http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required
> by applicable law or agreed to in writing,\n# software distributed under the
> License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR
> CONDITIONS OF ANY\n# KIND, either express or implied. See the License for
> the\n# specific language governing permissions and limitations\n# under the
> License.\n#\n#\n#\n\n# * Set root logger level to DEBUG and its only
> appender to A.\nlog4j.logger.org.apache.pig=info, A\n\n# * A is set to be
> a ConsoleAppender.\nlog4j.appender.A=org.apache.log4j.ConsoleAppender\n#
> * A uses
> PatternLayout.\nlog4j.appender.A.layout=org.apache.log4j.PatternLayout\nlog4j.appender.A.layout.ConversionPattern=%-4r
> [%t] %-5p %c %x - %m%n"
> {code}
> will be output as
> {code}
> "content" : "\n#\n#\n# Licensed to the Apache Software Foundation (ASF) under
> one\n# or more contributor license agreements. See the NOTICE file\n#
> distributed with this work for additional information\n# regarding copyright
> ownership. The ASF licenses this file\n# to you under the Apache License,
> Version 2.0 (the\n# \"License\"); you may not use this file except in
> compliance\n# with the License. You may obtain a copy of the License at\n#\n#
> http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required by
> applicable law or agreed to in writing,\n# software distributed under the
> License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR
> CONDITIONS OF ANY\n# KIND, either express or implied. See the License for
> the\n# specific language governing permissions and limitations\n# under the
> License.\n#\n#\n#\n\n# bigr configs.sh gpfs mmls ssh symphony Set root logger
> level to DEBUG and its only appender to A.\nlog4j.logger.org.apache.pig=info,
> A\n\n# bigr configs.sh gpfs mmls ssh symphony A is set to be a
> ConsoleAppender.\nlog4j.appender.A=org.apache.log4j.ConsoleAppender\n# bigr
> configs.sh gpfs mmls ssh symphony A uses
> PatternLayout.\nlog4j.appender.A.layout=org.apache.log4j.PatternLayout\nlog4j.appender.A.layout.ConversionPattern=%-4r
> [%t] %-5p %c %x - %m%n"
> {code}
> As you can see, there are no * string in the output any longer, but
> instead it has been replaced with "bigr configs.sh gpfs mmls ssh symphony"
> which happened to be the local files in my working dir.
> It all comes from this line in configs.sh, line 241-247
> {code}
> if [ "$propertiesStarted" -gt "0" ]; then
> if [ -z $FILENAME ]; then
> echo $line
> else
> echo $line >> $FILENAME
> fi
> fi
> {code}
> where the echo do not quote the $line to output
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-15754) configs.sh expands ***** in config values to a local file list, causing broken config files
[
https://issues.apache.org/jira/browse/AMBARI-15754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-15754:
-
Status: Open (was: Patch Available)
> configs.sh expands * in config values to a local file list, causing
> broken config files
> ---
>
> Key: AMBARI-15754
> URL: https://issues.apache.org/jira/browse/AMBARI-15754
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.0.0, 2.0.1, 2.1.0, 2.3.0, 2.0.2, 2.1.1, 2.1.2, trunk,
> 2.0.3, 2.2.0, 2.4.0, 2.2.1, 2.2.2, 2.4.1
>Reporter: Asger Askov Blekinge
>Assignee: Asger Askov Blekinge
> Labels: easyfix, patch
> Fix For: trunk
>
>
> When you try to get the value of, say, pig-log4j like this, it outputs
> correctly
> {code}
> curl -k -s -u $AMBARI_USER:$AMBARI_PASSWORD
> "$AMBARI_HOST:$AMBARI_PORT/api/v1/clusters/$CLUSTER_NAME/configurations?type=pig-log4j=version1"
> {code}
> If you use configs.sh to do the same
> {code}
> configs.sh -u $AMBARI_USER -p $AMBARI_PASSWORD -port $AMBARI_PORT get
> $AMBARI_HOST $CLUSTER_NAME pig-log4j
> {code}
> it will have replaced the * with the file list in the working directory
> So,
> {code}
> "content" : "\n#\n#\n# Licensed to the Apache Software Foundation (ASF)
> under one\n# or more contributor license agreements. See the NOTICE file\n#
> distributed with this work for additional information\n# regarding copyright
> ownership. The ASF licenses this file\n# to you under the Apache License,
> Version 2.0 (the\n# \"License\"); you may not use this file except in
> compliance\n# with the License. You may obtain a copy of the License
> at\n#\n# http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required
> by applicable law or agreed to in writing,\n# software distributed under the
> License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR
> CONDITIONS OF ANY\n# KIND, either express or implied. See the License for
> the\n# specific language governing permissions and limitations\n# under the
> License.\n#\n#\n#\n\n# * Set root logger level to DEBUG and its only
> appender to A.\nlog4j.logger.org.apache.pig=info, A\n\n# * A is set to be
> a ConsoleAppender.\nlog4j.appender.A=org.apache.log4j.ConsoleAppender\n#
> * A uses
> PatternLayout.\nlog4j.appender.A.layout=org.apache.log4j.PatternLayout\nlog4j.appender.A.layout.ConversionPattern=%-4r
> [%t] %-5p %c %x - %m%n"
> {code}
> will be output as
> {code}
> "content" : "\n#\n#\n# Licensed to the Apache Software Foundation (ASF) under
> one\n# or more contributor license agreements. See the NOTICE file\n#
> distributed with this work for additional information\n# regarding copyright
> ownership. The ASF licenses this file\n# to you under the Apache License,
> Version 2.0 (the\n# \"License\"); you may not use this file except in
> compliance\n# with the License. You may obtain a copy of the License at\n#\n#
> http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required by
> applicable law or agreed to in writing,\n# software distributed under the
> License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR
> CONDITIONS OF ANY\n# KIND, either express or implied. See the License for
> the\n# specific language governing permissions and limitations\n# under the
> License.\n#\n#\n#\n\n# bigr configs.sh gpfs mmls ssh symphony Set root logger
> level to DEBUG and its only appender to A.\nlog4j.logger.org.apache.pig=info,
> A\n\n# bigr configs.sh gpfs mmls ssh symphony A is set to be a
> ConsoleAppender.\nlog4j.appender.A=org.apache.log4j.ConsoleAppender\n# bigr
> configs.sh gpfs mmls ssh symphony A uses
> PatternLayout.\nlog4j.appender.A.layout=org.apache.log4j.PatternLayout\nlog4j.appender.A.layout.ConversionPattern=%-4r
> [%t] %-5p %c %x - %m%n"
> {code}
> As you can see, there are no * string in the output any longer, but
> instead it has been replaced with "bigr configs.sh gpfs mmls ssh symphony"
> which happened to be the local files in my working dir.
> It all comes from this line in configs.sh, line 241-247
> {code}
> if [ "$propertiesStarted" -gt "0" ]; then
> if [ -z $FILENAME ]; then
> echo $line
> else
> echo $line >> $FILENAME
> fi
> fi
> {code}
> where the echo do not quote the $line to output
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20124) Remove OrderedDict python module code from ranger stack
[ https://issues.apache.org/jira/browse/AMBARI-20124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-20124: -- Summary: Remove OrderedDict python module code from ranger stack (was: Remove python OrderedDict module code from ranger stack) > Remove OrderedDict python module code from ranger stack > > > Key: AMBARI-20124 > URL: https://issues.apache.org/jira/browse/AMBARI-20124 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Critical > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-15754) configs.sh expands ***** in config values to a local file list, causing broken config files
[
https://issues.apache.org/jira/browse/AMBARI-15754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-15754:
-
Fix Version/s: trunk
> configs.sh expands * in config values to a local file list, causing
> broken config files
> ---
>
> Key: AMBARI-15754
> URL: https://issues.apache.org/jira/browse/AMBARI-15754
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.0.0, 2.0.1, 2.1.0, 2.3.0, 2.0.2, 2.1.1, 2.1.2, trunk,
> 2.0.3, 2.2.0, 2.4.0, 2.2.1, 2.2.2, 2.4.1
>Reporter: Asger Askov Blekinge
>Assignee: Asger Askov Blekinge
> Labels: easyfix, patch
> Fix For: trunk
>
> Attachments: AMBARI-15754.v2.patch
>
>
> When you try to get the value of, say, pig-log4j like this, it outputs
> correctly
> {code}
> curl -k -s -u $AMBARI_USER:$AMBARI_PASSWORD
> "$AMBARI_HOST:$AMBARI_PORT/api/v1/clusters/$CLUSTER_NAME/configurations?type=pig-log4j=version1"
> {code}
> If you use configs.sh to do the same
> {code}
> configs.sh -u $AMBARI_USER -p $AMBARI_PASSWORD -port $AMBARI_PORT get
> $AMBARI_HOST $CLUSTER_NAME pig-log4j
> {code}
> it will have replaced the * with the file list in the working directory
> So,
> {code}
> "content" : "\n#\n#\n# Licensed to the Apache Software Foundation (ASF)
> under one\n# or more contributor license agreements. See the NOTICE file\n#
> distributed with this work for additional information\n# regarding copyright
> ownership. The ASF licenses this file\n# to you under the Apache License,
> Version 2.0 (the\n# \"License\"); you may not use this file except in
> compliance\n# with the License. You may obtain a copy of the License
> at\n#\n# http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required
> by applicable law or agreed to in writing,\n# software distributed under the
> License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR
> CONDITIONS OF ANY\n# KIND, either express or implied. See the License for
> the\n# specific language governing permissions and limitations\n# under the
> License.\n#\n#\n#\n\n# * Set root logger level to DEBUG and its only
> appender to A.\nlog4j.logger.org.apache.pig=info, A\n\n# * A is set to be
> a ConsoleAppender.\nlog4j.appender.A=org.apache.log4j.ConsoleAppender\n#
> * A uses
> PatternLayout.\nlog4j.appender.A.layout=org.apache.log4j.PatternLayout\nlog4j.appender.A.layout.ConversionPattern=%-4r
> [%t] %-5p %c %x - %m%n"
> {code}
> will be output as
> {code}
> "content" : "\n#\n#\n# Licensed to the Apache Software Foundation (ASF) under
> one\n# or more contributor license agreements. See the NOTICE file\n#
> distributed with this work for additional information\n# regarding copyright
> ownership. The ASF licenses this file\n# to you under the Apache License,
> Version 2.0 (the\n# \"License\"); you may not use this file except in
> compliance\n# with the License. You may obtain a copy of the License at\n#\n#
> http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required by
> applicable law or agreed to in writing,\n# software distributed under the
> License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR
> CONDITIONS OF ANY\n# KIND, either express or implied. See the License for
> the\n# specific language governing permissions and limitations\n# under the
> License.\n#\n#\n#\n\n# bigr configs.sh gpfs mmls ssh symphony Set root logger
> level to DEBUG and its only appender to A.\nlog4j.logger.org.apache.pig=info,
> A\n\n# bigr configs.sh gpfs mmls ssh symphony A is set to be a
> ConsoleAppender.\nlog4j.appender.A=org.apache.log4j.ConsoleAppender\n# bigr
> configs.sh gpfs mmls ssh symphony A uses
> PatternLayout.\nlog4j.appender.A.layout=org.apache.log4j.PatternLayout\nlog4j.appender.A.layout.ConversionPattern=%-4r
> [%t] %-5p %c %x - %m%n"
> {code}
> As you can see, there are no * string in the output any longer, but
> instead it has been replaced with "bigr configs.sh gpfs mmls ssh symphony"
> which happened to be the local files in my working dir.
> It all comes from this line in configs.sh, line 241-247
> {code}
> if [ "$propertiesStarted" -gt "0" ]; then
> if [ -z $FILENAME ]; then
> echo $line
> else
> echo $line >> $FILENAME
> fi
> fi
> {code}
> where the echo do not quote the $line to output
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20124) Remove python OrderedDict module code from ranger stack
Olivér Szabó created AMBARI-20124: - Summary: Remove python OrderedDict module code from ranger stack Key: AMBARI-20124 URL: https://issues.apache.org/jira/browse/AMBARI-20124 Project: Ambari Issue Type: Bug Affects Versions: 2.5.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Priority: Critical Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20123) Click feedback/disable toggle is missing for transition buttons in Kerberos Wizard - prone to various failures
Denys Buzhor created AMBARI-20123: - Summary: Click feedback/disable toggle is missing for transition buttons in Kerberos Wizard - prone to various failures Key: AMBARI-20123 URL: https://issues.apache.org/jira/browse/AMBARI-20123 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Denys Buzhor Assignee: Denys Buzhor Priority: Critical Fix For: 2.5.0 Following items should be fixed: * After the user clicks on "Next", need to disable the button right away and show the spin animation in the button like we already do for Install Wizard * While a step is still loading, do not allow the user to click Next (the button should be disabled until the step has completed loading) * Download CSV request can take some time, need to show spin animation and prevent additional clicks during data loading -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20122) Stack advisor needs to recommend dependency for slaves and masters
Jaimin Jetly created AMBARI-20122: - Summary: Stack advisor needs to recommend dependency for slaves and masters Key: AMBARI-20122 URL: https://issues.apache.org/jira/browse/AMBARI-20122 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 3.0.0 Reporter: Jaimin Jetly Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-15754) configs.sh expands ***** in config values to a local file list, causing broken config files
[
https://issues.apache.org/jira/browse/AMBARI-15754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez reassigned AMBARI-15754:
Assignee: Asger Askov Blekinge
> configs.sh expands * in config values to a local file list, causing
> broken config files
> ---
>
> Key: AMBARI-15754
> URL: https://issues.apache.org/jira/browse/AMBARI-15754
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.0.0, 2.0.1, 2.1.0, 2.3.0, 2.0.2, 2.1.1, 2.1.2, trunk,
> 2.0.3, 2.2.0, 2.4.0, 2.2.1, 2.2.2, 2.4.1
>Reporter: Asger Askov Blekinge
>Assignee: Asger Askov Blekinge
> Labels: easyfix, patch
> Attachments: AMBARI-15754.v2.patch
>
>
> When you try to get the value of, say, pig-log4j like this, it outputs
> correctly
> {code}
> curl -k -s -u $AMBARI_USER:$AMBARI_PASSWORD
> "$AMBARI_HOST:$AMBARI_PORT/api/v1/clusters/$CLUSTER_NAME/configurations?type=pig-log4j=version1"
> {code}
> If you use configs.sh to do the same
> {code}
> configs.sh -u $AMBARI_USER -p $AMBARI_PASSWORD -port $AMBARI_PORT get
> $AMBARI_HOST $CLUSTER_NAME pig-log4j
> {code}
> it will have replaced the * with the file list in the working directory
> So,
> {code}
> "content" : "\n#\n#\n# Licensed to the Apache Software Foundation (ASF)
> under one\n# or more contributor license agreements. See the NOTICE file\n#
> distributed with this work for additional information\n# regarding copyright
> ownership. The ASF licenses this file\n# to you under the Apache License,
> Version 2.0 (the\n# \"License\"); you may not use this file except in
> compliance\n# with the License. You may obtain a copy of the License
> at\n#\n# http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required
> by applicable law or agreed to in writing,\n# software distributed under the
> License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR
> CONDITIONS OF ANY\n# KIND, either express or implied. See the License for
> the\n# specific language governing permissions and limitations\n# under the
> License.\n#\n#\n#\n\n# * Set root logger level to DEBUG and its only
> appender to A.\nlog4j.logger.org.apache.pig=info, A\n\n# * A is set to be
> a ConsoleAppender.\nlog4j.appender.A=org.apache.log4j.ConsoleAppender\n#
> * A uses
> PatternLayout.\nlog4j.appender.A.layout=org.apache.log4j.PatternLayout\nlog4j.appender.A.layout.ConversionPattern=%-4r
> [%t] %-5p %c %x - %m%n"
> {code}
> will be output as
> {code}
> "content" : "\n#\n#\n# Licensed to the Apache Software Foundation (ASF) under
> one\n# or more contributor license agreements. See the NOTICE file\n#
> distributed with this work for additional information\n# regarding copyright
> ownership. The ASF licenses this file\n# to you under the Apache License,
> Version 2.0 (the\n# \"License\"); you may not use this file except in
> compliance\n# with the License. You may obtain a copy of the License at\n#\n#
> http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required by
> applicable law or agreed to in writing,\n# software distributed under the
> License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR
> CONDITIONS OF ANY\n# KIND, either express or implied. See the License for
> the\n# specific language governing permissions and limitations\n# under the
> License.\n#\n#\n#\n\n# bigr configs.sh gpfs mmls ssh symphony Set root logger
> level to DEBUG and its only appender to A.\nlog4j.logger.org.apache.pig=info,
> A\n\n# bigr configs.sh gpfs mmls ssh symphony A is set to be a
> ConsoleAppender.\nlog4j.appender.A=org.apache.log4j.ConsoleAppender\n# bigr
> configs.sh gpfs mmls ssh symphony A uses
> PatternLayout.\nlog4j.appender.A.layout=org.apache.log4j.PatternLayout\nlog4j.appender.A.layout.ConversionPattern=%-4r
> [%t] %-5p %c %x - %m%n"
> {code}
> As you can see, there are no * string in the output any longer, but
> instead it has been replaced with "bigr configs.sh gpfs mmls ssh symphony"
> which happened to be the local files in my working dir.
> It all comes from this line in configs.sh, line 241-247
> {code}
> if [ "$propertiesStarted" -gt "0" ]; then
> if [ -z $FILENAME ]; then
> echo $line
> else
> echo $line >> $FILENAME
> fi
> fi
> {code}
> where the echo do not quote the $line to output
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20121) Hue Migration Tool: param values getting cached
[ https://issues.apache.org/jira/browse/AMBARI-20121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-20121: - Status: Patch Available (was: Open) > Hue Migration Tool: param values getting cached > --- > > Key: AMBARI-20121 > URL: https://issues.apache.org/jira/browse/AMBARI-20121 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk > > Attachments: AMBARI-20121.patch > > > When navigating away from a route the values are getting cached on returning > to the route which is causing unexpected migrations > hiveView15 is an instance of hive-view version1.5 > hiveView20 is an instance of hive-view version2.0 > 1. Migrate the Hive-history queries (user admin,instance hiveView15,startdate > :2017-02-21,enddate:2017-02-22) > 2. Migrate the Hive-saved queries (user admin,instance hiveView15,startdate > :2017-02-21,enddate:2017-02-22) > 3. Migrate the Hive-history queries (user admin,instance hiveView20,startdate > :2017-02-21,enddate:2017-02-22) **different instanceName > But The UI shows migration to "hiveView20" happened twice. It uses the > previously cached value in 'admin' for the variable 'username' for migrating > artifacts. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20121) Hue Migration Tool: param values getting cached
[ https://issues.apache.org/jira/browse/AMBARI-20121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-20121: - Attachment: AMBARI-20121.patch > Hue Migration Tool: param values getting cached > --- > > Key: AMBARI-20121 > URL: https://issues.apache.org/jira/browse/AMBARI-20121 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk > > Attachments: AMBARI-20121.patch > > > When navigating away from a route the values are getting cached on returning > to the route which is causing unexpected migrations > hiveView15 is an instance of hive-view version1.5 > hiveView20 is an instance of hive-view version2.0 > 1. Migrate the Hive-history queries (user admin,instance hiveView15,startdate > :2017-02-21,enddate:2017-02-22) > 2. Migrate the Hive-saved queries (user admin,instance hiveView15,startdate > :2017-02-21,enddate:2017-02-22) > 3. Migrate the Hive-history queries (user admin,instance hiveView20,startdate > :2017-02-21,enddate:2017-02-22) **different instanceName > But The UI shows migration to "hiveView20" happened twice. It uses the > previously cached value in 'admin' for the variable 'username' for migrating > artifacts. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20121) Hue Migration Tool: param values getting cached
[ https://issues.apache.org/jira/browse/AMBARI-20121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-20121: - Description: When navigating away from a route the values are getting cached on returning to the route which is causing unexpected migrations hiveView15 is an instance of hive-view version1.5 hiveView20 is an instance of hive-view version2.0 1. Migrate the Hive-history queries (user admin,instance hiveView15,startdate :2017-02-21,enddate:2017-02-22) 2. Migrate the Hive-saved queries (user admin,instance hiveView15,startdate :2017-02-21,enddate:2017-02-22) 3. Migrate the Hive-history queries (user admin,instance hiveView20,startdate :2017-02-21,enddate:2017-02-22) **different instanceName But The UI shows migration to "hiveView20" happened twice. It uses the previously cached value in 'admin' for the variable 'username' for migrating artifacts. was: hiveView15 is an instance of hive-view version1.5 hiveView20 is an instance of hive-view version2.0 1. Migrate the Hive-history queries (user admin,instance hiveView15,startdate :2017-02-21,enddate:2017-02-22) 2. Migrate the Hive-saved queries (user admin,instance hiveView15,startdate :2017-02-21,enddate:2017-02-22) 3. Migrate the Hive-history queries (user admin,instance hiveView20,startdate :2017-02-21,enddate:2017-02-22) **different instanceName But The UI shows migration to "hiveView20" happened twice. It uses the previously cached value in 'admin' for the variable 'username' for migrating artifacts. > Hue Migration Tool: param values getting cached > --- > > Key: AMBARI-20121 > URL: https://issues.apache.org/jira/browse/AMBARI-20121 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk > > > When navigating away from a route the values are getting cached on returning > to the route which is causing unexpected migrations > hiveView15 is an instance of hive-view version1.5 > hiveView20 is an instance of hive-view version2.0 > 1. Migrate the Hive-history queries (user admin,instance hiveView15,startdate > :2017-02-21,enddate:2017-02-22) > 2. Migrate the Hive-saved queries (user admin,instance hiveView15,startdate > :2017-02-21,enddate:2017-02-22) > 3. Migrate the Hive-history queries (user admin,instance hiveView20,startdate > :2017-02-21,enddate:2017-02-22) **different instanceName > But The UI shows migration to "hiveView20" happened twice. It uses the > previously cached value in 'admin' for the variable 'username' for migrating > artifacts. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20121) Hue Migration Tool: param values getting cached
Ishan Bhatt created AMBARI-20121: Summary: Hue Migration Tool: param values getting cached Key: AMBARI-20121 URL: https://issues.apache.org/jira/browse/AMBARI-20121 Project: Ambari Issue Type: Bug Components: ambari-views Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: trunk hiveView15 is an instance of hive-view version1.5 hiveView20 is an instance of hive-view version2.0 1. Migrate the Hive-history queries (user admin,instance hiveView15,startdate :2017-02-21,enddate:2017-02-22) 2. Migrate the Hive-saved queries (user admin,instance hiveView15,startdate :2017-02-21,enddate:2017-02-22) 3. Migrate the Hive-history queries (user admin,instance hiveView20,startdate :2017-02-21,enddate:2017-02-22) **different instanceName But The UI shows migration to "hiveView20" happened twice. It uses the previously cached value in 'admin' for the variable 'username' for migrating artifacts. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20120) Error during EU while updating Ranger Log4J service configs
[
https://issues.apache.org/jira/browse/AMBARI-20120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley reassigned AMBARI-20120:
Assignee: Jonathan Hurley
Affects Version/s: 2.5.0
Fix Version/s: 2.5.0
> Error during EU while updating Ranger Log4J service configs
> ---
>
> Key: AMBARI-20120
> URL: https://issues.apache.org/jira/browse/AMBARI-20120
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20120.patch
>
>
> Perform an HDP upgrade from 2.3 to 2.4 where Ranger is an installed service.
> *Result*
> Observed errors while updating below Ranger service configs:
> Updating configuration usersync-log4j
> Updating configuration admin-log4j
> {code}
> Server action failed
> Could not find desired config type with name admin-log4j
> {code}
> - Both {{usersync-log4j}} and {{admin-log4j}} appear in Ranger 0.6.0 which is
> first used by HDP 2.5. Therefore, the configuration changes should simply be
> removed from upgrades on stacks before HDP 2.5
> - Additionally, I found {{RANGER_TAGSYNC}} references in HDP 2.3 and HDP 2.4.
> This component also first appeared in Ranger 0.6.0, so it should also be
> removed from earlier upgrade packs.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20120) Error during EU while updating Ranger Log4J service configs
[
https://issues.apache.org/jira/browse/AMBARI-20120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-20120:
-
Attachment: AMBARI-20120.patch
> Error during EU while updating Ranger Log4J service configs
> ---
>
> Key: AMBARI-20120
> URL: https://issues.apache.org/jira/browse/AMBARI-20120
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20120.patch
>
>
> Perform an HDP upgrade from 2.3 to 2.4 where Ranger is an installed service.
> *Result*
> Observed errors while updating below Ranger service configs:
> Updating configuration usersync-log4j
> Updating configuration admin-log4j
> {code}
> Server action failed
> Could not find desired config type with name admin-log4j
> {code}
> - Both {{usersync-log4j}} and {{admin-log4j}} appear in Ranger 0.6.0 which is
> first used by HDP 2.5. Therefore, the configuration changes should simply be
> removed from upgrades on stacks before HDP 2.5
> - Additionally, I found {{RANGER_TAGSYNC}} references in HDP 2.3 and HDP 2.4.
> This component also first appeared in Ranger 0.6.0, so it should also be
> removed from earlier upgrade packs.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20120) Error during EU while updating Ranger Log4J service configs
[
https://issues.apache.org/jira/browse/AMBARI-20120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-20120:
-
Status: Patch Available (was: Open)
> Error during EU while updating Ranger Log4J service configs
> ---
>
> Key: AMBARI-20120
> URL: https://issues.apache.org/jira/browse/AMBARI-20120
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20120.patch
>
>
> Perform an HDP upgrade from 2.3 to 2.4 where Ranger is an installed service.
> *Result*
> Observed errors while updating below Ranger service configs:
> Updating configuration usersync-log4j
> Updating configuration admin-log4j
> {code}
> Server action failed
> Could not find desired config type with name admin-log4j
> {code}
> - Both {{usersync-log4j}} and {{admin-log4j}} appear in Ranger 0.6.0 which is
> first used by HDP 2.5. Therefore, the configuration changes should simply be
> removed from upgrades on stacks before HDP 2.5
> - Additionally, I found {{RANGER_TAGSYNC}} references in HDP 2.3 and HDP 2.4.
> This component also first appeared in Ranger 0.6.0, so it should also be
> removed from earlier upgrade packs.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20120) Error during EU while updating Ranger Log4J service configs
Jonathan Hurley created AMBARI-20120:
Summary: Error during EU while updating Ranger Log4J service
configs
Key: AMBARI-20120
URL: https://issues.apache.org/jira/browse/AMBARI-20120
Project: Ambari
Issue Type: Bug
Reporter: Jonathan Hurley
Priority: Critical
Perform an HDP upgrade from 2.3 to 2.4 where Ranger is an installed service.
*Result*
Observed errors while updating below Ranger service configs:
Updating configuration usersync-log4j
Updating configuration admin-log4j
{code}
Server action failed
Could not find desired config type with name admin-log4j
{code}
- Both {{usersync-log4j}} and {{admin-log4j}} appear in Ranger 0.6.0 which is
first used by HDP 2.5. Therefore, the configuration changes should simply be
removed from upgrades on stacks before HDP 2.5
- Additionally, I found {{RANGER_TAGSYNC}} references in HDP 2.3 and HDP 2.4.
This component also first appeared in Ranger 0.6.0, so it should also be
removed from earlier upgrade packs.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20117) Log Search: add global cluster filter for every query
[
https://issues.apache.org/jira/browse/AMBARI-20117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879168#comment-15879168
]
Hadoop QA commented on AMBARI-20117:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12853985/AMBARI-20117.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 16 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-logsearch/ambari-logsearch-portal.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10694//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10694//console
This message is automatically generated.
> Log Search: add global cluster filter for every query
> -
>
> Key: AMBARI-20117
> URL: https://issues.apache.org/jira/browse/AMBARI-20117
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.5.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: trunk
>
> Attachments: AMBARI-20117.patch
>
>
> Adding a global cluster filter for Log Search queries in order to support
> multi cluster environments. (Ambari will filter on cluster name)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20057) "NodeManagers Status" value is empty in Yarn Summary page
[ https://issues.apache.org/jira/browse/AMBARI-20057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-20057: - Resolution: Fixed Status: Resolved (was: Patch Available) > "NodeManagers Status" value is empty in Yarn Summary page > - > > Key: AMBARI-20057 > URL: https://issues.apache.org/jira/browse/AMBARI-20057 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Yesha Vora >Assignee: Antonenko Alexander > Attachments: AMBARI-20057.patch, Screen Shot 2017-02-16 at 1.36.27 > PM.png > > > The value of "NodeManagers Status" is empty in Yarn Summary page. It should > have printed node manager status such as "3 live/0 dead/0 decommissioned". -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19989) Allow user to view Tez View after executing query
[
https://issues.apache.org/jira/browse/AMBARI-19989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879086#comment-15879086
]
Hadoop QA commented on AMBARI-19989:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12853931/AMBARI-19989.02.branch-2.5..patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10693//console
This message is automatically generated.
> Allow user to view Tez View after executing query
> -
>
> Key: AMBARI-19989
> URL: https://issues.apache.org/jira/browse/AMBARI-19989
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: venkat
>Assignee: venkat
> Labels: hive-view
> Fix For: 2.5.0
>
> Attachments: AMBARI-19989.01.branch-2.5.patch,
> AMBARI-19989.02.branch-2.5..patch, AMBARI-19989.branch-2.5.patch
>
>
> As per the parity with Hive View 1.5, allow user to traverse to tez view from
> the query page after executing a query.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20118) Test and fix new modals styles on Ambari
[ https://issues.apache.org/jira/browse/AMBARI-20118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879081#comment-15879081 ] Hudson commented on AMBARI-20118: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6816 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6816/]) AMBARI-20118 Test and fix new modals styles on Ambari. (ababiichuk) (ababiichuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0b6d1cd3b311389e8d385ab782ae78a65b14ef8b]) * (edit) ambari-web/app/views/main/admin/kerberos/disable_view.js * (edit) ambari-web/app/templates/wizard/step3/step3_host_warning_popup_footer.hbs * (edit) ambari-web/app/templates/common/progress.hbs * (edit) ambari-web/app/templates/common/assign_master_components.hbs * (edit) ambari-web/app/styles/theme/bootstrap-ambari.css * (delete) ambari-web/app/templates/common/configs/propertyDependence_footer.hbs * (edit) ambari-web/app/controllers/wizard/step7/assign_master_controller.js * (edit) ambari-web/app/views/wizard/step7/assign_master_view.js * (edit) ambari-web/app/styles/enhanced_service_dashboard.less * (edit) ambari-web/app/templates/main/service/info/save_popup_footer.hbs * (edit) ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js * (edit) ambari-web/app/routes/main.js * (edit) ambari-web/app/views/common/configs/service_configs_by_category_view.js * (edit) ambari-web/app/templates/common/modal_popup.hbs * (edit) ambari-web/app/styles/stack_versions.less * (edit) ambari-web/app/views/common/assign_master_components_view.js * (edit) ambari-web/app/styles/modal_popups.less * (edit) ambari-web/app/controllers/wizard/step9_controller.js > Test and fix new modals styles on Ambari > > > Key: AMBARI-20118 > URL: https://issues.apache.org/jira/browse/AMBARI-20118 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-20118.patch > > > Apply updated modal styles to ambari-web and fix inconsistences. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20118) Test and fix new modals styles on Ambari
[ https://issues.apache.org/jira/browse/AMBARI-20118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-20118: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > Test and fix new modals styles on Ambari > > > Key: AMBARI-20118 > URL: https://issues.apache.org/jira/browse/AMBARI-20118 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-20118.patch > > > Apply updated modal styles to ambari-web and fix inconsistences. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20118) Test and fix new modals styles on Ambari
[
https://issues.apache.org/jira/browse/AMBARI-20118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15878992#comment-15878992
]
Hadoop QA commented on AMBARI-20118:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12854010/AMBARI-20118.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10692//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10692//console
This message is automatically generated.
> Test and fix new modals styles on Ambari
>
>
> Key: AMBARI-20118
> URL: https://issues.apache.org/jira/browse/AMBARI-20118
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-20118.patch
>
>
> Apply updated modal styles to ambari-web and fix inconsistences.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20119) "Use RedHat Satellite/Spacewalk" setting not working correctly in Ambari 2.4.2.0
[ https://issues.apache.org/jira/browse/AMBARI-20119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-20119: Attachment: AMBARI-20119.patch > "Use RedHat Satellite/Spacewalk" setting not working correctly in Ambari > 2.4.2.0 > > > Key: AMBARI-20119 > URL: https://issues.apache.org/jira/browse/AMBARI-20119 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20119.patch > > > In Ambari 2.4.2.0, the "Use RedHat Satellite/Spacewalk" button does not work > and persist. > I have outlined the procedure to test. in "Testing Procedure" field below. In > addition to that, even if we go and manually edit the repository file, next > time Ambari does a Install operation (can be triggered by "Stop All/Start > All" sequence of operations ), it overwrites the file with original repo > files and not leave it to Satellite managed. > The feature works as expected in Ambari 2.4.0.0. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20119) "Use RedHat Satellite/Spacewalk" setting not working correctly in Ambari 2.4.2.0
[ https://issues.apache.org/jira/browse/AMBARI-20119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-20119: Fix Version/s: 2.5.0 Description: In Ambari 2.4.2.0, the "Use RedHat Satellite/Spacewalk" button does not work and persist. I have outlined the procedure to test. in "Testing Procedure" field below. In addition to that, even if we go and manually edit the repository file, next time Ambari does a Install operation (can be triggered by "Stop All/Start All" sequence of operations ), it overwrites the file with original repo files and not leave it to Satellite managed. The feature works as expected in Ambari 2.4.0.0. was: In Ambari 2.4.2.0, the "Use RedHat Satellite/Spacewalk" button does not work and persist. I have outlined the procedure to test. in "Testing Procedure" field below. In addition to that, even if we go and manually edit the repository file, next time Ambari does a Install operation (can be triggered by "Stop All/Start All" sequence of operations ), it overwrites the file with original repo files and not leave it to Satellite managed. The feature works as expected in Ambari 2.4.0.0. > "Use RedHat Satellite/Spacewalk" setting not working correctly in Ambari > 2.4.2.0 > > > Key: AMBARI-20119 > URL: https://issues.apache.org/jira/browse/AMBARI-20119 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Critical > Fix For: 2.5.0 > > > In Ambari 2.4.2.0, the "Use RedHat Satellite/Spacewalk" button does not work > and persist. > I have outlined the procedure to test. in "Testing Procedure" field below. In > addition to that, even if we go and manually edit the repository file, next > time Ambari does a Install operation (can be triggered by "Stop All/Start > All" sequence of operations ), it overwrites the file with original repo > files and not leave it to Satellite managed. > The feature works as expected in Ambari 2.4.0.0. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20119) "Use RedHat Satellite/Spacewalk" setting not working correctly in Ambari 2.4.2.0
Dmitry Lysnichenko created AMBARI-20119: --- Summary: "Use RedHat Satellite/Spacewalk" setting not working correctly in Ambari 2.4.2.0 Key: AMBARI-20119 URL: https://issues.apache.org/jira/browse/AMBARI-20119 Project: Ambari Issue Type: Bug Reporter: Dmitry Lysnichenko Assignee: Dmitry Lysnichenko Priority: Critical In Ambari 2.4.2.0, the "Use RedHat Satellite/Spacewalk" button does not work and persist. I have outlined the procedure to test. in "Testing Procedure" field below. In addition to that, even if we go and manually edit the repository file, next time Ambari does a Install operation (can be triggered by "Stop All/Start All" sequence of operations ), it overwrites the file with original repo files and not leave it to Satellite managed. The feature works as expected in Ambari 2.4.0.0. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20119) "Use RedHat Satellite/Spacewalk" setting not working correctly in Ambari 2.4.2.0
[ https://issues.apache.org/jira/browse/AMBARI-20119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-20119: Component/s: ambari-server > "Use RedHat Satellite/Spacewalk" setting not working correctly in Ambari > 2.4.2.0 > > > Key: AMBARI-20119 > URL: https://issues.apache.org/jira/browse/AMBARI-20119 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Critical > > In Ambari 2.4.2.0, the "Use RedHat Satellite/Spacewalk" button does not work > and persist. > I have outlined the procedure to test. in "Testing Procedure" field below. In > addition to that, even if we go and manually edit the repository file, next > time Ambari does a Install operation (can be triggered by "Stop All/Start > All" sequence of operations ), it overwrites the file with original repo > files and not leave it to Satellite managed. > The feature works as expected in Ambari 2.4.0.0. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20118) Test and fix new modals styles on Ambari
[ https://issues.apache.org/jira/browse/AMBARI-20118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-20118: -- Status: Patch Available (was: Open) > Test and fix new modals styles on Ambari > > > Key: AMBARI-20118 > URL: https://issues.apache.org/jira/browse/AMBARI-20118 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-20118.patch > > > Apply updated modal styles to ambari-web and fix inconsistences. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20118) Test and fix new modals styles on Ambari
[ https://issues.apache.org/jira/browse/AMBARI-20118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-20118: -- Attachment: AMBARI-20118.patch > Test and fix new modals styles on Ambari > > > Key: AMBARI-20118 > URL: https://issues.apache.org/jira/browse/AMBARI-20118 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-20118.patch > > > Apply updated modal styles to ambari-web and fix inconsistences. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20118) Test and fix new modals styles on Ambari
Andrii Babiichuk created AMBARI-20118: - Summary: Test and fix new modals styles on Ambari Key: AMBARI-20118 URL: https://issues.apache.org/jira/browse/AMBARI-20118 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Fix For: 3.0.0 Apply updated modal styles to ambari-web and fix inconsistences. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19991) cluster deployment fails if cluster template has fewer host_groups than that in blueprint
[ https://issues.apache.org/jira/browse/AMBARI-19991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-19991: --- Resolution: Fixed Status: Resolved (was: Patch Available) > cluster deployment fails if cluster template has fewer host_groups than that > in blueprint > - > > Key: AMBARI-19991 > URL: https://issues.apache.org/jira/browse/AMBARI-19991 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-19991.patch, AMBARI-19991_v2.patch > > > cluster creation REST API request gets accepted when, cluster template does > not list all the host_groups mentioned in the blueprint. But cluster > deployment hangs showing error message in the logs > Caused by: java.lang.IllegalArgumentException: > TopologyManager.ConfigureClusterTask - prerequisites for config request > processing not yet satisfied > at > org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:908) > at > org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:889) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20089) HiveView2.0: Add new UDF is not working
[ https://issues.apache.org/jira/browse/AMBARI-20089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DIPAYAN BHOWMICK updated AMBARI-20089: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5, trunk. > HiveView2.0: Add new UDF is not working > --- > > Key: AMBARI-20089 > URL: https://issues.apache.org/jira/browse/AMBARI-20089 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha >Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-20089-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19989) Allow user to view Tez View after executing query
[ https://issues.apache.org/jira/browse/AMBARI-19989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DIPAYAN BHOWMICK updated AMBARI-19989: -- Status: Patch Available (was: Open) > Allow user to view Tez View after executing query > - > > Key: AMBARI-19989 > URL: https://issues.apache.org/jira/browse/AMBARI-19989 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Labels: hive-view > Fix For: 2.5.0 > > Attachments: AMBARI-19989.01.branch-2.5.patch, > AMBARI-19989.02.branch-2.5..patch, AMBARI-19989.branch-2.5.patch > > > As per the parity with Hive View 1.5, allow user to traverse to tez view from > the query page after executing a query. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
