[jira] [Commented] (AMBARI-20199) Hive View: Query fails if we have an additional newline after the last query statement ending with ';'
[
https://issues.apache.org/jira/browse/AMBARI-20199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889693#comment-15889693
]
Hudson commented on AMBARI-20199:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6893 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6893/])
AMBARI-20199. HiveView2.0 query fails if we have an additional newline
(dipayan.bhowmick:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4fb86de568347276c99a5cab739b4cab60f49b24])
* (edit)
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/resources/jobs/viewJobs/JobControllerImpl.java
* (edit)
contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/resources/jobs/viewJobs/JobControllerImpl.java
> Hive View: Query fails if we have an additional newline after the last query
> statement ending with ';'
> --
>
> Key: AMBARI-20199
> URL: https://issues.apache.org/jira/browse/AMBARI-20199
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20199.2.branch-2.5.patch,
> AMBARI-20199.branch-2.5.patch
>
>
> Suppose if I have a multiline query like this where the last statement ends
> with ';' and has an additional newline char
> {code:java}
> SELECT * FROM timesheet limit 5;
> SELECT * FROM drivers limit 5;
> {code}
> Then the query fails with following error:
> {code:java}
> org.apache.hive.service.cli.HiveSQLException: Error while compiling
> statement: FAILED: ParseException line 1:0 cannot recognize input near
> '' '' ''
> {code}
> entire trace:
> {code:java}
> java.lang.Exception: org.apache.hive.service.cli.HiveSQLException: Error
> while compiling statement: FAILED: ParseException line 1:0 cannot recognize
> input near '' '' ''
> java.lang.Exception: org.apache.hive.service.cli.HiveSQLException: Error
> while compiling statement: FAILED: ParseException line 1:0 cannot recognize
> input near '' '' ''
> at
> org.apache.ambari.view.hive20.resources.jobs.JobService.getOne(JobService.java:146)
> at sun.reflect.GeneratedMethodAccessor697.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at
> co
[jira] [Commented] (AMBARI-20207) proper error is not thrown on hive view authorization page
[ https://issues.apache.org/jira/browse/AMBARI-20207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889692#comment-15889692 ] Hudson commented on AMBARI-20207: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6893 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6893/]) AMBARI-20207. Proper error is not thrown on hive view authorization (dipayan.bhowmick: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0712ef69fd81611e80273259660ef23d49187334]) * (edit) contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/resources/system/ranger/RangerService.java > proper error is not thrown on hive view authorization page > -- > > Key: AMBARI-20207 > URL: https://issues.apache.org/jira/browse/AMBARI-20207 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: DIPAYAN BHOWMICK >Assignee: DIPAYAN BHOWMICK > Fix For: 2.5.0 > > Attachments: AMBARI-20207.branch-2.5.patch > > > proper error is not thrown on hive view authorization page in case of > following scenarios: > if wrong username/password is configured in hive view config > if repo name is wrong in hive view config -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20177) Hive View 2.0: Edit table popup has wrong title 'Create Database' and control buttons edit/cancel are misplaced in lower resolutions
[ https://issues.apache.org/jira/browse/AMBARI-20177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889694#comment-15889694 ] Hudson commented on AMBARI-20177: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6893 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6893/]) AMBARI-20177. HiveView2.0: Text 'Create Database' is shown on UI with (dipayan.bhowmick: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=04039a6542c6f9cd4d44ead1107aac69dec1e8ff]) * (edit) contrib/views/hive20/src/main/resources/ui/app/templates/components/table-advanced-settings.hbs * (edit) contrib/views/hive20/src/main/resources/ui/app/templates/components/edit-table.hbs * (edit) contrib/views/hive20/src/main/resources/ui/app/templates/databases/database/tables/table/edit.hbs > Hive View 2.0: Edit table popup has wrong title 'Create Database' and control > buttons edit/cancel are misplaced in lower resolutions > > > Key: AMBARI-20177 > URL: https://issues.apache.org/jira/browse/AMBARI-20177 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: DIPAYAN BHOWMICK >Assignee: DIPAYAN BHOWMICK > Fix For: 2.5.0 > > Attachments: AMBARI-20177.branch-2.5.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20186) HiveView 2.0: Result tab prints nothing for select query on empty table
[ https://issues.apache.org/jira/browse/AMBARI-20186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889691#comment-15889691 ] Hudson commented on AMBARI-20186: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6893 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6893/]) AMBARI-20186. Result tab prints nothing for select query on empty table. (dipayan.bhowmick: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=561f65d573b568db09b842e4c9bb70fc77ae7723]) * (edit) contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/client/NonPersistentCursor.java * (edit) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/actor/message/job/NoMoreItems.java * (edit) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/actor/ResultSetIterator.java * (edit) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/client/NonPersistentCursor.java * (edit) contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/actor/ResultSetIterator.java * (edit) contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/actor/message/job/NoMoreItems.java > HiveView 2.0: Result tab prints nothing for select query on empty table > --- > > Key: AMBARI-20186 > URL: https://issues.apache.org/jira/browse/AMBARI-20186 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Yesha Vora >Assignee: DIPAYAN BHOWMICK > Attachments: AMBARI-20186.branch-2.5.patch > > > Scenario: > * Create an empty table > * Run Select * from table > Current behavior: > The result tab does not show anything. > Expected: > Result tab should show an empty table as below. > | column1 | column2 | column3 | > Since there is no data printed, It confuses the user regarding result. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20213) HiveView2.0 - order jobs with most recent first
[ https://issues.apache.org/jira/browse/AMBARI-20213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889690#comment-15889690 ] Hudson commented on AMBARI-20213: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6893 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6893/]) AMBARI-20213. HiveView2.0 - order jobs with most recent first. (dipayan.bhowmick: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4c0690ac5460d64c09bc0799d1a11b02520a0cba]) * (edit) contrib/views/hive20/src/main/resources/ui/app/components/jobs-browser.js > HiveView2.0 - order jobs with most recent first > --- > > Key: AMBARI-20213 > URL: https://issues.apache.org/jira/browse/AMBARI-20213 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: DIPAYAN BHOWMICK >Assignee: DIPAYAN BHOWMICK > Fix For: 2.5.0 > > Attachments: AMBARI-20213.branch-2.5.patch > > > Jobs in HIve View should be sorted by most recent ones first, as that is what > people would be interested in most of the time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20177) Hive View 2.0: Edit table popup has wrong title 'Create Database' and control buttons edit/cancel are misplaced in lower resolutions
[ https://issues.apache.org/jira/browse/AMBARI-20177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889687#comment-15889687 ] Hudson commented on AMBARI-20177: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1133 (See [https://builds.apache.org/job/Ambari-branch-2.5/1133/]) AMBARI-20177. HiveView2.0: Text 'Create Database' is shown on UI with (dipayan.bhowmick: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ad94fcc2e86fee88f723f36f9472f9ef137c9be3]) * (edit) contrib/views/hive20/src/main/resources/ui/app/templates/components/edit-table.hbs * (edit) contrib/views/hive20/src/main/resources/ui/app/templates/components/table-advanced-settings.hbs * (edit) contrib/views/hive20/src/main/resources/ui/app/templates/databases/database/tables/table/edit.hbs > Hive View 2.0: Edit table popup has wrong title 'Create Database' and control > buttons edit/cancel are misplaced in lower resolutions > > > Key: AMBARI-20177 > URL: https://issues.apache.org/jira/browse/AMBARI-20177 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: DIPAYAN BHOWMICK >Assignee: DIPAYAN BHOWMICK > Fix For: 2.5.0 > > Attachments: AMBARI-20177.branch-2.5.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20204) Huemigration View not working with Oracle Db(Single cluster)
[ https://issues.apache.org/jira/browse/AMBARI-20204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20204: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Huemigration View not working with Oracle Db(Single cluster) > > > Key: AMBARI-20204 > URL: https://issues.apache.org/jira/browse/AMBARI-20204 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-20204.patch, Screen Shot 2017-02-23 at 2.59.09 > PM.png > > > The Hue-Server and Ambari-server has been setup on oracle DB. > Instance Names are not visible In hue-migration view. > The Rest Api is also returning null. > After resolving this other issues persist like Class not overrided for oracle > correctly for pig and hive, timestamp insertion to ambari database incorrect, > no support for Hive later versions and date format wrong for fetching Hue > queries -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20186) HiveView 2.0: Result tab prints nothing for select query on empty table
[ https://issues.apache.org/jira/browse/AMBARI-20186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889684#comment-15889684 ] Hudson commented on AMBARI-20186: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1133 (See [https://builds.apache.org/job/Ambari-branch-2.5/1133/]) AMBARI-20186. Result tab prints nothing for select query on empty table. (dipayan.bhowmick: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=952ee58de5406663a4e7df4060928664ecd576cb]) * (edit) contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/actor/ResultSetIterator.java * (edit) contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/actor/message/job/NoMoreItems.java * (edit) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/actor/message/job/NoMoreItems.java * (edit) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/actor/ResultSetIterator.java * (edit) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/client/NonPersistentCursor.java * (edit) contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/client/NonPersistentCursor.java > HiveView 2.0: Result tab prints nothing for select query on empty table > --- > > Key: AMBARI-20186 > URL: https://issues.apache.org/jira/browse/AMBARI-20186 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Yesha Vora >Assignee: DIPAYAN BHOWMICK > Attachments: AMBARI-20186.branch-2.5.patch > > > Scenario: > * Create an empty table > * Run Select * from table > Current behavior: > The result tab does not show anything. > Expected: > Result tab should show an empty table as below. > | column1 | column2 | column3 | > Since there is no data printed, It confuses the user regarding result. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20207) proper error is not thrown on hive view authorization page
[ https://issues.apache.org/jira/browse/AMBARI-20207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889685#comment-15889685 ] Hudson commented on AMBARI-20207: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1133 (See [https://builds.apache.org/job/Ambari-branch-2.5/1133/]) AMBARI-20207. Proper error is not thrown on hive view authorization (dipayan.bhowmick: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=da9669763fd5225423f99bdd9364303009b1a8bb]) * (edit) contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/resources/system/ranger/RangerService.java > proper error is not thrown on hive view authorization page > -- > > Key: AMBARI-20207 > URL: https://issues.apache.org/jira/browse/AMBARI-20207 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: DIPAYAN BHOWMICK >Assignee: DIPAYAN BHOWMICK > Fix For: 2.5.0 > > Attachments: AMBARI-20207.branch-2.5.patch > > > proper error is not thrown on hive view authorization page in case of > following scenarios: > if wrong username/password is configured in hive view config > if repo name is wrong in hive view config -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20204) Huemigration View not working with Oracle Db(Single cluster)
[ https://issues.apache.org/jira/browse/AMBARI-20204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-20204: -- Fix Version/s: (was: trunk) 2.5.0 > Huemigration View not working with Oracle Db(Single cluster) > > > Key: AMBARI-20204 > URL: https://issues.apache.org/jira/browse/AMBARI-20204 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20204.patch, Screen Shot 2017-02-23 at 2.59.09 > PM.png > > > The Hue-Server and Ambari-server has been setup on oracle DB. > Instance Names are not visible In hue-migration view. > The Rest Api is also returning null. > After resolving this other issues persist like Class not overrided for oracle > correctly for pig and hive, timestamp insertion to ambari database incorrect, > no support for Hive later versions and date format wrong for fetching Hue > queries -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20200) hive-site.xml, hbase-site.xml, etc. are not found in class path for Zeppelin
[ https://issues.apache.org/jira/browse/AMBARI-20200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-20200: - Attachment: AMBARI-20200_branch-2.5_v4.patch > hive-site.xml, hbase-site.xml, etc. are not found in class path for Zeppelin > > > Key: AMBARI-20200 > URL: https://issues.apache.org/jira/browse/AMBARI-20200 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: AMBARI-20200_branch-2.5_v1.patch, > AMBARI-20200_branch-2.5_v2.patch, AMBARI-20200_branch-2.5_v3.patch, > AMBARI-20200_branch-2.5_v4.patch > > > hive-site.xml, hbase-site.xml, etc. are not found in class path for > Zeppelin's interpreter. > As a result of which JDBC:phoenix on kerberos mode doesn't work. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20213) HiveView2.0 - order jobs with most recent first
[ https://issues.apache.org/jira/browse/AMBARI-20213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889683#comment-15889683 ] Hudson commented on AMBARI-20213: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1133 (See [https://builds.apache.org/job/Ambari-branch-2.5/1133/]) AMBARI-20213. HiveView2.0 - order jobs with most recent first. (dipayan.bhowmick: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=eb0733e7477b3a303568fb87391a212e90bd1423]) * (edit) contrib/views/hive20/src/main/resources/ui/app/components/jobs-browser.js > HiveView2.0 - order jobs with most recent first > --- > > Key: AMBARI-20213 > URL: https://issues.apache.org/jira/browse/AMBARI-20213 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: DIPAYAN BHOWMICK >Assignee: DIPAYAN BHOWMICK > Fix For: 2.5.0 > > Attachments: AMBARI-20213.branch-2.5.patch > > > Jobs in HIve View should be sorted by most recent ones first, as that is what > people would be interested in most of the time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20199) Hive View: Query fails if we have an additional newline after the last query statement ending with ';'
[
https://issues.apache.org/jira/browse/AMBARI-20199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889686#comment-15889686
]
Hudson commented on AMBARI-20199:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1133 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1133/])
AMBARI-20199. HiveView2.0 query fails if we have an additional newline
(dipayan.bhowmick:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e9475c4795aca8040c69c61b46d8d0406ce5dcaa])
* (edit)
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/resources/jobs/viewJobs/JobControllerImpl.java
* (edit)
contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/resources/jobs/viewJobs/JobControllerImpl.java
> Hive View: Query fails if we have an additional newline after the last query
> statement ending with ';'
> --
>
> Key: AMBARI-20199
> URL: https://issues.apache.org/jira/browse/AMBARI-20199
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20199.2.branch-2.5.patch,
> AMBARI-20199.branch-2.5.patch
>
>
> Suppose if I have a multiline query like this where the last statement ends
> with ';' and has an additional newline char
> {code:java}
> SELECT * FROM timesheet limit 5;
> SELECT * FROM drivers limit 5;
> {code}
> Then the query fails with following error:
> {code:java}
> org.apache.hive.service.cli.HiveSQLException: Error while compiling
> statement: FAILED: ParseException line 1:0 cannot recognize input near
> '' '' ''
> {code}
> entire trace:
> {code:java}
> java.lang.Exception: org.apache.hive.service.cli.HiveSQLException: Error
> while compiling statement: FAILED: ParseException line 1:0 cannot recognize
> input near '' '' ''
> java.lang.Exception: org.apache.hive.service.cli.HiveSQLException: Error
> while compiling statement: FAILED: ParseException line 1:0 cannot recognize
> input near '' '' ''
> at
> org.apache.ambari.view.hive20.resources.jobs.JobService.getOne(JobService.java:146)
> at sun.reflect.GeneratedMethodAccessor697.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at
> com.su
[jira] [Updated] (AMBARI-20206) Workflow manager is allowing to have empty action node
[ https://issues.apache.org/jira/browse/AMBARI-20206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20206: - Attachment: AMBARI-20206_trunk.patch > Workflow manager is allowing to have empty action node > -- > > Key: AMBARI-20206 > URL: https://issues.apache.org/jira/browse/AMBARI-20206 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20206_trunk.patch > > > Workflow manager is allowing to have empty action node. > Steps to reproduce : > 1) Add a new node to the workflow > 2) Delete node name and keep it empty. > 3) Workflow manager is not complaining about empty node name. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20206) Workflow manager is allowing to have empty action node
[ https://issues.apache.org/jira/browse/AMBARI-20206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20206: - Status: Patch Available (was: Open) > Workflow manager is allowing to have empty action node > -- > > Key: AMBARI-20206 > URL: https://issues.apache.org/jira/browse/AMBARI-20206 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Padma Priya Nagaraj > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20206_trunk.patch > > > Workflow manager is allowing to have empty action node. > Steps to reproduce : > 1) Add a new node to the workflow > 2) Delete node name and keep it empty. > 3) Workflow manager is not complaining about empty node name. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20131) Workflow details are lost upon refreshing the browser
[ https://issues.apache.org/jira/browse/AMBARI-20131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20131: - Status: Patch Available (was: Open) > Workflow details are lost upon refreshing the browser > - > > Key: AMBARI-20131 > URL: https://issues.apache.org/jira/browse/AMBARI-20131 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Padma Priya Nagaraj >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20131_trunk.patch > > > Workflow details are lost upon refreshing the browser. > Steps to reproduce : > 1) Create a new workflow. > 2) Now refresh the browser. > 3) Upon refreshing, the previous workflow tab is not displayed and all the > unsaved works are lost. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20248) get_not_managed_resources.py issue
[
https://issues.apache.org/jira/browse/AMBARI-20248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889668#comment-15889668
]
Hadoop QA commented on AMBARI-20248:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12855301/AMBARI-20248.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 .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10812//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10812//console
This message is automatically generated.
> get_not_managed_resources.py issue
> --
>
> Key: AMBARI-20248
> URL: https://issues.apache.org/jira/browse/AMBARI-20248
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: zhangxiaolu
> Fix For: trunk
>
> Attachments: AMBARI-20248.patch, screenshot-1.png
>
>
> File
> "/var/lib/ambari-agent/cache/common-services/IMPALA/2.2.0/package/scripts/params_linux.py",
> line 166, in
> immutable_paths = get_not_managed_resources(),
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_not_managed_resources.py",
> line 36, in get_not_managed_resources
> not_managed_hdfs_path_list =
> json.loads(config['hostLevelParams']['not_managed_hdfs_path_list'])[:]
> File "/usr/lib64/python2.6/json/__init__.py", line 307, in loads
> return _default_decoder.decode(s)
> File "/usr/lib64/python2.6/json/decoder.py", line 319, in decode
> obj, end = self.raw_decode(s, idx=_w(s, 0).end())
> TypeError: expected string or buffer
> INFO 2017-03-01 15:05:06,690 logger.py:71 - Mount point for directory
> /hadoop/hdfs/data is /
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20131) Workflow details are lost upon refreshing the browser
[ https://issues.apache.org/jira/browse/AMBARI-20131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padma Priya Nagaraj updated AMBARI-20131: - Attachment: AMBARI-20131_trunk.patch > Workflow details are lost upon refreshing the browser > - > > Key: AMBARI-20131 > URL: https://issues.apache.org/jira/browse/AMBARI-20131 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: Padma Priya Nagaraj >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20131_trunk.patch > > > Workflow details are lost upon refreshing the browser. > Steps to reproduce : > 1) Create a new workflow. > 2) Now refresh the browser. > 3) Upon refreshing, the previous workflow tab is not displayed and all the > unsaved works are lost. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20094) Zeppelin should configure hadoop.proxyuser in HDFS core-site.xml
[ https://issues.apache.org/jira/browse/AMBARI-20094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889652#comment-15889652 ] Renjith Kamath commented on AMBARI-20094: - Committed to branch-2.5 and trunk > Zeppelin should configure hadoop.proxyuser in HDFS core-site.xml > > > Key: AMBARI-20094 > URL: https://issues.apache.org/jira/browse/AMBARI-20094 > Project: Ambari > Issue Type: Bug >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: AMBARI-20094_branch-2.5_v1.patch, > AMBARI-20094_branch-2.5_v2.patch > > > Zeppelin should configure hadoop.proxyuser.zeppelin.groups and > hadoop.proxyuser.zeppelin.hosts in HDFS core-site.xml -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20094) Zeppelin should configure hadoop.proxyuser in HDFS core-site.xml
[ https://issues.apache.org/jira/browse/AMBARI-20094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renjith Kamath updated AMBARI-20094: Resolution: Fixed Status: Resolved (was: Patch Available) > Zeppelin should configure hadoop.proxyuser in HDFS core-site.xml > > > Key: AMBARI-20094 > URL: https://issues.apache.org/jira/browse/AMBARI-20094 > Project: Ambari > Issue Type: Bug >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: AMBARI-20094_branch-2.5_v1.patch, > AMBARI-20094_branch-2.5_v2.patch > > > Zeppelin should configure hadoop.proxyuser.zeppelin.groups and > hadoop.proxyuser.zeppelin.hosts in HDFS core-site.xml -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20216) HiveView2.0: Database and tables info doesn't match after navigating between tabs and landing back on Tables tab
[ https://issues.apache.org/jira/browse/AMBARI-20216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889647#comment-15889647 ] Hudson commented on AMBARI-20216: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6892 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6892/]) AMBARI-20216. HiveView2.0: Database and tables info doesn't match after (dipayan.bhowmick: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0ffa4789ad2372859287b8c0264e8b080fd1d8df]) * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/databases/database/tables.js * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/databases.js > HiveView2.0: Database and tables info doesn't match after navigating between > tabs and landing back on Tables tab > > > Key: AMBARI-20216 > URL: https://issues.apache.org/jira/browse/AMBARI-20216 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: DIPAYAN BHOWMICK >Assignee: DIPAYAN BHOWMICK > Fix For: 2.5.0 > > Attachments: AMBARI-20216.branch-2.5.patch > > > STR : > 1. Go to Hive view2 page > 2. Create a table in default database > 3. Browse and choose dipayan db. Tables for dipayan db are loaded > 4. Now switch between tabs - goto Query tab - and come back to tables tab > 5. Database shown is 'default' where as tables is for 'dipayan' table -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20216) HiveView2.0: Database and tables info doesn't match after navigating between tabs and landing back on Tables tab
[ https://issues.apache.org/jira/browse/AMBARI-20216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889642#comment-15889642 ] Hudson commented on AMBARI-20216: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1132 (See [https://builds.apache.org/job/Ambari-branch-2.5/1132/]) AMBARI-20216. HiveView2.0: Database and tables info doesn't match after (dipayan.bhowmick: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f4bee9dff583cce1bff6cc4de02032e876a20b95]) * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/databases/database/tables.js * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/databases.js > HiveView2.0: Database and tables info doesn't match after navigating between > tabs and landing back on Tables tab > > > Key: AMBARI-20216 > URL: https://issues.apache.org/jira/browse/AMBARI-20216 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: DIPAYAN BHOWMICK >Assignee: DIPAYAN BHOWMICK > Fix For: 2.5.0 > > Attachments: AMBARI-20216.branch-2.5.patch > > > STR : > 1. Go to Hive view2 page > 2. Create a table in default database > 3. Browse and choose dipayan db. Tables for dipayan db are loaded > 4. Now switch between tabs - goto Query tab - and come back to tables tab > 5. Database shown is 'default' where as tables is for 'dipayan' table -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20177) Hive View 2.0: Edit table popup has wrong title 'Create Database' and control buttons edit/cancel are misplaced in lower resolutions
[ https://issues.apache.org/jira/browse/AMBARI-20177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DIPAYAN BHOWMICK updated AMBARI-20177: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5, trunk. > Hive View 2.0: Edit table popup has wrong title 'Create Database' and control > buttons edit/cancel are misplaced in lower resolutions > > > Key: AMBARI-20177 > URL: https://issues.apache.org/jira/browse/AMBARI-20177 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: DIPAYAN BHOWMICK >Assignee: DIPAYAN BHOWMICK > Fix For: 2.5.0 > > Attachments: AMBARI-20177.branch-2.5.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20199) Hive View: Query fails if we have an additional newline after the last query statement ending with ';'
[
https://issues.apache.org/jira/browse/AMBARI-20199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
DIPAYAN BHOWMICK updated AMBARI-20199:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to branch-2.5, trunk.
> Hive View: Query fails if we have an additional newline after the last query
> statement ending with ';'
> --
>
> Key: AMBARI-20199
> URL: https://issues.apache.org/jira/browse/AMBARI-20199
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20199.2.branch-2.5.patch,
> AMBARI-20199.branch-2.5.patch
>
>
> Suppose if I have a multiline query like this where the last statement ends
> with ';' and has an additional newline char
> {code:java}
> SELECT * FROM timesheet limit 5;
> SELECT * FROM drivers limit 5;
> {code}
> Then the query fails with following error:
> {code:java}
> org.apache.hive.service.cli.HiveSQLException: Error while compiling
> statement: FAILED: ParseException line 1:0 cannot recognize input near
> '' '' ''
> {code}
> entire trace:
> {code:java}
> java.lang.Exception: org.apache.hive.service.cli.HiveSQLException: Error
> while compiling statement: FAILED: ParseException line 1:0 cannot recognize
> input near '' '' ''
> java.lang.Exception: org.apache.hive.service.cli.HiveSQLException: Error
> while compiling statement: FAILED: ParseException line 1:0 cannot recognize
> input near '' '' ''
> at
> org.apache.ambari.view.hive20.resources.jobs.JobService.getOne(JobService.java:146)
> at sun.reflect.GeneratedMethodAccessor697.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
> at
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1507)
> at
> org.springframework.security.web.FilterChainP
[jira] [Updated] (AMBARI-20207) proper error is not thrown on hive view authorization page
[ https://issues.apache.org/jira/browse/AMBARI-20207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DIPAYAN BHOWMICK updated AMBARI-20207: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5, trunk. > proper error is not thrown on hive view authorization page > -- > > Key: AMBARI-20207 > URL: https://issues.apache.org/jira/browse/AMBARI-20207 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: DIPAYAN BHOWMICK >Assignee: DIPAYAN BHOWMICK > Fix For: 2.5.0 > > Attachments: AMBARI-20207.branch-2.5.patch > > > proper error is not thrown on hive view authorization page in case of > following scenarios: > if wrong username/password is configured in hive view config > if repo name is wrong in hive view config -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20248) get_not_managed_resources.py issue
[ https://issues.apache.org/jira/browse/AMBARI-20248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20248: - Description: File "/var/lib/ambari-agent/cache/common-services/IMPALA/2.2.0/package/scripts/params_linux.py", line 166, in immutable_paths = get_not_managed_resources(), File "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_not_managed_resources.py", line 36, in get_not_managed_resources not_managed_hdfs_path_list = json.loads(config['hostLevelParams']['not_managed_hdfs_path_list'])[:] File "/usr/lib64/python2.6/json/__init__.py", line 307, in loads return _default_decoder.decode(s) File "/usr/lib64/python2.6/json/decoder.py", line 319, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) TypeError: expected string or buffer INFO 2017-03-01 15:05:06,690 logger.py:71 - Mount point for directory /hadoop/hdfs/data is / > get_not_managed_resources.py issue > -- > > Key: AMBARI-20248 > URL: https://issues.apache.org/jira/browse/AMBARI-20248 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20248.patch, screenshot-1.png > > > File > "/var/lib/ambari-agent/cache/common-services/IMPALA/2.2.0/package/scripts/params_linux.py", > line 166, in > immutable_paths = get_not_managed_resources(), > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_not_managed_resources.py", > line 36, in get_not_managed_resources > not_managed_hdfs_path_list = > json.loads(config['hostLevelParams']['not_managed_hdfs_path_list'])[:] > File "/usr/lib64/python2.6/json/__init__.py", line 307, in loads > return _default_decoder.decode(s) > File "/usr/lib64/python2.6/json/decoder.py", line 319, in decode > obj, end = self.raw_decode(s, idx=_w(s, 0).end()) > TypeError: expected string or buffer > INFO 2017-03-01 15:05:06,690 logger.py:71 - Mount point for directory > /hadoop/hdfs/data is / -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20186) HiveView 2.0: Result tab prints nothing for select query on empty table
[ https://issues.apache.org/jira/browse/AMBARI-20186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DIPAYAN BHOWMICK updated AMBARI-20186: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5, trunk. > HiveView 2.0: Result tab prints nothing for select query on empty table > --- > > Key: AMBARI-20186 > URL: https://issues.apache.org/jira/browse/AMBARI-20186 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Yesha Vora >Assignee: DIPAYAN BHOWMICK > Attachments: AMBARI-20186.branch-2.5.patch > > > Scenario: > * Create an empty table > * Run Select * from table > Current behavior: > The result tab does not show anything. > Expected: > Result tab should show an empty table as below. > | column1 | column2 | column3 | > Since there is no data printed, It confuses the user regarding result. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20248) get_not_managed_resources.py issue
[ https://issues.apache.org/jira/browse/AMBARI-20248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20248: - Status: Patch Available (was: Open) > get_not_managed_resources.py issue > -- > > Key: AMBARI-20248 > URL: https://issues.apache.org/jira/browse/AMBARI-20248 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20248.patch, screenshot-1.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20248) get_not_managed_resources.py issue
[ https://issues.apache.org/jira/browse/AMBARI-20248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20248: - Attachment: AMBARI-20248.patch > get_not_managed_resources.py issue > -- > > Key: AMBARI-20248 > URL: https://issues.apache.org/jira/browse/AMBARI-20248 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20248.patch, screenshot-1.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20248) get_not_managed_resources.py issue
[ https://issues.apache.org/jira/browse/AMBARI-20248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-20248: - Attachment: screenshot-1.png > get_not_managed_resources.py issue > -- > > Key: AMBARI-20248 > URL: https://issues.apache.org/jira/browse/AMBARI-20248 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: zhangxiaolu > Fix For: trunk > > Attachments: screenshot-1.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20248) get_not_managed_resources.py issue
zhangxiaolu created AMBARI-20248: Summary: get_not_managed_resources.py issue Key: AMBARI-20248 URL: https://issues.apache.org/jira/browse/AMBARI-20248 Project: Ambari Issue Type: Bug Affects Versions: trunk Reporter: zhangxiaolu Fix For: trunk -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20213) HiveView2.0 - order jobs with most recent first
[ https://issues.apache.org/jira/browse/AMBARI-20213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DIPAYAN BHOWMICK updated AMBARI-20213: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5, trunk. > HiveView2.0 - order jobs with most recent first > --- > > Key: AMBARI-20213 > URL: https://issues.apache.org/jira/browse/AMBARI-20213 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: DIPAYAN BHOWMICK >Assignee: DIPAYAN BHOWMICK > Fix For: 2.5.0 > > Attachments: AMBARI-20213.branch-2.5.patch > > > Jobs in HIve View should be sorted by most recent ones first, as that is what > people would be interested in most of the time. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20247) Show full error while importing the workflow from encrypted file
Belliraj HB created AMBARI-20247: Summary: Show full error while importing the workflow from encrypted file Key: AMBARI-20247 URL: https://issues.apache.org/jira/browse/AMBARI-20247 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Belliraj HB Assignee: M Madhan Mohan Reddy Fix For: 2.5.0 Live cluster : https://172.22.98.248:8443/#/main/views/WORKFLOW_MANAGER/1.0.0/WFM Facing issue while importing workflow where api /api/v1/views/WORKFLOW_MANAGER/versions/1.0.0/instances/WFM/resources/proxy/readWorkflow?workflowPath=/user/hrt_qa/test_WfKillSubwf1/workflow.xml&jobType=WORKFLOW is failing with 500 status code. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20240) a running workflow cannot be killed from WFM ui immediately
[
https://issues.apache.org/jira/browse/AMBARI-20240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Belliraj HB resolved AMBARI-20240.
--
Resolution: Fixed
This is fixed as part of AMBARI-20080. We are informing the user that it may
take some time to change the status to killed and the user needs to refresh.
Oozie takes time to kill a job.
> a running workflow cannot be killed from WFM ui immediately
> ---
>
> Key: AMBARI-20240
> URL: https://issues.apache.org/jira/browse/AMBARI-20240
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: zhixun he
>Assignee: Padma Priya Nagaraj
>Priority: Critical
> Labels: WFD, WFM
> Fix For: 2.5.0
>
>
> Steps:
> 1. log into ambari ui
> 2. go to wfm
> 3. upload workflow from file system:
> https://github.com/hortonworks/certification/blob/pixie-dust/HDPTests/tests/oozie/oozie_1/regression-two/test_WfKillSubwf1/workflow.xml
> 4. submit the workflow
> 5. kill the workflow from WFM ui
> Error:
> workflow ui is still showing running after the kill. Wait 5 min and refresh
> the page, we can see it is killed.
> if you check the log of wf on ui, it showed it is killed several
> times{noformat}
> 2017-02-16 18:25:08,356 INFO DagEngine:520 -
> SERVER[bugbash-r7-oozie-tde-we-2-1.openstacklocal] USER[ambari-server-cl1
> doAs admin] GROUP[-] TOKEN[-] APP[-]
> JOB[003-170215185313202-oozie-oozi-W] ACTION[] User admin killed the WF
> job
> 003-170215185313202-oozie-oozi-W
> 2017-02-16 18:25:18,534 INFO DagEngine:520 -
> SERVER[bugbash-r7-oozie-tde-we-2-
> 1.openstacklocal] USER[ambari-server-cl1 doAs admin] GROUP[-] TOKEN[-] APP[-]
> JOB[003-170215185313202-oozie-oozi-W] ACTION[] User admin killed the WF
> job
> 003-170215185313202-oozie-oozi-W
> 2017-02-16 18:25:57,166 INFO DagEngine:520 -
> SERVER[bugbash-r7-oozie-tde-we-2-
> 1.openstacklocal] USER[ambari-server-cl1 doAs admin] GROUP[-] TOKEN[-] APP[-]
> JOB[003-170215185313202-oozie-oozi-W] ACTION[] User admin killed the WF
> job
> 003-170215185313202-oozie-oozi-W
> 2017-02-16 18:26:02,047 INFO DagEngine:520 -
> SERVER[bugbash-r7-oozie-tde-we-2-
> 1.openstacklocal] USER[ambari-server-cl1 doAs admin] GROUP[-] TOKEN[-] APP[-]
> JOB[003-170215185313202-oozie-oozi-W] ACTION[] User admin killed the WF
> job
> 003-170215185313202-oozie-oozi-W{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20216) HiveView2.0: Database and tables info doesn't match after navigating between tabs and landing back on Tables tab
[ https://issues.apache.org/jira/browse/AMBARI-20216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DIPAYAN BHOWMICK updated AMBARI-20216: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5, trunk. > HiveView2.0: Database and tables info doesn't match after navigating between > tabs and landing back on Tables tab > > > Key: AMBARI-20216 > URL: https://issues.apache.org/jira/browse/AMBARI-20216 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: DIPAYAN BHOWMICK >Assignee: DIPAYAN BHOWMICK > Fix For: 2.5.0 > > Attachments: AMBARI-20216.branch-2.5.patch > > > STR : > 1. Go to Hive view2 page > 2. Create a table in default database > 3. Browse and choose dipayan db. Tables for dipayan db are loaded > 4. Now switch between tabs - goto Query tab - and come back to tables tab > 5. Database shown is 'default' where as tables is for 'dipayan' table -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20246) Not able to preview the xml for coordinator
Supreeth Sharma created AMBARI-20246: Summary: Not able to preview the xml for coordinator Key: AMBARI-20246 URL: https://issues.apache.org/jira/browse/AMBARI-20246 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Supreeth Sharma Priority: Blocker Fix For: 2.5.0 Issue 1: Not able to preview the xml for coordinator. I am not seeing any error in UI console log. Steps to reproduce : 1) Import the coordinator. 2) Import the coordinator. 3) Try to preview the coordinator and UI is not showing preview. Issue 2: After issue 1 is encountered, if user tries to perform any other operations, then UI is getting hung. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20245) Setup tez ats related parameters
[ https://issues.apache.org/jira/browse/AMBARI-20245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20245: --- Status: Patch Available (was: Open) > Setup tez ats related parameters > > > Key: AMBARI-20245 > URL: https://issues.apache.org/jira/browse/AMBARI-20245 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Siddharth Seth >Assignee: Sumit Mohanty >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20245.patch > > > Dags per group needs to be set to 5. > TASK_ATTEMPT events to be ignored needs to be set to > |tez-interactive-site|tez.history.logging.timeline.num-dags-per-group|5| > |tez-site|tez.history.logging.timeline-cache-plugin.old-num-dags-per-group|5| > |tez-intearactive-site|tez.history.logging.taskattempt-filters|EXECUTOR_BUSY,EXTERNAL_PREEMPTION| -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20245) Setup tez ats related parameters
[ https://issues.apache.org/jira/browse/AMBARI-20245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20245: --- Attachment: AMBARI-20245.patch > Setup tez ats related parameters > > > Key: AMBARI-20245 > URL: https://issues.apache.org/jira/browse/AMBARI-20245 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Siddharth Seth >Assignee: Sumit Mohanty >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20245.patch > > > Dags per group needs to be set to 5. > TASK_ATTEMPT events to be ignored needs to be set to > |tez-interactive-site|tez.history.logging.timeline.num-dags-per-group|5| > |tez-site|tez.history.logging.timeline-cache-plugin.old-num-dags-per-group|5| > |tez-intearactive-site|tez.history.logging.taskattempt-filters|EXECUTOR_BUSY,EXTERNAL_PREEMPTION| -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20245) Setup tez ats related parameters
Sumit Mohanty created AMBARI-20245: -- Summary: Setup tez ats related parameters Key: AMBARI-20245 URL: https://issues.apache.org/jira/browse/AMBARI-20245 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.5.0 Reporter: Siddharth Seth Assignee: Sumit Mohanty Priority: Critical Fix For: 2.5.0 Dags per group needs to be set to 5. TASK_ATTEMPT events to be ignored needs to be set to |tez-interactive-site|tez.history.logging.timeline.num-dags-per-group|5| |tez-site|tez.history.logging.timeline-cache-plugin.old-num-dags-per-group|5| |tez-intearactive-site|tez.history.logging.taskattempt-filters|EXECUTOR_BUSY,EXTERNAL_PREEMPTION| -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19599) llap-daemon-log4j.xml is out of sync with hive master
[ https://issues.apache.org/jira/browse/AMBARI-19599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889304#comment-15889304 ] Hudson commented on AMBARI-19599: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6891 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6891/]) AMBARI-19599. Logging options updates in llap-daemon-log4j.xml. (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7808134f56ccd832b6b3f6bad575671eb0f4bb5b]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/llap-daemon-log4j.xml > llap-daemon-log4j.xml is out of sync with hive master > - > > Key: AMBARI-19599 > URL: https://issues.apache.org/jira/browse/AMBARI-19599 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Prasanth Jayachandran >Assignee: Prasanth Jayachandran > Fix For: 2.5.0 > > Attachments: AMBARI-19599.1.patch > > > Few logger changes went to llap log4j properties file. We need to update > llap-daemon-log4j.xml file to reflect those changes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20225) Take care of hive-interactive-site's 'hive.tez.container.size' config during HDP upgrade from 2.5 to 2.6 and update default value for tez-interactive-site's config 't
[
https://issues.apache.org/jira/browse/AMBARI-20225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889302#comment-15889302
]
Hadoop QA commented on AMBARI-20225:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12855244/AMBARI-20225.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10811//console
This message is automatically generated.
> Take care of hive-interactive-site's 'hive.tez.container.size' config during
> HDP upgrade from 2.5 to 2.6 and update default value for
> tez-interactive-site's config 'tez.am.resource.memory.mb'.
>
>
> Key: AMBARI-20225
> URL: https://issues.apache.org/jira/browse/AMBARI-20225
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-20225.patch
>
>
> *Background :*
> We are dealing with 2 specific configs here.
> *(1).* 'tez.am.resource.memory.mb' for tez-interactive-site and
> *(2).* 'hive.tez.container.size' for hive-interactive-site.
> - 'tez.am.resource.memory.mb' already exists in tez-interactive-site from
> Ambari-2.4 onwards and recently its default value had been changed to
> 'SET_ON_FIRST_INVOCATION' in its hive-interacive-site.
> - 'hive.tez.container.size' was inherited and used from Hive1/hive-site in
> Ambari 2.4. Starting from Ambari 2.5, it was added as a config explicitly in
> hive-interactive-site with a default value of 'SET_ON_FIRST_INVOCATION'.
> The non-standard 'SET_ON_FIRST_INVOCATION' was introduced, so as to give a
> hint in Stack Advisor (SA) call for the 1st time on Hive Server Interactive
> ON (enable_hive_interactive config), so that config values for both can be
> calculated and set for the 1st time. Subsequesnt calls in the lifecycle, will
> just read the value set by SA or if later changed by user manually.
> *Problem :*
> 'SET_ON_FIRST_INVOCATION', being non-standard was breaking the code in
> upgrade scenario.
> *Fix:*
> Removing the use of 'SET_ON_FIRST_INVOCATION' and adding code for correct
> behavior of configs during HDP upgrade.
>
> *Possible scenarios:*
> *1. Ambari upgrade from 2.4 - > 2.5 having HDP 2.5. Implying
> 2.5/stack_advisor.py code would have been updated with new LLAP GA logic.*
>- 'tez.am.resource.memory.mb' will already be there whether Hive Server
> Interactive (HSI) is ON or OFF after Ambari upgrade.
> - If HSI if OFF before the upgrade was done, nothing to do over there.
> - If HSI on ON before AMbari upgrade, or is made ON after Ambari
> upgrade, SA logic has been updated to take of reading
> 'hive.tez.container.size' from hive-site as it wont exist in
> hive-interactive-site at this point. It will show up in hive-interative-site
> aftre the HDP upgrade to 2.6
> *2. Ambari 2.4 having HDP 2.5 -> Upgrade to Ambari 2.5 -> Upgraded to HDP 2.6*
>- 'tez.am.resource.memory.mb' will already be there
>- As part of HDP 2.5 upgrade to HDP 2.6, 'hive.tez.container.size' would
> have got added, having current value picked from
> hive-site/hive.tez.container.size. SA code carries a calculation logic for
> config 'hive.tez.container.size', which is bound to yield different value
> compared to hive-site/'hive.tez.container.size'. The config's value will get
> updated/caluclated (1). when HSI is made ON (meaning
> 'enabled_hive_interactive' config detected as **True** in
> changed-configurations).
>
> *3. Ambari 2.5 with HDP 2.5 -> Upgraded to HDP 2.6*
>- Both 'hive.tez.container.size' and 'tez.am.resource.memory.mb' (alreday
> present at HDP 2.5 in hive-interactive-site) will exist after the HDP upgrade.
> *Note* that a fresh value for 'hive.tez.container.size' and
> 'tez.am.resource.memory.mb' is caluclated at below conditions:
> (1). when HSI is made ON, meaning 'enabled_hive_interactive' config detected
> as **True** in changed-configurations, or
> (2). it's a cluster create operation, where HSI also is supposed to be
> started. (BP scenario)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20197) RestMetricsPropertyProvider support nested JSON metrics
[
https://issues.apache.org/jira/browse/AMBARI-20197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889301#comment-15889301
]
Hadoop QA commented on AMBARI-20197:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12855267/AMBARI-20197.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/10810//console
This message is automatically generated.
> RestMetricsPropertyProvider support nested JSON metrics
> ---
>
> Key: AMBARI-20197
> URL: https://issues.apache.org/jira/browse/AMBARI-20197
> Project: Ambari
> Issue Type: Bug
> Components: metrics
>Affects Versions: 2.4.2
>Reporter: Kevin Risden
> Attachments: AMBARI-20197.patch, AMBARI-20197.patch
>
>
> Attempting to use the RestMetricsPropertyProvider with nested metrics results
> in a ClassCastException.
> {code}
> Caused by: java.lang.ClassCastException: com.google.gson.internal.StringMap
> cannot be cast to com.google.gson.JsonElement
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.extractValuesFromJSON(RestMetricsPropertyProvider.java:472)
> {code}
> Based on reading the code, this should be supported by using the # path
> splitter.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20244) HBase indicates restart required after upgrade from Amabri-2.4+HDP-2.5
Aravindan Vijayan created AMBARI-20244:
--
Summary: HBase indicates restart required after upgrade from
Amabri-2.4+HDP-2.5
Key: AMBARI-20244
URL: https://issues.apache.org/jira/browse/AMBARI-20244
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Affects Versions: 2.5.0
Reporter: Aravindan Vijayan
Assignee: Aravindan Vijayan
Priority: Critical
Fix For: 2.5.0
HBase indicates restart required after upgrade to Ambari-2.5 from Ambari-2.4 +
HDP-2.6. The root cause seems to be the addition of a property to
ams-ssl-client config type
Ambari-2.4 deployed
{code}
"properties" : {
"ssl.client.truststore.location" : "/etc/security/clientKeys/all.jks",
"ssl.client.truststore.password" :
"SECRET:ams-ssl-client:1:ssl.client.truststore.password",
"ssl.client.truststore.type" : "jks"
}
{code}
Post upgrade it became the following - *ssl.client.truststore.alias* got added.
{code}
"properties" : {
"ssl.client.truststore.alias" : "",
"ssl.client.truststore.location" : "/etc/security/clientKeys/all.jks",
"ssl.client.truststore.password" :
"SECRET:ams-ssl-client:2:ssl.client.truststore.password",
"ssl.client.truststore.type" : "jks"
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19841) Add 'yarn.client.failover-proxy-provider' in yarn-site.xml by default for all HA enabled clusters
[ https://issues.apache.org/jira/browse/AMBARI-19841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan updated AMBARI-19841: --- Attachment: AMBARI-19841_trunk.patch > Add 'yarn.client.failover-proxy-provider' in yarn-site.xml by default for all > HA enabled clusters > - > > Key: AMBARI-19841 > URL: https://issues.apache.org/jira/browse/AMBARI-19841 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > Attachments: AMBARI-19841_trunk.patch > > > > When HA is enabled, the class to be used by Clients, AMs and > NMs to failover to the Active RM. It should extend > org.apache.hadoop.yarn.client.RMFailoverProxyProvider > yarn.client.failover-proxy-provider > > org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider > > needs to be added to yarn-site.xml for HDP 2.6/fenton -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-19697) Uninstalled services including Ganglia is coming up in Config History-Service dropdown
[ https://issues.apache.org/jira/browse/AMBARI-19697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan reassigned AMBARI-19697: -- Assignee: Antonenko Alexander > Uninstalled services including Ganglia is coming up in Config History-Service > dropdown > -- > > Key: AMBARI-19697 > URL: https://issues.apache.org/jira/browse/AMBARI-19697 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Dhanya Balasundaran >Assignee: Antonenko Alexander > Fix For: 2.5.0 > > > - Navigate to dashboard page > - Choose 'Config History' tab > - Service dropdown has all services supported by the stack. It even shows > Ganglia which is not supported now. > Checked on an older version and its not there. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19697) Uninstalled services including Ganglia is coming up in Config History-Service dropdown
[ https://issues.apache.org/jira/browse/AMBARI-19697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889245#comment-15889245 ] Aravindan Vijayan commented on AMBARI-19697: [~aantonenko] Can we close this? > Uninstalled services including Ganglia is coming up in Config History-Service > dropdown > -- > > Key: AMBARI-19697 > URL: https://issues.apache.org/jira/browse/AMBARI-19697 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Dhanya Balasundaran >Assignee: Antonenko Alexander > Fix For: 2.5.0 > > > - Navigate to dashboard page > - Choose 'Config History' tab > - Service dropdown has all services supported by the stack. It even shows > Ganglia which is not supported now. > Checked on an older version and its not there. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20151) add extra Tez logging configs for Hive
[
https://issues.apache.org/jira/browse/AMBARI-20151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889232#comment-15889232
]
Sumit Mohanty commented on AMBARI-20151:
[~sershe] looks like {{AMBARI-19599. Logging options updates in
llap-daemon-log4j.xml}} was not in trunk. So now the patch does not apply. Can
you recreate the patch?
> add extra Tez logging configs for Hive
> --
>
> Key: AMBARI-20151
> URL: https://issues.apache.org/jira/browse/AMBARI-20151
> Project: Ambari
> Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Fix For: 2.5.0
>
> Attachments: AMBARI-20151.01.patch, AMBARI-20151.02.patch,
> AMBARI-20151.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20197) RestMetricsPropertyProvider support nested JSON metrics
[
https://issues.apache.org/jira/browse/AMBARI-20197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Risden updated AMBARI-20197:
--
Status: Open (was: Patch Available)
> RestMetricsPropertyProvider support nested JSON metrics
> ---
>
> Key: AMBARI-20197
> URL: https://issues.apache.org/jira/browse/AMBARI-20197
> Project: Ambari
> Issue Type: Bug
> Components: metrics
>Affects Versions: 2.4.2
>Reporter: Kevin Risden
> Attachments: AMBARI-20197.patch, AMBARI-20197.patch
>
>
> Attempting to use the RestMetricsPropertyProvider with nested metrics results
> in a ClassCastException.
> {code}
> Caused by: java.lang.ClassCastException: com.google.gson.internal.StringMap
> cannot be cast to com.google.gson.JsonElement
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.extractValuesFromJSON(RestMetricsPropertyProvider.java:472)
> {code}
> Based on reading the code, this should be supported by using the # path
> splitter.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20197) RestMetricsPropertyProvider support nested JSON metrics
[
https://issues.apache.org/jira/browse/AMBARI-20197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Risden updated AMBARI-20197:
--
Attachment: AMBARI-20197.patch
Reattaching to get build to trigger?
> RestMetricsPropertyProvider support nested JSON metrics
> ---
>
> Key: AMBARI-20197
> URL: https://issues.apache.org/jira/browse/AMBARI-20197
> Project: Ambari
> Issue Type: Bug
> Components: metrics
>Affects Versions: 2.4.2
>Reporter: Kevin Risden
> Attachments: AMBARI-20197.patch, AMBARI-20197.patch
>
>
> Attempting to use the RestMetricsPropertyProvider with nested metrics results
> in a ClassCastException.
> {code}
> Caused by: java.lang.ClassCastException: com.google.gson.internal.StringMap
> cannot be cast to com.google.gson.JsonElement
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.extractValuesFromJSON(RestMetricsPropertyProvider.java:472)
> {code}
> Based on reading the code, this should be supported by using the # path
> splitter.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20197) RestMetricsPropertyProvider support nested JSON metrics
[
https://issues.apache.org/jira/browse/AMBARI-20197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Risden updated AMBARI-20197:
--
Status: Patch Available (was: Open)
> RestMetricsPropertyProvider support nested JSON metrics
> ---
>
> Key: AMBARI-20197
> URL: https://issues.apache.org/jira/browse/AMBARI-20197
> Project: Ambari
> Issue Type: Bug
> Components: metrics
>Affects Versions: 2.4.2
>Reporter: Kevin Risden
> Attachments: AMBARI-20197.patch, AMBARI-20197.patch
>
>
> Attempting to use the RestMetricsPropertyProvider with nested metrics results
> in a ClassCastException.
> {code}
> Caused by: java.lang.ClassCastException: com.google.gson.internal.StringMap
> cannot be cast to com.google.gson.JsonElement
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.extractValuesFromJSON(RestMetricsPropertyProvider.java:472)
> {code}
> Based on reading the code, this should be supported by using the # path
> splitter.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20151) add extra Tez logging configs for Hive
[ https://issues.apache.org/jira/browse/AMBARI-20151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889218#comment-15889218 ] Sumit Mohanty commented on AMBARI-20151: Yup will do :-) > add extra Tez logging configs for Hive > -- > > Key: AMBARI-20151 > URL: https://issues.apache.org/jira/browse/AMBARI-20151 > Project: Ambari > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 2.5.0 > > Attachments: AMBARI-20151.01.patch, AMBARI-20151.02.patch, > AMBARI-20151.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-19789) Hive LLAP and Hive2 log4j changes should be removed from upgrade packs hdp 2.3 and hdp 2.4
[ https://issues.apache.org/jira/browse/AMBARI-19789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved AMBARI-19789. Resolution: Fixed > Hive LLAP and Hive2 log4j changes should be removed from upgrade packs hdp > 2.3 and hdp 2.4 > -- > > Key: AMBARI-19789 > URL: https://issues.apache.org/jira/browse/AMBARI-19789 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19660) Add log rotation settings - handle upgrade scenario - Storm, Hive
[ https://issues.apache.org/jira/browse/AMBARI-19660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19660: --- Fix Version/s: 2.5.0 > Add log rotation settings - handle upgrade scenario - Storm, Hive > - > > Key: AMBARI-19660 > URL: https://issues.apache.org/jira/browse/AMBARI-19660 > Project: Ambari > Issue Type: Bug >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > > Changes made to all upgrade packs 2.3->2.4,2.5,2.6 ; 2.4->2.5,2.6 ; 2.5->2.6 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19762) Kerberizing PERF cluster fails since cannot find principal name config in dummy.py
[ https://issues.apache.org/jira/browse/AMBARI-19762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19762: --- Fix Version/s: 2.5.0 > Kerberizing PERF cluster fails since cannot find principal name config in > dummy.py > -- > > Key: AMBARI-19762 > URL: https://issues.apache.org/jira/browse/AMBARI-19762 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > > STR: > Install Ambari 2.5.0 on GCE > Install PERF 1.0 stack with all services > Kerberize the cluster > Start services > Fails on History Server and ZKFC. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19656) Zookeeper, hdfs default values changed by log4j rotation commit needs to be reverted
[ https://issues.apache.org/jira/browse/AMBARI-19656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19656: --- Fix Version/s: 2.5.0 > Zookeeper, hdfs default values changed by log4j rotation commit needs to be > reverted > > > Key: AMBARI-19656 > URL: https://issues.apache.org/jira/browse/AMBARI-19656 > Project: Ambari > Issue Type: Bug >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > > Default value for hdfs maxbackupindex was originally 10, > https://reviews.apache.org/r/54760/ changed it to 20. > Default value for zookeeper maxfilesize and maxbackupindex was originally 10, > https://reviews.apache.org/r/54955/ changed it to 256 and 20 respectively. > Made appropriate corrections in this patch. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19600) AMS log4j rotation properties changes should be visible on ambari-upgrade
[ https://issues.apache.org/jira/browse/AMBARI-19600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19600: --- Fix Version/s: 2.5.0 > AMS log4j rotation properties changes should be visible on ambari-upgrade > - > > Key: AMBARI-19600 > URL: https://issues.apache.org/jira/browse/AMBARI-19600 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > > AMS rotation properties from ams-log4j and ams-hbase-log4j will be seen on > ambari-upgrade. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19541) Add log rotation settings - handle HDP upgrade scenario
[ https://issues.apache.org/jira/browse/AMBARI-19541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19541: --- Fix Version/s: 2.5.0 > Add log rotation settings - handle HDP upgrade scenario > --- > > Key: AMBARI-19541 > URL: https://issues.apache.org/jira/browse/AMBARI-19541 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > Attachments: AMBARI-19541_addendum.patch, AMBARI-19541_trunk.patch > > > This jira will have the upgrade pack work for the following services > YARN > HDFS > HBASE > ZOOKEEPER > OOZIE > FALCON > ATLAS > RANGER > RANGER-KMS > KAFKA > KNOX -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19274) Add common log rotation settings to hbase, zookeeper, ams
[ https://issues.apache.org/jira/browse/AMBARI-19274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19274: --- Fix Version/s: 2.5.0 > Add common log rotation settings to hbase, zookeeper, ams > - > > Key: AMBARI-19274 > URL: https://issues.apache.org/jira/browse/AMBARI-19274 > Project: Ambari > Issue Type: Task >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > Attachments: AMBARI-18814_addendum.patch, AMBARI-19274-2.patch, > AMBARI-19274.patch > > > Add common log rotation settings to hbase, zookeeper, ams -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-18839) ACID transactions is missing description in hive configs
[ https://issues.apache.org/jira/browse/AMBARI-18839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-18839: --- Fix Version/s: 2.5.0 > ACID transactions is missing description in hive configs > > > Key: AMBARI-18839 > URL: https://issues.apache.org/jira/browse/AMBARI-18839 > Project: Ambari > Issue Type: Bug >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > > ACID transaction enabler does not have any description. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-18814) Add common log rotation settings to HDFS configs
[ https://issues.apache.org/jira/browse/AMBARI-18814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-18814: --- Fix Version/s: 2.5.0 > Add common log rotation settings to HDFS configs > > > Key: AMBARI-18814 > URL: https://issues.apache.org/jira/browse/AMBARI-18814 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > Attachments: AMBARI-18814_addendum.patch, AMBARI-18814.patch > > > Add common log rotation settings to HDFS configs -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19538) Add log rotation settings to Hive, Druid, Storm
[ https://issues.apache.org/jira/browse/AMBARI-19538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19538: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Add log rotation settings to Hive, Druid, Storm > --- > > Key: AMBARI-19538 > URL: https://issues.apache.org/jira/browse/AMBARI-19538 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > Attachments: AMBARI-19538.patch > > > This jira is for log4j rotation settings for hive, druid and storm -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19538) Add log rotation settings to Hive, Druid, Storm
[ https://issues.apache.org/jira/browse/AMBARI-19538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19538: --- Fix Version/s: 2.5.0 > Add log rotation settings to Hive, Druid, Storm > --- > > Key: AMBARI-19538 > URL: https://issues.apache.org/jira/browse/AMBARI-19538 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.5.0 > > Attachments: AMBARI-19538.patch > > > This jira is for log4j rotation settings for hive, druid and storm -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20151) add extra Tez logging configs for Hive
[ https://issues.apache.org/jira/browse/AMBARI-20151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889202#comment-15889202 ] Sergey Shelukhin commented on AMBARI-20151: --- [~swapanshridhar] [~sumitmohanty] do you want to commit this? ;) > add extra Tez logging configs for Hive > -- > > Key: AMBARI-20151 > URL: https://issues.apache.org/jira/browse/AMBARI-20151 > Project: Ambari > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 2.5.0 > > Attachments: AMBARI-20151.01.patch, AMBARI-20151.02.patch, > AMBARI-20151.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20225) Take care of hive-interactive-site's 'hive.tez.container.size' config during HDP upgrade from 2.5 to 2.6 and update default value for tez-interactive-site's config 'tez
[ https://issues.apache.org/jira/browse/AMBARI-20225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20225: - Affects Version/s: trunk > Take care of hive-interactive-site's 'hive.tez.container.size' config during > HDP upgrade from 2.5 to 2.6 and update default value for > tez-interactive-site's config 'tez.am.resource.memory.mb'. > > > Key: AMBARI-20225 > URL: https://issues.apache.org/jira/browse/AMBARI-20225 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-20225.patch > > > *Background :* > We are dealing with 2 specific configs here. > *(1).* 'tez.am.resource.memory.mb' for tez-interactive-site and > *(2).* 'hive.tez.container.size' for hive-interactive-site. > - 'tez.am.resource.memory.mb' already exists in tez-interactive-site from > Ambari-2.4 onwards and recently its default value had been changed to > 'SET_ON_FIRST_INVOCATION' in its hive-interacive-site. > - 'hive.tez.container.size' was inherited and used from Hive1/hive-site in > Ambari 2.4. Starting from Ambari 2.5, it was added as a config explicitly in > hive-interactive-site with a default value of 'SET_ON_FIRST_INVOCATION'. > The non-standard 'SET_ON_FIRST_INVOCATION' was introduced, so as to give a > hint in Stack Advisor (SA) call for the 1st time on Hive Server Interactive > ON (enable_hive_interactive config), so that config values for both can be > calculated and set for the 1st time. Subsequesnt calls in the lifecycle, will > just read the value set by SA or if later changed by user manually. > *Problem :* > 'SET_ON_FIRST_INVOCATION', being non-standard was breaking the code in > upgrade scenario. > *Fix:* > Removing the use of 'SET_ON_FIRST_INVOCATION' and adding code for correct > behavior of configs during HDP upgrade. > > *Possible scenarios:* > *1. Ambari upgrade from 2.4 - > 2.5 having HDP 2.5. Implying > 2.5/stack_advisor.py code would have been updated with new LLAP GA logic.* >- 'tez.am.resource.memory.mb' will already be there whether Hive Server > Interactive (HSI) is ON or OFF after Ambari upgrade. > - If HSI if OFF before the upgrade was done, nothing to do over there. > - If HSI on ON before AMbari upgrade, or is made ON after Ambari > upgrade, SA logic has been updated to take of reading > 'hive.tez.container.size' from hive-site as it wont exist in > hive-interactive-site at this point. It will show up in hive-interative-site > aftre the HDP upgrade to 2.6 > *2. Ambari 2.4 having HDP 2.5 -> Upgrade to Ambari 2.5 -> Upgraded to HDP 2.6* >- 'tez.am.resource.memory.mb' will already be there >- As part of HDP 2.5 upgrade to HDP 2.6, 'hive.tez.container.size' would > have got added, having current value picked from > hive-site/hive.tez.container.size. SA code carries a calculation logic for > config 'hive.tez.container.size', which is bound to yield different value > compared to hive-site/'hive.tez.container.size'. The config's value will get > updated/caluclated (1). when HSI is made ON (meaning > 'enabled_hive_interactive' config detected as **True** in > changed-configurations). > > *3. Ambari 2.5 with HDP 2.5 -> Upgraded to HDP 2.6* >- Both 'hive.tez.container.size' and 'tez.am.resource.memory.mb' (alreday > present at HDP 2.5 in hive-interactive-site) will exist after the HDP upgrade. > *Note* that a fresh value for 'hive.tez.container.size' and > 'tez.am.resource.memory.mb' is caluclated at below conditions: > (1). when HSI is made ON, meaning 'enabled_hive_interactive' config detected > as **True** in changed-configurations, or > (2). it's a cluster create operation, where HSI also is supposed to be > started. (BP scenario) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20225) Take care of hive-interactive-site's 'hive.tez.container.size' config during HDP upgrade from 2.5 to 2.6 and update default value for tez-interactive-site's config 'tez
[ https://issues.apache.org/jira/browse/AMBARI-20225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20225: - Attachment: AMBARI-20225.patch > Take care of hive-interactive-site's 'hive.tez.container.size' config during > HDP upgrade from 2.5 to 2.6 and update default value for > tez-interactive-site's config 'tez.am.resource.memory.mb'. > > > Key: AMBARI-20225 > URL: https://issues.apache.org/jira/browse/AMBARI-20225 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-20225.patch > > > *Background :* > We are dealing with 2 specific configs here. > *(1).* 'tez.am.resource.memory.mb' for tez-interactive-site and > *(2).* 'hive.tez.container.size' for hive-interactive-site. > - 'tez.am.resource.memory.mb' already exists in tez-interactive-site from > Ambari-2.4 onwards and recently its default value had been changed to > 'SET_ON_FIRST_INVOCATION' in its hive-interacive-site. > - 'hive.tez.container.size' was inherited and used from Hive1/hive-site in > Ambari 2.4. Starting from Ambari 2.5, it was added as a config explicitly in > hive-interactive-site with a default value of 'SET_ON_FIRST_INVOCATION'. > The non-standard 'SET_ON_FIRST_INVOCATION' was introduced, so as to give a > hint in Stack Advisor (SA) call for the 1st time on Hive Server Interactive > ON (enable_hive_interactive config), so that config values for both can be > calculated and set for the 1st time. Subsequesnt calls in the lifecycle, will > just read the value set by SA or if later changed by user manually. > *Problem :* > 'SET_ON_FIRST_INVOCATION', being non-standard was breaking the code in > upgrade scenario. > *Fix:* > Removing the use of 'SET_ON_FIRST_INVOCATION' and adding code for correct > behavior of configs during HDP upgrade. > > *Possible scenarios:* > *1. Ambari upgrade from 2.4 - > 2.5 having HDP 2.5. Implying > 2.5/stack_advisor.py code would have been updated with new LLAP GA logic.* >- 'tez.am.resource.memory.mb' will already be there whether Hive Server > Interactive (HSI) is ON or OFF after Ambari upgrade. > - If HSI if OFF before the upgrade was done, nothing to do over there. > - If HSI on ON before AMbari upgrade, or is made ON after Ambari > upgrade, SA logic has been updated to take of reading > 'hive.tez.container.size' from hive-site as it wont exist in > hive-interactive-site at this point. It will show up in hive-interative-site > aftre the HDP upgrade to 2.6 > *2. Ambari 2.4 having HDP 2.5 -> Upgrade to Ambari 2.5 -> Upgraded to HDP 2.6* >- 'tez.am.resource.memory.mb' will already be there >- As part of HDP 2.5 upgrade to HDP 2.6, 'hive.tez.container.size' would > have got added, having current value picked from > hive-site/hive.tez.container.size. SA code carries a calculation logic for > config 'hive.tez.container.size', which is bound to yield different value > compared to hive-site/'hive.tez.container.size'. The config's value will get > updated/caluclated (1). when HSI is made ON (meaning > 'enabled_hive_interactive' config detected as **True** in > changed-configurations). > > *3. Ambari 2.5 with HDP 2.5 -> Upgraded to HDP 2.6* >- Both 'hive.tez.container.size' and 'tez.am.resource.memory.mb' (alreday > present at HDP 2.5 in hive-interactive-site) will exist after the HDP upgrade. > *Note* that a fresh value for 'hive.tez.container.size' and > 'tez.am.resource.memory.mb' is caluclated at below conditions: > (1). when HSI is made ON, meaning 'enabled_hive_interactive' config detected > as **True** in changed-configurations, or > (2). it's a cluster create operation, where HSI also is supposed to be > started. (BP scenario) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20225) Take care of hive-interactive-site's 'hive.tez.container.size' config during HDP upgrade from 2.5 to 2.6 and update default value for tez-interactive-site's config 'tez
[ https://issues.apache.org/jira/browse/AMBARI-20225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20225: - Fix Version/s: trunk Status: Patch Available (was: Open) > Take care of hive-interactive-site's 'hive.tez.container.size' config during > HDP upgrade from 2.5 to 2.6 and update default value for > tez-interactive-site's config 'tez.am.resource.memory.mb'. > > > Key: AMBARI-20225 > URL: https://issues.apache.org/jira/browse/AMBARI-20225 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-20225.patch > > > *Background :* > We are dealing with 2 specific configs here. > *(1).* 'tez.am.resource.memory.mb' for tez-interactive-site and > *(2).* 'hive.tez.container.size' for hive-interactive-site. > - 'tez.am.resource.memory.mb' already exists in tez-interactive-site from > Ambari-2.4 onwards and recently its default value had been changed to > 'SET_ON_FIRST_INVOCATION' in its hive-interacive-site. > - 'hive.tez.container.size' was inherited and used from Hive1/hive-site in > Ambari 2.4. Starting from Ambari 2.5, it was added as a config explicitly in > hive-interactive-site with a default value of 'SET_ON_FIRST_INVOCATION'. > The non-standard 'SET_ON_FIRST_INVOCATION' was introduced, so as to give a > hint in Stack Advisor (SA) call for the 1st time on Hive Server Interactive > ON (enable_hive_interactive config), so that config values for both can be > calculated and set for the 1st time. Subsequesnt calls in the lifecycle, will > just read the value set by SA or if later changed by user manually. > *Problem :* > 'SET_ON_FIRST_INVOCATION', being non-standard was breaking the code in > upgrade scenario. > *Fix:* > Removing the use of 'SET_ON_FIRST_INVOCATION' and adding code for correct > behavior of configs during HDP upgrade. > > *Possible scenarios:* > *1. Ambari upgrade from 2.4 - > 2.5 having HDP 2.5. Implying > 2.5/stack_advisor.py code would have been updated with new LLAP GA logic.* >- 'tez.am.resource.memory.mb' will already be there whether Hive Server > Interactive (HSI) is ON or OFF after Ambari upgrade. > - If HSI if OFF before the upgrade was done, nothing to do over there. > - If HSI on ON before AMbari upgrade, or is made ON after Ambari > upgrade, SA logic has been updated to take of reading > 'hive.tez.container.size' from hive-site as it wont exist in > hive-interactive-site at this point. It will show up in hive-interative-site > aftre the HDP upgrade to 2.6 > *2. Ambari 2.4 having HDP 2.5 -> Upgrade to Ambari 2.5 -> Upgraded to HDP 2.6* >- 'tez.am.resource.memory.mb' will already be there >- As part of HDP 2.5 upgrade to HDP 2.6, 'hive.tez.container.size' would > have got added, having current value picked from > hive-site/hive.tez.container.size. SA code carries a calculation logic for > config 'hive.tez.container.size', which is bound to yield different value > compared to hive-site/'hive.tez.container.size'. The config's value will get > updated/caluclated (1). when HSI is made ON (meaning > 'enabled_hive_interactive' config detected as **True** in > changed-configurations). > > *3. Ambari 2.5 with HDP 2.5 -> Upgraded to HDP 2.6* >- Both 'hive.tez.container.size' and 'tez.am.resource.memory.mb' (alreday > present at HDP 2.5 in hive-interactive-site) will exist after the HDP upgrade. > *Note* that a fresh value for 'hive.tez.container.size' and > 'tez.am.resource.memory.mb' is caluclated at below conditions: > (1). when HSI is made ON, meaning 'enabled_hive_interactive' config detected > as **True** in changed-configurations, or > (2). it's a cluster create operation, where HSI also is supposed to be > started. (BP scenario) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20225) Take care of hive-interactive-site's 'hive.tez.container.size' config during HDP upgrade from 2.5 to 2.6 and update default value for tez-interactive-site's config 'tez
[ https://issues.apache.org/jira/browse/AMBARI-20225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20225: - Summary: Take care of hive-interactive-site's 'hive.tez.container.size' config during HDP upgrade from 2.5 to 2.6 and update default value for tez-interactive-site's config 'tez.am.resource.memory.mb'. (was: Take care of Hive2's 'hive.tez.container.size' config during HDP upgrade from 2.5 to 2.6) > Take care of hive-interactive-site's 'hive.tez.container.size' config during > HDP upgrade from 2.5 to 2.6 and update default value for > tez-interactive-site's config 'tez.am.resource.memory.mb'. > > > Key: AMBARI-20225 > URL: https://issues.apache.org/jira/browse/AMBARI-20225 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.5.0 > > > *Background :* > We are dealing with 2 specific configs here. > *(1).* 'tez.am.resource.memory.mb' for tez-interactive-site and > *(2).* 'hive.tez.container.size' for hive-interactive-site. > - 'tez.am.resource.memory.mb' already exists in tez-interactive-site from > Ambari-2.4 onwards and recently its default value had been changed to > 'SET_ON_FIRST_INVOCATION' in its hive-interacive-site. > - 'hive.tez.container.size' was inherited and used from Hive1/hive-site in > Ambari 2.4. Starting from Ambari 2.5, it was added as a config explicitly in > hive-interactive-site with a default value of 'SET_ON_FIRST_INVOCATION'. > The non-standard 'SET_ON_FIRST_INVOCATION' was introduced, so as to give a > hint in Stack Advisor (SA) call for the 1st time on Hive Server Interactive > ON (enable_hive_interactive config), so that config values for both can be > calculated and set for the 1st time. Subsequesnt calls in the lifecycle, will > just read the value set by SA or if later changed by user manually. > *Problem :* > 'SET_ON_FIRST_INVOCATION', being non-standard was breaking the code in > upgrade scenario. > *Fix:* > Removing the use of 'SET_ON_FIRST_INVOCATION' and adding code for correct > behavior of configs during HDP upgrade. > > *Possible scenarios:* > *1. Ambari upgrade from 2.4 - > 2.5 having HDP 2.5. Implying > 2.5/stack_advisor.py code would have been updated with new LLAP GA logic.* >- 'tez.am.resource.memory.mb' will already be there whether Hive Server > Interactive (HSI) is ON or OFF after Ambari upgrade. > - If HSI if OFF before the upgrade was done, nothing to do over there. > - If HSI on ON before AMbari upgrade, or is made ON after Ambari > upgrade, SA logic has been updated to take of reading > 'hive.tez.container.size' from hive-site as it wont exist in > hive-interactive-site at this point. It will show up in hive-interative-site > aftre the HDP upgrade to 2.6 > *2. Ambari 2.4 having HDP 2.5 -> Upgrade to Ambari 2.5 -> Upgraded to HDP 2.6* >- 'tez.am.resource.memory.mb' will already be there >- As part of HDP 2.5 upgrade to HDP 2.6, 'hive.tez.container.size' would > have got added, having current value picked from > hive-site/hive.tez.container.size. SA code carries a calculation logic for > config 'hive.tez.container.size', which is bound to yield different value > compared to hive-site/'hive.tez.container.size'. The config's value will get > updated/caluclated (1). when HSI is made ON (meaning > 'enabled_hive_interactive' config detected as **True** in > changed-configurations). > > *3. Ambari 2.5 with HDP 2.5 -> Upgraded to HDP 2.6* >- Both 'hive.tez.container.size' and 'tez.am.resource.memory.mb' (alreday > present at HDP 2.5 in hive-interactive-site) will exist after the HDP upgrade. > *Note* that a fresh value for 'hive.tez.container.size' and > 'tez.am.resource.memory.mb' is caluclated at below conditions: > (1). when HSI is made ON, meaning 'enabled_hive_interactive' config detected > as **True** in changed-configurations, or > (2). it's a cluster create operation, where HSI also is supposed to be > started. (BP scenario) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20225) Take care of Hive2's 'hive.tez.container.size' config during HDP upgrade from 2.5 to 2.6
[ https://issues.apache.org/jira/browse/AMBARI-20225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20225: - Description: *Background :* We are dealing with 2 specific configs here. *(1).* 'tez.am.resource.memory.mb' for tez-interactive-site and *(2).* 'hive.tez.container.size' for hive-interactive-site. - 'tez.am.resource.memory.mb' already exists in tez-interactive-site from Ambari-2.4 onwards and recently its default value had been changed to 'SET_ON_FIRST_INVOCATION' in its hive-interacive-site. - 'hive.tez.container.size' was inherited and used from Hive1/hive-site in Ambari 2.4. Starting from Ambari 2.5, it was added as a config explicitly in hive-interactive-site with a default value of 'SET_ON_FIRST_INVOCATION'. The non-standard 'SET_ON_FIRST_INVOCATION' was introduced, so as to give a hint in Stack Advisor (SA) call for the 1st time on Hive Server Interactive ON (enable_hive_interactive config), so that config values for both can be calculated and set for the 1st time. Subsequesnt calls in the lifecycle, will just read the value set by SA or if later changed by user manually. *Problem :* 'SET_ON_FIRST_INVOCATION', being non-standard was breaking the code in upgrade scenario. *Fix:* Removing the use of 'SET_ON_FIRST_INVOCATION' and adding code for correct behavior of configs during HDP upgrade. *Possible scenarios:* *1. Ambari upgrade from 2.4 - > 2.5 having HDP 2.5. Implying 2.5/stack_advisor.py code would have been updated with new LLAP GA logic.* - 'tez.am.resource.memory.mb' will already be there whether Hive Server Interactive (HSI) is ON or OFF after Ambari upgrade. - If HSI if OFF before the upgrade was done, nothing to do over there. - If HSI on ON before AMbari upgrade, or is made ON after Ambari upgrade, SA logic has been updated to take of reading 'hive.tez.container.size' from hive-site as it wont exist in hive-interactive-site at this point. It will show up in hive-interative-site aftre the HDP upgrade to 2.6 *2. Ambari 2.4 having HDP 2.5 -> Upgrade to Ambari 2.5 -> Upgraded to HDP 2.6* - 'tez.am.resource.memory.mb' will already be there - As part of HDP 2.5 upgrade to HDP 2.6, 'hive.tez.container.size' would have got added, having current value picked from hive-site/hive.tez.container.size. SA code carries a calculation logic for config 'hive.tez.container.size', which is bound to yield different value compared to hive-site/'hive.tez.container.size'. The config's value will get updated/caluclated (1). when HSI is made ON (meaning 'enabled_hive_interactive' config detected as **True** in changed-configurations). *3. Ambari 2.5 with HDP 2.5 -> Upgraded to HDP 2.6* - Both 'hive.tez.container.size' and 'tez.am.resource.memory.mb' (alreday present at HDP 2.5 in hive-interactive-site) will exist after the HDP upgrade. *Note* that a fresh value for 'hive.tez.container.size' and 'tez.am.resource.memory.mb' is caluclated at below conditions: (1). when HSI is made ON, meaning 'enabled_hive_interactive' config detected as **True** in changed-configurations, or (2). it's a cluster create operation, where HSI also is supposed to be started. (BP scenario) was: *Background :* We are dealing with 2 specific configs here. *(1).* 'tez.am.resource.memory.mb' for tez-interactive-site and *(2).* 'hive.tez.container.size' for hive-interactive-site. - 'tez.am.resource.memory.mb' already exists in tez-interactive-site from Ambari-2.4 onwards and recently its default value had been changed to 'SET_ON_FIRST_INVOCATION' in its hive-interacive-site. - 'hive.tez.container.size' was inherited and used from Hive1/hive-site in Ambari 2.4. Starting from Ambari 2.5, it was added as a config explicitly in hive-interactive-site with a default value of 'SET_ON_FIRST_INVOCATION'. The non-standard 'SET_ON_FIRST_INVOCATION' was introduced, so as to give a hint in Stack Advisor (SA) call for the 1st time on Hive Server Interactive ON (enable_hive_interactive config), so that config values for both can be calculated and set for the 1st time. Subsequesnt calls in the lifecycle, will just read the value set by SA or if later changed by user manually. *Problem :* 'SET_ON_FIRST_INVOCATION', being non-standard was breaking the code in upgrade scenario. *Fix:* Removing the use of 'SET_ON_FIRST_INVOCATION' and adding code for correct behavior of configs during HDP upgrade. *Possible scenarios:* *1. Ambari upgrade from 2.4 - > 2.5 having HDP 2.5. Implying 2.5/stack_advisor.py code would have been updated with new LLAP GA logic.* - 'tez.am.resource.memory.mb' will already be there whether Hive Server Interactive (HSI) is ON or OFF after Ambari upgrade. - If HSI if OFF before the upgrade was done, nothing to do over there. - If HSI on ON before AMbari upgrade, or is made ON after Ambari upgrade, SA logic has been upd
[jira] [Updated] (AMBARI-20225) Take care of Hive2's 'hive.tez.container.size' config during HDP upgrade from 2.5 to 2.6
[ https://issues.apache.org/jira/browse/AMBARI-20225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20225: - Description: *Background :* We are dealing with 2 specific configs here. *(1).* 'tez.am.resource.memory.mb' for tez-interactive-site and *(2).* 'hive.tez.container.size' for hive-interactive-site. - 'tez.am.resource.memory.mb' already exists in tez-interactive-site from Ambari-2.4 onwards and recently its default value had been changed to 'SET_ON_FIRST_INVOCATION' in its hive-interacive-site. - 'hive.tez.container.size' was inherited and used from Hive1/hive-site in Ambari 2.4. Starting from Ambari 2.5, it was added as a config explicitly in hive-interactive-site with a default value of 'SET_ON_FIRST_INVOCATION'. The non-standard 'SET_ON_FIRST_INVOCATION' was introduced, so as to give a hint in Stack Advisor (SA) call for the 1st time on Hive Server Interactive ON (enable_hive_interactive config), so that config values for both can be calculated and set for the 1st time. Subsequesnt calls in the lifecycle, will just read the value set by SA or if later changed by user manually. *Problem :* 'SET_ON_FIRST_INVOCATION', being non-standard was breaking the code in upgrade scenario. *Fix:* Removing the use of 'SET_ON_FIRST_INVOCATION' and adding code for correct behavior of configs during HDP upgrade. *Possible scenarios:* *1. Ambari upgrade from 2.4 - > 2.5 having HDP 2.5. Implying 2.5/stack_advisor.py code would have been updated with new LLAP GA logic.* - 'tez.am.resource.memory.mb' will already be there whether Hive Server Interactive (HSI) is ON or OFF after Ambari upgrade. - If HSI if OFF before the upgrade was done, nothing to do over there. - If HSI on ON before AMbari upgrade, or is made ON after Ambari upgrade, SA logic has been updated to take of reading 'hive.tez.container.size' from hive-site as it wont exist in hive-interactive-site at this point. It will show up in hive-interative-site aftre the HDP upgrade to 2.6 *2. Ambari 2.4 having HDP 2.5 -> Upgrade to Ambari 2.5 -> Upgraded to HDP 2.6* - 'tez.am.resource.memory.mb' will already be there - As part of HDP 2.5 upgrade to HDP 2.6, 'hive.tez.container.size' would have got added, having current value picked from hive-site/hive.tez.container.size. SA code carries a calculation logic for config 'hive.tez.container.size', which is bound to yield different value compared to hive-site/'hive.tez.container.size'. The config's value will get updated/caluclated (1). when HSI is made ON (meaning 'enabled_hive_interactive' config detected as **True** in changed-configurations). *3. Ambari 2.5 with HDP 2.5 -> Upgraded to HDP 2.6* - Both 'hive.tez.container.size' and 'tez.am.resource.memory.mb' (alreday present at HDP 2.5 in hive-interactive-site) will exist after the HDP upgrade. **Note** that a fresh value for 'hive.tez.container.size' and 'tez.am.resource.memory.mb' is caluclated at below conditions: (1). when HSI is made ON, meaning 'enabled_hive_interactive' config detected as **True** in changed-configurations, or (2). it's a cluster create operation, where HSI also is supposed to be started. (BP scenario) was: *Background :** We are dealing with 2 specific configs here. *(1).* 'tez.am.resource.memory.mb' for tez-interactive-site and *(2).* 'hive.tez.container.size' for hive-interactive-site. - 'tez.am.resource.memory.mb' already exists in tez-interactive-site from Ambari-2.4 onwards and recently its default value had been changed to 'SET_ON_FIRST_INVOCATION' in its hive-interacive-site. - 'hive.tez.container.size' was inherited and used from Hive1/hive-site in Ambari 2.4. Starting from Ambari 2.5, it was added as a config explicitly in hive-interactive-site with a default value of 'SET_ON_FIRST_INVOCATION'. The non-standard 'SET_ON_FIRST_INVOCATION' was introduced, so as to give a hint in Stack Advisor (SA) call for the 1st time on Hive Server Interactive ON (enable_hive_interactive config), so that config values for both can be calculated and set for the 1st time. Subsequesnt calls in the lifecycle, will just read the value set by SA or if later changed by user manually. **Problem :** **-** 'SET_ON_FIRST_INVOCATION', being non-standard was breaking the code in upgrade scenario. **Fix:** **** Removing the use of 'SET_ON_FIRST_INVOCATION' and adding code for correct behavior of configs during HDP upgrade. **Possible scenarios:** **--** **1. Ambari upgrade from 2.4 - > 2.5 having HDP 2.5. Implying 2.5/stack_advisor.py code would have been updated with new LLAP GA logic.** - 'tez.am.resource.memory.mb' will already be there whether Hive Server Interactive (HSI) is ON or OFF after Ambari upgrade. - If HSI if OFF before the upgrade was done, nothing to do over there. - If HSI on ON before AMbari upgrade,
[jira] [Updated] (AMBARI-20225) Take care of Hive2's 'hive.tez.container.size' config during HDP upgrade from 2.5 to 2.6
[ https://issues.apache.org/jira/browse/AMBARI-20225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20225: - Description: *Background :** We are dealing with 2 specific configs here. *(1).* 'tez.am.resource.memory.mb' for tez-interactive-site and *(2).* 'hive.tez.container.size' for hive-interactive-site. - 'tez.am.resource.memory.mb' already exists in tez-interactive-site from Ambari-2.4 onwards and recently its default value had been changed to 'SET_ON_FIRST_INVOCATION' in its hive-interacive-site. - 'hive.tez.container.size' was inherited and used from Hive1/hive-site in Ambari 2.4. Starting from Ambari 2.5, it was added as a config explicitly in hive-interactive-site with a default value of 'SET_ON_FIRST_INVOCATION'. The non-standard 'SET_ON_FIRST_INVOCATION' was introduced, so as to give a hint in Stack Advisor (SA) call for the 1st time on Hive Server Interactive ON (enable_hive_interactive config), so that config values for both can be calculated and set for the 1st time. Subsequesnt calls in the lifecycle, will just read the value set by SA or if later changed by user manually. **Problem :** **-** 'SET_ON_FIRST_INVOCATION', being non-standard was breaking the code in upgrade scenario. **Fix:** **** Removing the use of 'SET_ON_FIRST_INVOCATION' and adding code for correct behavior of configs during HDP upgrade. **Possible scenarios:** **--** **1. Ambari upgrade from 2.4 - > 2.5 having HDP 2.5. Implying 2.5/stack_advisor.py code would have been updated with new LLAP GA logic.** - 'tez.am.resource.memory.mb' will already be there whether Hive Server Interactive (HSI) is ON or OFF after Ambari upgrade. - If HSI if OFF before the upgrade was done, nothing to do over there. - If HSI on ON before AMbari upgrade, or is made ON after Ambari upgrade, SA logic has been updated to take of reading 'hive.tez.container.size' from hive-site as it wont exist in hive-interactive-site at this point. It will show up in hive-interative-site aftre the HDP upgrade to 2.6 **2. Ambari 2.4 having HDP 2.5 -> Upgrade to Ambari 2.5 -> Upgraded to HDP 2.6** - 'tez.am.resource.memory.mb' will already be there - As part of HDP 2.5 upgrade to HDP 2.6, 'hive.tez.container.size' would have got added, having current value picked from hive-site/hive.tez.container.size. SA code carries a calculation logic for config 'hive.tez.container.size', which is bound to yield different value compared to hive-site/'hive.tez.container.size'. The config's value will get updated/caluclated (1). when HSI is made ON (meaning 'enabled_hive_interactive' config detected as **True** in changed-configurations). **3. Ambari 2.5 with HDP 2.5 -> Upgraded to HDP 2.6** - Both 'hive.tez.container.size' and 'tez.am.resource.memory.mb' (alreday present at HDP 2.5 in hive-interactive-site) will exist after the HDP upgrade. **Note** that a fresh value for 'hive.tez.container.size' and 'tez.am.resource.memory.mb' is caluclated at below conditions: (1). when HSI is made ON, meaning 'enabled_hive_interactive' config detected as **True** in changed-configurations, or (2). it's a cluster create operation, where HSI also is supposed to be started. (BP scenario) was: **Background :** **--** We are dealing with 2 specific configs here. **(1).** 'tez.am.resource.memory.mb' for tez-interactive-site and **(2).** 'hive.tez.container.size' for hive-interactive-site. - 'tez.am.resource.memory.mb' already exists in tez-interactive-site from Ambari-2.4 onwards and recently its default value had been changed to 'SET_ON_FIRST_INVOCATION' in its hive-interacive-site. - 'hive.tez.container.size' was inherited and used from Hive1/hive-site in Ambari 2.4. Starting from Ambari 2.5, it was added as a config explicitly in hive-interactive-site with a default value of 'SET_ON_FIRST_INVOCATION'. The non-standard 'SET_ON_FIRST_INVOCATION' was introduced, so as to give a hint in Stack Advisor (SA) call for the 1st time on Hive Server Interactive ON (enable_hive_interactive config), so that config values for both can be calculated and set for the 1st time. Subsequesnt calls in the lifecycle, will just read the value set by SA or if later changed by user manually. **Problem :** **-** 'SET_ON_FIRST_INVOCATION', being non-standard was breaking the code in upgrade scenario. **Fix:** **** Removing the use of 'SET_ON_FIRST_INVOCATION' and adding code for correct behavior of configs during HDP upgrade. **Possible scenarios:** **--** **1. Ambari upgrade from 2.4 - > 2.5 having HDP 2.5. Implying 2.5/stack_advisor.py code would have been updated with new LLAP GA logic.** - 'tez.am.resource.memory.mb' will already be there whether Hive Server Interactive (HSI) is ON or OFF after Ambari upgrade. - If HSI if OFF before the upgrade
[jira] [Updated] (AMBARI-20225) Take care of Hive2's 'hive.tez.container.size' config during HDP upgrade from 2.5 to 2.6
[ https://issues.apache.org/jira/browse/AMBARI-20225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20225: - Description: **Background :** **--** We are dealing with 2 specific configs here. **(1).** 'tez.am.resource.memory.mb' for tez-interactive-site and **(2).** 'hive.tez.container.size' for hive-interactive-site. - 'tez.am.resource.memory.mb' already exists in tez-interactive-site from Ambari-2.4 onwards and recently its default value had been changed to 'SET_ON_FIRST_INVOCATION' in its hive-interacive-site. - 'hive.tez.container.size' was inherited and used from Hive1/hive-site in Ambari 2.4. Starting from Ambari 2.5, it was added as a config explicitly in hive-interactive-site with a default value of 'SET_ON_FIRST_INVOCATION'. The non-standard 'SET_ON_FIRST_INVOCATION' was introduced, so as to give a hint in Stack Advisor (SA) call for the 1st time on Hive Server Interactive ON (enable_hive_interactive config), so that config values for both can be calculated and set for the 1st time. Subsequesnt calls in the lifecycle, will just read the value set by SA or if later changed by user manually. **Problem :** **-** 'SET_ON_FIRST_INVOCATION', being non-standard was breaking the code in upgrade scenario. **Fix:** **** Removing the use of 'SET_ON_FIRST_INVOCATION' and adding code for correct behavior of configs during HDP upgrade. **Possible scenarios:** **--** **1. Ambari upgrade from 2.4 - > 2.5 having HDP 2.5. Implying 2.5/stack_advisor.py code would have been updated with new LLAP GA logic.** - 'tez.am.resource.memory.mb' will already be there whether Hive Server Interactive (HSI) is ON or OFF after Ambari upgrade. - If HSI if OFF before the upgrade was done, nothing to do over there. - If HSI on ON before AMbari upgrade, or is made ON after Ambari upgrade, SA logic has been updated to take of reading 'hive.tez.container.size' from hive-site as it wont exist in hive-interactive-site at this point. It will show up in hive-interative-site aftre the HDP upgrade to 2.6 **2. Ambari 2.4 having HDP 2.5 -> Upgrade to Ambari 2.5 -> Upgraded to HDP 2.6** - 'tez.am.resource.memory.mb' will already be there - As part of HDP 2.5 upgrade to HDP 2.6, 'hive.tez.container.size' would have got added, having current value picked from hive-site/hive.tez.container.size. SA code carries a calculation logic for config 'hive.tez.container.size', which is bound to yield different value compared to hive-site/'hive.tez.container.size'. The config's value will get updated/caluclated (1). when HSI is made ON (meaning 'enabled_hive_interactive' config detected as **True** in changed-configurations). **3. Ambari 2.5 with HDP 2.5 -> Upgraded to HDP 2.6** - Both 'hive.tez.container.size' and 'tez.am.resource.memory.mb' (alreday present at HDP 2.5 in hive-interactive-site) will exist after the HDP upgrade. **Note** that a fresh value for 'hive.tez.container.size' and 'tez.am.resource.memory.mb' is caluclated at below conditions: (1). when HSI is made ON, meaning 'enabled_hive_interactive' config detected as **True** in changed-configurations, or (2). it's a cluster create operation, where HSI also is supposed to be started. (BP scenario) > Take care of Hive2's 'hive.tez.container.size' config during HDP upgrade from > 2.5 to 2.6 > > > Key: AMBARI-20225 > URL: https://issues.apache.org/jira/browse/AMBARI-20225 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.5.0 > > > **Background :** > **--** > We are dealing with 2 specific configs here. > **(1).** 'tez.am.resource.memory.mb' for tez-interactive-site and > **(2).** 'hive.tez.container.size' for hive-interactive-site. > - 'tez.am.resource.memory.mb' already exists in tez-interactive-site from > Ambari-2.4 onwards and recently its default value had been changed to > 'SET_ON_FIRST_INVOCATION' in its hive-interacive-site. > - 'hive.tez.container.size' was inherited and used from Hive1/hive-site in > Ambari 2.4. Starting from Ambari 2.5, it was added as a config explicitly in > hive-interactive-site with a default value of 'SET_ON_FIRST_INVOCATION'. > The non-standard 'SET_ON_FIRST_INVOCATION' was introduced, so as to give a > hint in Stack Advisor (SA) call for the 1st time on Hive Server Interactive > ON (enable_hive_interactive config), so that config values for both can be > calculated and set for the 1st time. Subsequesnt calls in the lifecycle, will > just read the value set by SA or if later changed by user manually. > **Problem :** > **-** > 'SET_ON_
[jira] [Commented] (AMBARI-20243) Include option to filter out properties from APi that returns ambari.properties file
[
https://issues.apache.org/jira/browse/AMBARI-20243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888980#comment-15888980
]
Hadoop QA commented on AMBARI-20243:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12855217/AMBARI-20243.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 1 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:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10809//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10809//console
This message is automatically generated.
> Include option to filter out properties from APi that returns
> ambari.properties file
>
>
> Key: AMBARI-20243
> URL: https://issues.apache.org/jira/browse/AMBARI-20243
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: trunk
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
> Fix For: trunk
>
> Attachments: AMBARI-20243.patch
>
>
> Currently all the details from the ambari.properties file is being returned
> by the API call.
> Some of those information may not be utilized and hence an option can be
> provided to filter the properties.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20033) Typecasting to 'long' from earlier 'float', before setting them the following configs for recommendation : (1). 'llap_concurrency', (2). 'llap_concurrency' max value an
[ https://issues.apache.org/jira/browse/AMBARI-20033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20033: - Resolution: Fixed Status: Resolved (was: Patch Available) > Typecasting to 'long' from earlier 'float', before setting them the following > configs for recommendation : (1). 'llap_concurrency', (2). 'llap_concurrency' > max value and (3). 'hive.llap.daemon.num.executors' max value. > -- > > Key: AMBARI-20033 > URL: https://issues.apache.org/jira/browse/AMBARI-20033 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-20033.patch, AMBARI-20033.trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20194) Enable/Disable UI objects related to managing alert targets based on user's privileges
[ https://issues.apache.org/jira/browse/AMBARI-20194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888926#comment-15888926 ] Hudson commented on AMBARI-20194: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1131 (See [https://builds.apache.org/job/Ambari-branch-2.5/1131/]) AMBARI-20194 - Enable/Disable UI objects related to managing alert (rzang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b53fc82a7184fb8b54c290b523f9146c19227a87]) * (edit) ambari-web/app/app.js * (edit) ambari-web/app/templates/main/alerts/manage_alert_notifications_popup.hbs * (edit) ambari-web/app/views/main/alerts/manage_alert_notifications_view.js * (edit) ambari-web/test/views/main/alerts/manage_alert_notifications_view_test.js * (edit) ambari-web/app/controllers/main/alerts/alert_definitions_actions_controller.js > Enable/Disable UI objects related to managing alert targets based on user's > privileges > -- > > Key: AMBARI-20194 > URL: https://issues.apache.org/jira/browse/AMBARI-20194 > 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-20194.patch > > > UI objects related to managing alert targets need to be enabled or disabled > based on user's privileges. > The relevant privilege name is CLUSTER.MANAGE_ALERT_NOTIFICATIONS. If this > exists in the users's set of privileges, the user should be able to manage > alert targets and relevant details. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20194) Enable/Disable UI objects related to managing alert targets based on user's privileges
[ https://issues.apache.org/jira/browse/AMBARI-20194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888914#comment-15888914 ] Hudson commented on AMBARI-20194: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6890 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6890/]) AMBARI-20194 - Enable/Disable UI objects related to managing alert (rzang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=aa057cb42b08676fac4d4ef75d1b77ad3b6da893]) * (edit) ambari-web/test/views/main/alerts/manage_alert_notifications_view_test.js * (edit) ambari-web/app/views/main/alerts/manage_alert_notifications_view.js * (edit) ambari-web/app/app.js * (edit) ambari-web/app/controllers/main/alerts/alert_definitions_actions_controller.js * (edit) ambari-web/app/templates/main/alerts/manage_alert_notifications_popup.hbs > Enable/Disable UI objects related to managing alert targets based on user's > privileges > -- > > Key: AMBARI-20194 > URL: https://issues.apache.org/jira/browse/AMBARI-20194 > 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-20194.patch > > > UI objects related to managing alert targets need to be enabled or disabled > based on user's privileges. > The relevant privilege name is CLUSTER.MANAGE_ALERT_NOTIFICATIONS. If this > exists in the users's set of privileges, the user should be able to manage > alert targets and relevant details. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20194) Enable/Disable UI objects related to managing alert targets based on user's privileges
[ https://issues.apache.org/jira/browse/AMBARI-20194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20194: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and 2.5 b53fc82a7184fb8b54c290b523f9146c19227a87 > Enable/Disable UI objects related to managing alert targets based on user's > privileges > -- > > Key: AMBARI-20194 > URL: https://issues.apache.org/jira/browse/AMBARI-20194 > 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-20194.patch > > > UI objects related to managing alert targets need to be enabled or disabled > based on user's privileges. > The relevant privilege name is CLUSTER.MANAGE_ALERT_NOTIFICATIONS. If this > exists in the users's set of privileges, the user should be able to manage > alert targets and relevant details. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20221) Ambari db schema update should be able to compare Ambari versions with build text
[ https://issues.apache.org/jira/browse/AMBARI-20221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1564#comment-1564 ] Di Li commented on AMBARI-20221: both failures shown in the integration builds were due to a Kerberos unit test that seemed to have indicated a timeout. This should be unrelated to the changes introduced in this JIRA. > Ambari db schema update should be able to compare Ambari versions with build > text > - > > Key: AMBARI-20221 > URL: https://issues.apache.org/jira/browse/AMBARI-20221 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-20221.patch > > > SchemaUpgradeHelper should be able to handle Ambari with versions like > 1.2.3_mycompany_00 instead of just versions like 1.2.3.4 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20243) Include option to filter out properties from APi that returns ambari.properties file
[ https://issues.apache.org/jira/browse/AMBARI-20243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-20243: -- Status: Patch Available (was: Open) > Include option to filter out properties from APi that returns > ambari.properties file > > > Key: AMBARI-20243 > URL: https://issues.apache.org/jira/browse/AMBARI-20243 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk > > Attachments: AMBARI-20243.patch > > > Currently all the details from the ambari.properties file is being returned > by the API call. > Some of those information may not be utilized and hence an option can be > provided to filter the properties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20243) Include option to filter out properties from APi that returns ambari.properties file
[ https://issues.apache.org/jira/browse/AMBARI-20243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-20243: -- Attachment: AMBARI-20243.patch > Include option to filter out properties from APi that returns > ambari.properties file > > > Key: AMBARI-20243 > URL: https://issues.apache.org/jira/browse/AMBARI-20243 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk > > Attachments: AMBARI-20243.patch > > > Currently all the details from the ambari.properties file is being returned > by the API call. > Some of those information may not be utilized and hence an option can be > provided to filter the properties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20243) Include option to filter out properties from APi that returns ambari.properties file
[ https://issues.apache.org/jira/browse/AMBARI-20243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-20243: -- Status: Open (was: Patch Available) > Include option to filter out properties from APi that returns > ambari.properties file > > > Key: AMBARI-20243 > URL: https://issues.apache.org/jira/browse/AMBARI-20243 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk > > > Currently all the details from the ambari.properties file is being returned > by the API call. > Some of those information may not be utilized and hence an option can be > provided to filter the properties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20243) Include option to filter out properties from APi that returns ambari.properties file
[ https://issues.apache.org/jira/browse/AMBARI-20243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-20243: -- Attachment: (was: AMBARI-20243.patch) > Include option to filter out properties from APi that returns > ambari.properties file > > > Key: AMBARI-20243 > URL: https://issues.apache.org/jira/browse/AMBARI-20243 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk > > > Currently all the details from the ambari.properties file is being returned > by the API call. > Some of those information may not be utilized and hence an option can be > provided to filter the properties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20243) Include option to filter out properties from APi that returns ambari.properties file
[ https://issues.apache.org/jira/browse/AMBARI-20243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-20243: -- Status: Patch Available (was: Open) > Include option to filter out properties from APi that returns > ambari.properties file > > > Key: AMBARI-20243 > URL: https://issues.apache.org/jira/browse/AMBARI-20243 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk > > Attachments: AMBARI-20243.patch > > > Currently all the details from the ambari.properties file is being returned > by the API call. > Some of those information may not be utilized and hence an option can be > provided to filter the properties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20243) Include option to filter out properties from APi that returns ambari.properties file
[ https://issues.apache.org/jira/browse/AMBARI-20243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-20243: -- Attachment: AMBARI-20243.patch > Include option to filter out properties from APi that returns > ambari.properties file > > > Key: AMBARI-20243 > URL: https://issues.apache.org/jira/browse/AMBARI-20243 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk > > Attachments: AMBARI-20243.patch > > > Currently all the details from the ambari.properties file is being returned > by the API call. > Some of those information may not be utilized and hence an option can be > provided to filter the properties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20243) Include option to filter out properties from APi that returns ambari.properties file
[ https://issues.apache.org/jira/browse/AMBARI-20243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-20243: -- Description: Currently all the details from the ambari.properties file is being returned by the API call. Some of those information may not be utilized and hence an option can be provided to filter the properties. > Include option to filter out properties from APi that returns > ambari.properties file > > > Key: AMBARI-20243 > URL: https://issues.apache.org/jira/browse/AMBARI-20243 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk > > > Currently all the details from the ambari.properties file is being returned > by the API call. > Some of those information may not be utilized and hence an option can be > provided to filter the properties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20243) Include option to filter out properties from APi that returns ambari.properties file
Anita Gnanamalar Jebaraj created AMBARI-20243: - Summary: Include option to filter out properties from APi that returns ambari.properties file Key: AMBARI-20243 URL: https://issues.apache.org/jira/browse/AMBARI-20243 Project: Ambari Issue Type: Bug Components: ambari-sever Affects Versions: trunk Reporter: Anita Gnanamalar Jebaraj Assignee: Anita Gnanamalar Jebaraj Fix For: trunk -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20221) Ambari db schema update should be able to compare Ambari versions with build text
[ https://issues.apache.org/jira/browse/AMBARI-20221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1528#comment-1528 ] Hudson commented on AMBARI-20221: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6889 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6889/]) AMBARI-20221 Ambari db schema update should be able to compare Ambari (dili: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=aeb5076ad66692a43af531c7c5377bdb72dc0f37]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/utils/TestVersionUtils.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/utils/VersionUtils.java > Ambari db schema update should be able to compare Ambari versions with build > text > - > > Key: AMBARI-20221 > URL: https://issues.apache.org/jira/browse/AMBARI-20221 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-20221.patch > > > SchemaUpgradeHelper should be able to handle Ambari with versions like > 1.2.3_mycompany_00 instead of just versions like 1.2.3.4 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20221) Ambari db schema update should be able to compare Ambari versions with build text
[ https://issues.apache.org/jira/browse/AMBARI-20221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-20221: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari db schema update should be able to compare Ambari versions with build > text > - > > Key: AMBARI-20221 > URL: https://issues.apache.org/jira/browse/AMBARI-20221 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-20221.patch > > > SchemaUpgradeHelper should be able to handle Ambari with versions like > 1.2.3_mycompany_00 instead of just versions like 1.2.3.4 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20221) Ambari db schema update should be able to compare Ambari versions with build text
[ https://issues.apache.org/jira/browse/AMBARI-20221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888768#comment-15888768 ] Di Li commented on AMBARI-20221: pushed to trunk as https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=aeb5076ad66692a43af531c7c5377bdb72dc0f37 > Ambari db schema update should be able to compare Ambari versions with build > text > - > > Key: AMBARI-20221 > URL: https://issues.apache.org/jira/browse/AMBARI-20221 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-20221.patch > > > SchemaUpgradeHelper should be able to handle Ambari with versions like > 1.2.3_mycompany_00 instead of just versions like 1.2.3.4 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20242) Increase Ranger/Atlas timeout (check znode)
[ https://issues.apache.org/jira/browse/AMBARI-20242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-20242: -- Status: Patch Available (was: Open) > Increase Ranger/Atlas timeout (check znode) > --- > > Key: AMBARI-20242 > URL: https://issues.apache.org/jira/browse/AMBARI-20242 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-20242.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20241) Increase Ranger/Atlas timeout (check znode)
[ https://issues.apache.org/jira/browse/AMBARI-20241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-20241. --- Resolution: Duplicate duplicate of AMBARI-20242 > Increase Ranger/Atlas timeout (check znode) > --- > > Key: AMBARI-20241 > URL: https://issues.apache.org/jira/browse/AMBARI-20241 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20242) Increase Ranger/Atlas timeout (check znode)
[ https://issues.apache.org/jira/browse/AMBARI-20242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-20242: -- Attachment: AMBARI-20242.patch > Increase Ranger/Atlas timeout (check znode) > --- > > Key: AMBARI-20242 > URL: https://issues.apache.org/jira/browse/AMBARI-20242 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-20242.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20242) Increase Ranger/Atlas timeout (check znode)
Olivér Szabó created AMBARI-20242: - Summary: Increase Ranger/Atlas timeout (check znode) Key: AMBARI-20242 URL: https://issues.apache.org/jira/browse/AMBARI-20242 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20241) Increase Ranger/Atlas timeout (check znode)
Olivér Szabó created AMBARI-20241: - Summary: Increase Ranger/Atlas timeout (check znode) Key: AMBARI-20241 URL: https://issues.apache.org/jira/browse/AMBARI-20241 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20240) a running workflow cannot be killed from WFM ui immediately
zhixun he created AMBARI-20240: -- Summary: a running workflow cannot be killed from WFM ui immediately Key: AMBARI-20240 URL: https://issues.apache.org/jira/browse/AMBARI-20240 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: zhixun he Assignee: Padma Priya Nagaraj Priority: Critical Fix For: 2.5.0 Steps: 1. log into ambari ui 2. go to wfm 3. upload workflow from file system: 4. submit the workflow 5. kill or suspend the workflow from WFM ui Issue: workflow ui is not giving any confirmation message when wf is killed or suspended -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20240) a running workflow cannot be killed from WFM ui immediately
[
https://issues.apache.org/jira/browse/AMBARI-20240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhixun he updated AMBARI-20240:
---
Description:
Steps:
1. log into ambari ui
2. go to wfm
3. upload workflow from file system:
https://github.com/hortonworks/certification/blob/pixie-dust/HDPTests/tests/oozie/oozie_1/regression-two/test_WfKillSubwf1/workflow.xml
4. submit the workflow
5. kill the workflow from WFM ui
Error:
workflow ui is still showing running after the kill. Wait 5 min and refresh the
page, we can see it is killed.
if you check the log of wf on ui, it showed it is killed several times{noformat}
2017-02-16 18:25:08,356 INFO DagEngine:520 -
SERVER[bugbash-r7-oozie-tde-we-2-1.openstacklocal] USER[ambari-server-cl1 doAs
admin] GROUP[-] TOKEN[-] APP[-]
JOB[003-170215185313202-oozie-oozi-W] ACTION[] User admin killed the WF job
003-170215185313202-oozie-oozi-W
2017-02-16 18:25:18,534 INFO DagEngine:520 - SERVER[bugbash-r7-oozie-tde-we-2-
1.openstacklocal] USER[ambari-server-cl1 doAs admin] GROUP[-] TOKEN[-] APP[-]
JOB[003-170215185313202-oozie-oozi-W] ACTION[] User admin killed the WF job
003-170215185313202-oozie-oozi-W
2017-02-16 18:25:57,166 INFO DagEngine:520 - SERVER[bugbash-r7-oozie-tde-we-2-
1.openstacklocal] USER[ambari-server-cl1 doAs admin] GROUP[-] TOKEN[-] APP[-]
JOB[003-170215185313202-oozie-oozi-W] ACTION[] User admin killed the WF job
003-170215185313202-oozie-oozi-W
2017-02-16 18:26:02,047 INFO DagEngine:520 - SERVER[bugbash-r7-oozie-tde-we-2-
1.openstacklocal] USER[ambari-server-cl1 doAs admin] GROUP[-] TOKEN[-] APP[-]
JOB[003-170215185313202-oozie-oozi-W] ACTION[] User admin killed the WF job
003-170215185313202-oozie-oozi-W{noformat}
was:
Steps:
1. log into ambari ui
2. go to wfm
3. upload workflow from file system:
4. submit the workflow
5. kill or suspend the workflow from WFM ui
Issue:
workflow ui is not giving any confirmation message when wf is killed or
suspended
> a running workflow cannot be killed from WFM ui immediately
> ---
>
> Key: AMBARI-20240
> URL: https://issues.apache.org/jira/browse/AMBARI-20240
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: zhixun he
>Assignee: Padma Priya Nagaraj
>Priority: Critical
> Labels: WFD, WFM
> Fix For: 2.5.0
>
>
> Steps:
> 1. log into ambari ui
> 2. go to wfm
> 3. upload workflow from file system:
> https://github.com/hortonworks/certification/blob/pixie-dust/HDPTests/tests/oozie/oozie_1/regression-two/test_WfKillSubwf1/workflow.xml
> 4. submit the workflow
> 5. kill the workflow from WFM ui
> Error:
> workflow ui is still showing running after the kill. Wait 5 min and refresh
> the page, we can see it is killed.
> if you check the log of wf on ui, it showed it is killed several
> times{noformat}
> 2017-02-16 18:25:08,356 INFO DagEngine:520 -
> SERVER[bugbash-r7-oozie-tde-we-2-1.openstacklocal] USER[ambari-server-cl1
> doAs admin] GROUP[-] TOKEN[-] APP[-]
> JOB[003-170215185313202-oozie-oozi-W] ACTION[] User admin killed the WF
> job
> 003-170215185313202-oozie-oozi-W
> 2017-02-16 18:25:18,534 INFO DagEngine:520 -
> SERVER[bugbash-r7-oozie-tde-we-2-
> 1.openstacklocal] USER[ambari-server-cl1 doAs admin] GROUP[-] TOKEN[-] APP[-]
> JOB[003-170215185313202-oozie-oozi-W] ACTION[] User admin killed the WF
> job
> 003-170215185313202-oozie-oozi-W
> 2017-02-16 18:25:57,166 INFO DagEngine:520 -
> SERVER[bugbash-r7-oozie-tde-we-2-
> 1.openstacklocal] USER[ambari-server-cl1 doAs admin] GROUP[-] TOKEN[-] APP[-]
> JOB[003-170215185313202-oozie-oozi-W] ACTION[] User admin killed the WF
> job
> 003-170215185313202-oozie-oozi-W
> 2017-02-16 18:26:02,047 INFO DagEngine:520 -
> SERVER[bugbash-r7-oozie-tde-we-2-
> 1.openstacklocal] USER[ambari-server-cl1 doAs admin] GROUP[-] TOKEN[-] APP[-]
> JOB[003-170215185313202-oozie-oozi-W] ACTION[] User admin killed the WF
> job
> 003-170215185313202-oozie-oozi-W{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20238) Add Streamline Stack definition
Sriharsha Chintalapani created AMBARI-20238: --- Summary: Add Streamline Stack definition Key: AMBARI-20238 URL: https://issues.apache.org/jira/browse/AMBARI-20238 Project: Ambari Issue Type: Improvement Reporter: Sriharsha Chintalapani Assignee: Sriharsha Chintalapani Priority: Critical -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20239) Add Registry stack definition
Sriharsha Chintalapani created AMBARI-20239: --- Summary: Add Registry stack definition Key: AMBARI-20239 URL: https://issues.apache.org/jira/browse/AMBARI-20239 Project: Ambari Issue Type: Improvement Reporter: Sriharsha Chintalapani Assignee: Sriharsha Chintalapani Priority: Critical -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20230) Pom.xml change in Workflow manager to fix the version of front end plugin to make it compatible with the maven version used in ambari
[ https://issues.apache.org/jira/browse/AMBARI-20230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888586#comment-15888586 ] Hudson commented on AMBARI-20230: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1130 (See [https://builds.apache.org/job/Ambari-branch-2.5/1130/]) AMBARI-20230. Pom.xml change in Workflow manager to fix the version of (pallavkul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0c9e3a75b54fa73782b34cd6c12cbd69cdb13488]) * (edit) contrib/views/wfmanager/pom.xml > Pom.xml change in Workflow manager to fix the version of front end plugin to > make it compatible with the maven version used in ambari > - > > Key: AMBARI-20230 > URL: https://issues.apache.org/jira/browse/AMBARI-20230 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: venkat >Assignee: venkat > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20230_branch_2.5.patch > > > The version for front end plugin has to be changed to make it compatible with > the maven version used in Amabri -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20237) After regenerate keytabs post Ambari upgrade yarn.nodemanager.linux-container-executor.cgroups.mount-path property got added with blank value
[ https://issues.apache.org/jira/browse/AMBARI-20237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Sharma updated AMBARI-20237: -- Description: STR 1. Deployed cluster with Ambari version: 2.4.1.0-22 and HDP version: 2.5.0.0-1245(secure cluster) 2. Upgrade Ambari to 2.5.0.0 3. Regenerate keytabs for missing hosts and let it complete 4. Go to YARN - configs Result Observed that yarn.nodemanager.linux-container-executor.cgroups.mount-path got added as a property with blank value was: STR 1. Deployed cluster with Ambari version: 2.4.1.0-22 and HDP version: 2.5.0.0-1245(secure cluster) 2. Upgrade Ambari to 2.5.0.0-999 3. Regenerate keytabs for missing hosts and let it complete 4. Go to YARN - configs Result Observed that yarn.nodemanager.linux-container-executor.cgroups.mount-path got added as a property with blank value > After regenerate keytabs post Ambari upgrade > yarn.nodemanager.linux-container-executor.cgroups.mount-path property got > added with blank value > -- > > Key: AMBARI-20237 > URL: https://issues.apache.org/jira/browse/AMBARI-20237 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vivek Sharma >Priority: Critical > Labels: upgrade > Fix For: 2.5.0 > > > STR > 1. Deployed cluster with Ambari version: 2.4.1.0-22 and HDP version: > 2.5.0.0-1245(secure cluster) > 2. Upgrade Ambari to 2.5.0.0 > 3. Regenerate keytabs for missing hosts and let it complete > 4. Go to YARN - configs > Result > Observed that yarn.nodemanager.linux-container-executor.cgroups.mount-path > got added as a property with blank value -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20237) After regenerate keytabs post Ambari upgrade yarn.nodemanager.linux-container-executor.cgroups.mount-path property got added with blank value
Vivek Sharma created AMBARI-20237: - Summary: After regenerate keytabs post Ambari upgrade yarn.nodemanager.linux-container-executor.cgroups.mount-path property got added with blank value Key: AMBARI-20237 URL: https://issues.apache.org/jira/browse/AMBARI-20237 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Vivek Sharma Priority: Critical Fix For: 2.5.0 STR 1. Deployed cluster with Ambari version: 2.4.1.0-22 and HDP version: 2.5.0.0-1245(secure cluster) 2. Upgrade Ambari to 2.5.0.0-999 3. Regenerate keytabs for missing hosts and let it complete 4. Go to YARN - configs Result Observed that yarn.nodemanager.linux-container-executor.cgroups.mount-path got added as a property with blank value -- This message was sent by Atlassian JIRA (v6.3.15#6346)
