[jira] [Updated] (AMBARI-22755) Show OneFS JMX metrics on the UI
[ https://issues.apache.org/jira/browse/AMBARI-22755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22755: Labels: pull-request-available (was: ) > Show OneFS JMX metrics on the UI > > > Key: AMBARI-22755 > URL: https://issues.apache.org/jira/browse/AMBARI-22755 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > > There are some metrics like a (NameNode uptime/StartTime and HDFS disk > usage/Capacity*) which cannot be shown in a widget because widgets only > support AMS based metrics. > Normally these metrics are shown in a service specific dashboard which is > hardcoded in the ui (summary.js/serviceCustomViewsMap). > {code} > serviceCustomViewsMap: function() { > return { > HBASE: App.MainDashboardServiceHbaseView, > HDFS: App.MainDashboardServiceHdfsView, > STORM: App.MainDashboardServiceStormView, > YARN: App.MainDashboardServiceYARNView, > RANGER: App.MainDashboardServiceRangerView, > FLUME: App.MainDashboardServiceFlumeView, > HIVE: App.MainDashboardServiceHiveView > } > }.property('serviceName'), > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-23179) Hive view 2.0 does not parse the TAB delimited CSV files while using 'Upload Table'
[ https://issues.apache.org/jira/browse/AMBARI-23179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore reassigned AMBARI-23179: -- Assignee: Nitiraj Singh Rathore > Hive view 2.0 does not parse the TAB delimited CSV files while using 'Upload > Table' > --- > > Key: AMBARI-23179 > URL: https://issues.apache.org/jira/browse/AMBARI-23179 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.0 > Environment: HDP 2.6.3 > Ambari 2.6.0 >Reporter: Sindhu Subhas >Assignee: Nitiraj Singh Rathore >Priority: Major > Attachments: Screen Shot 2018-02-28 at 1.02.44 AM.png, Screen Shot > 2018-02-28 at 5.05.55 PM.png, Screen Shot 2018-02-28 at 5.06.47 PM.png, > Screen Shot 2018-02-28 at 5.07.30 PM.png, datatab.tsv > > > Problem: > When trying to Upload table from Hive view 2.0 from a TAB delimited file, the > data is not parsed as expected. > Same feature works as expected in Hive view 1.5.0. > Attached output from Hive view 2.0 and output from Hive view 1.5.0. > From the code, we do see difference in the code for > src/main/java/org/apache/ambari/view/hive20/resources/uploads/UploadService.java. > Debug from Hive view 2.0: > {code:java} > 27 Feb 2018 20:27:28,169 DEBUG > [HiveViewActorSystem-akka.actor.default-dispatcher-4] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] OperationController:53 - } java.util.HashMap > 27 Feb 2018 20:27:28,169 DEBUG > [HiveViewActorSystem-akka.actor.default-dispatcher-4] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] HiveActor:41 - Message submitted: > 927343c0-5ed6-435c-be60-37448ac1a8b0 > 27 Feb 2018 20:27:30,925 INFO [ambari-client-thread-38] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] UploadService:484 - isFirstRowHeader : false, > inputFileType : CSV > 27 Feb 2018 20:27:30,934 INFO [ambari-client-thread-38] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] OpenCSVParser:50 - setting delimiter as T > 27 Feb 2018 20:27:30,934 INFO [ambari-client-thread-38] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] OpenCSVParser:56 - setting Quote char : " > 27 Feb 2018 20:27:30,934 INFO [ambari-client-thread-38] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] OpenCSVParser:62 - setting escapeChar : \ > 27 Feb 2018 20:27:30,939 INFO [ambari-client-thread-38] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] Parser:75 - generating preview for : > ParseOptions{options={OPTIONS_CSV_QUOTE=", OPTIONS_CSV_DELIMITER=T, > HEADER=NONE, FILE_TYPE=CSV, OPTIONS_CSV_ESCAPE_CHAR=\}} > 27 Feb 2018 20:27:30,939 DEBUG [ambari-client-thread-38] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] Parser:83 - Illegal number of preview columns supplied > null > 27 Feb 2018 20:27:30,943 DEBUG [ambari-client-thread-38] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] ParseUtils:152 - error while parsing as timestamp > string column1 column2 column3 > java.lang.IllegalArgumentException: Timestamp format must be -mm-dd > hh:mm:ss[.f] > at java.sql.Timestamp.valueOf(Timestamp.java:204) > . > 27 Feb 2018 20:27:30,948 INFO [ambari-client-thread-38] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] Parser:149 - datatype detected for column 0 : STRING > 27 Feb 2018 20:27:30,949 DEBUG [ambari-client-thread-38] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] Parser:159 - return headers : > [ColumnInfo{name='column1', type='STRING', precision=null, scale=null, > comment='null'}] > {code} > Debug from Hive view 1.5.0: > {code:java} > 27 Feb 2018 20:13:15,881 INFO [ambari-client-thread-38] [HIVE 1.5.0 > AUTO_HIVE_INSTANCE] UploadService:499 - isFirstRowHeader : true, > inputFileType : CSV > 27 Feb 2018 20:13:15,918 INFO [ambari-client-thread-38] [HIVE 1.5.0 > AUTO_HIVE_INSTANCE] OpenCSVParser:50 - setting delimiter as > 27 Feb 2018 20:13:15,919 INFO [ambari-client-thread-38] [HIVE 1.5.0 > AUTO_HIVE_INSTANCE] OpenCSVParser:56 - setting Quote char : " > 27 Feb 2018 20:13:15,919 INFO [ambari-client-thread-38] [HIVE 1.5.0 > AUTO_HIVE_INSTANCE] OpenCSVParser:62 - setting escapeChar : \ > 27 Feb 2018 20:13:15,928 INFO [ambari-client-thread-38] [HIVE 1.5.0 > AUTO_HIVE_INSTANCE] Parser:75 - generating preview for : > ParseOptions{options={OPTIONS_CSV_QUOTE=", OPTIONS_CSV_DELIMITER= , > HEADER=FIRST_RECORD, FILE_TYPE=CSV, OPTIONS_CSV_ESCAPE_CHAR=\}} > 27 Feb 2018 20:13:15,929 DEBUG [ambari-client-thread-38] [HIVE 1.5.0 > AUTO_HIVE_INSTANCE] Parser:83 - Illegal number of preview columns supplied > null > 27 Feb 2018 20:13:15,936 DEBUG [ambari-client-thread-38] [HIVE 1.5.0 > AUTO_HIVE_INSTANCE] ParseUtils:152 - error while parsing as timestamp string > AD > java.lang.IllegalArgumentException: Timestamp format must be -mm-dd > hh:mm:ss[.f] > at java.sql.Timestamp.valueOf(Timestamp.java:204) > . > 27 Feb 2018 20:13:15,961 INFO [ambari-client-threa
[jira] [Resolved] (AMBARI-23170) Instance manager json output should have the same structure for both client and server modules
[ https://issues.apache.org/jira/browse/AMBARI-23170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen resolved AMBARI-23170. - Resolution: Fixed > Instance manager json output should have the same structure for both client > and server modules > -- > > Key: AMBARI-23170 > URL: https://issues.apache.org/jira/browse/AMBARI-23170 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23179) Hive view 2.0 does not parse the TAB delimited CSV files while using 'Upload Table'
[ https://issues.apache.org/jira/browse/AMBARI-23179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23179: Labels: pull-request-available (was: ) > Hive view 2.0 does not parse the TAB delimited CSV files while using 'Upload > Table' > --- > > Key: AMBARI-23179 > URL: https://issues.apache.org/jira/browse/AMBARI-23179 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.0 > Environment: HDP 2.6.3 > Ambari 2.6.0 >Reporter: Sindhu Subhas >Assignee: Nitiraj Singh Rathore >Priority: Major > Labels: pull-request-available > Attachments: Screen Shot 2018-02-28 at 1.02.44 AM.png, Screen Shot > 2018-02-28 at 5.05.55 PM.png, Screen Shot 2018-02-28 at 5.06.47 PM.png, > Screen Shot 2018-02-28 at 5.07.30 PM.png, datatab.tsv > > > Problem: > When trying to Upload table from Hive view 2.0 from a TAB delimited file, the > data is not parsed as expected. > Same feature works as expected in Hive view 1.5.0. > Attached output from Hive view 2.0 and output from Hive view 1.5.0. > From the code, we do see difference in the code for > src/main/java/org/apache/ambari/view/hive20/resources/uploads/UploadService.java. > Debug from Hive view 2.0: > {code:java} > 27 Feb 2018 20:27:28,169 DEBUG > [HiveViewActorSystem-akka.actor.default-dispatcher-4] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] OperationController:53 - } java.util.HashMap > 27 Feb 2018 20:27:28,169 DEBUG > [HiveViewActorSystem-akka.actor.default-dispatcher-4] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] HiveActor:41 - Message submitted: > 927343c0-5ed6-435c-be60-37448ac1a8b0 > 27 Feb 2018 20:27:30,925 INFO [ambari-client-thread-38] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] UploadService:484 - isFirstRowHeader : false, > inputFileType : CSV > 27 Feb 2018 20:27:30,934 INFO [ambari-client-thread-38] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] OpenCSVParser:50 - setting delimiter as T > 27 Feb 2018 20:27:30,934 INFO [ambari-client-thread-38] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] OpenCSVParser:56 - setting Quote char : " > 27 Feb 2018 20:27:30,934 INFO [ambari-client-thread-38] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] OpenCSVParser:62 - setting escapeChar : \ > 27 Feb 2018 20:27:30,939 INFO [ambari-client-thread-38] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] Parser:75 - generating preview for : > ParseOptions{options={OPTIONS_CSV_QUOTE=", OPTIONS_CSV_DELIMITER=T, > HEADER=NONE, FILE_TYPE=CSV, OPTIONS_CSV_ESCAPE_CHAR=\}} > 27 Feb 2018 20:27:30,939 DEBUG [ambari-client-thread-38] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] Parser:83 - Illegal number of preview columns supplied > null > 27 Feb 2018 20:27:30,943 DEBUG [ambari-client-thread-38] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] ParseUtils:152 - error while parsing as timestamp > string column1 column2 column3 > java.lang.IllegalArgumentException: Timestamp format must be -mm-dd > hh:mm:ss[.f] > at java.sql.Timestamp.valueOf(Timestamp.java:204) > . > 27 Feb 2018 20:27:30,948 INFO [ambari-client-thread-38] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] Parser:149 - datatype detected for column 0 : STRING > 27 Feb 2018 20:27:30,949 DEBUG [ambari-client-thread-38] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] Parser:159 - return headers : > [ColumnInfo{name='column1', type='STRING', precision=null, scale=null, > comment='null'}] > {code} > Debug from Hive view 1.5.0: > {code:java} > 27 Feb 2018 20:13:15,881 INFO [ambari-client-thread-38] [HIVE 1.5.0 > AUTO_HIVE_INSTANCE] UploadService:499 - isFirstRowHeader : true, > inputFileType : CSV > 27 Feb 2018 20:13:15,918 INFO [ambari-client-thread-38] [HIVE 1.5.0 > AUTO_HIVE_INSTANCE] OpenCSVParser:50 - setting delimiter as > 27 Feb 2018 20:13:15,919 INFO [ambari-client-thread-38] [HIVE 1.5.0 > AUTO_HIVE_INSTANCE] OpenCSVParser:56 - setting Quote char : " > 27 Feb 2018 20:13:15,919 INFO [ambari-client-thread-38] [HIVE 1.5.0 > AUTO_HIVE_INSTANCE] OpenCSVParser:62 - setting escapeChar : \ > 27 Feb 2018 20:13:15,928 INFO [ambari-client-thread-38] [HIVE 1.5.0 > AUTO_HIVE_INSTANCE] Parser:75 - generating preview for : > ParseOptions{options={OPTIONS_CSV_QUOTE=", OPTIONS_CSV_DELIMITER= , > HEADER=FIRST_RECORD, FILE_TYPE=CSV, OPTIONS_CSV_ESCAPE_CHAR=\}} > 27 Feb 2018 20:13:15,929 DEBUG [ambari-client-thread-38] [HIVE 1.5.0 > AUTO_HIVE_INSTANCE] Parser:83 - Illegal number of preview columns supplied > null > 27 Feb 2018 20:13:15,936 DEBUG [ambari-client-thread-38] [HIVE 1.5.0 > AUTO_HIVE_INSTANCE] ParseUtils:152 - error while parsing as timestamp string > AD > java.lang.IllegalArgumentException: Timestamp format must be -mm-dd > hh:mm:ss[.f] > at java.sql.Timestamp.valueOf(Timestamp.java:204) > . > 27 Feb 2018 20:13:
[jira] [Updated] (AMBARI-23179) Hive view 2.0 does not parse the TAB delimited CSV files while using 'Upload Table'
[ https://issues.apache.org/jira/browse/AMBARI-23179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-23179: --- Status: Patch Available (was: Open) > Hive view 2.0 does not parse the TAB delimited CSV files while using 'Upload > Table' > --- > > Key: AMBARI-23179 > URL: https://issues.apache.org/jira/browse/AMBARI-23179 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.0 > Environment: HDP 2.6.3 > Ambari 2.6.0 >Reporter: Sindhu Subhas >Assignee: Nitiraj Singh Rathore >Priority: Major > Labels: pull-request-available > Attachments: Screen Shot 2018-02-28 at 1.02.44 AM.png, Screen Shot > 2018-02-28 at 5.05.55 PM.png, Screen Shot 2018-02-28 at 5.06.47 PM.png, > Screen Shot 2018-02-28 at 5.07.30 PM.png, datatab.tsv > > Time Spent: 20m > Remaining Estimate: 0h > > Problem: > When trying to Upload table from Hive view 2.0 from a TAB delimited file, the > data is not parsed as expected. > Same feature works as expected in Hive view 1.5.0. > Attached output from Hive view 2.0 and output from Hive view 1.5.0. > From the code, we do see difference in the code for > src/main/java/org/apache/ambari/view/hive20/resources/uploads/UploadService.java. > Debug from Hive view 2.0: > {code:java} > 27 Feb 2018 20:27:28,169 DEBUG > [HiveViewActorSystem-akka.actor.default-dispatcher-4] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] OperationController:53 - } java.util.HashMap > 27 Feb 2018 20:27:28,169 DEBUG > [HiveViewActorSystem-akka.actor.default-dispatcher-4] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] HiveActor:41 - Message submitted: > 927343c0-5ed6-435c-be60-37448ac1a8b0 > 27 Feb 2018 20:27:30,925 INFO [ambari-client-thread-38] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] UploadService:484 - isFirstRowHeader : false, > inputFileType : CSV > 27 Feb 2018 20:27:30,934 INFO [ambari-client-thread-38] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] OpenCSVParser:50 - setting delimiter as T > 27 Feb 2018 20:27:30,934 INFO [ambari-client-thread-38] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] OpenCSVParser:56 - setting Quote char : " > 27 Feb 2018 20:27:30,934 INFO [ambari-client-thread-38] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] OpenCSVParser:62 - setting escapeChar : \ > 27 Feb 2018 20:27:30,939 INFO [ambari-client-thread-38] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] Parser:75 - generating preview for : > ParseOptions{options={OPTIONS_CSV_QUOTE=", OPTIONS_CSV_DELIMITER=T, > HEADER=NONE, FILE_TYPE=CSV, OPTIONS_CSV_ESCAPE_CHAR=\}} > 27 Feb 2018 20:27:30,939 DEBUG [ambari-client-thread-38] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] Parser:83 - Illegal number of preview columns supplied > null > 27 Feb 2018 20:27:30,943 DEBUG [ambari-client-thread-38] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] ParseUtils:152 - error while parsing as timestamp > string column1 column2 column3 > java.lang.IllegalArgumentException: Timestamp format must be -mm-dd > hh:mm:ss[.f] > at java.sql.Timestamp.valueOf(Timestamp.java:204) > . > 27 Feb 2018 20:27:30,948 INFO [ambari-client-thread-38] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] Parser:149 - datatype detected for column 0 : STRING > 27 Feb 2018 20:27:30,949 DEBUG [ambari-client-thread-38] [HIVE 2.0.0 > AUTO_HIVE20_INSTANCE] Parser:159 - return headers : > [ColumnInfo{name='column1', type='STRING', precision=null, scale=null, > comment='null'}] > {code} > Debug from Hive view 1.5.0: > {code:java} > 27 Feb 2018 20:13:15,881 INFO [ambari-client-thread-38] [HIVE 1.5.0 > AUTO_HIVE_INSTANCE] UploadService:499 - isFirstRowHeader : true, > inputFileType : CSV > 27 Feb 2018 20:13:15,918 INFO [ambari-client-thread-38] [HIVE 1.5.0 > AUTO_HIVE_INSTANCE] OpenCSVParser:50 - setting delimiter as > 27 Feb 2018 20:13:15,919 INFO [ambari-client-thread-38] [HIVE 1.5.0 > AUTO_HIVE_INSTANCE] OpenCSVParser:56 - setting Quote char : " > 27 Feb 2018 20:13:15,919 INFO [ambari-client-thread-38] [HIVE 1.5.0 > AUTO_HIVE_INSTANCE] OpenCSVParser:62 - setting escapeChar : \ > 27 Feb 2018 20:13:15,928 INFO [ambari-client-thread-38] [HIVE 1.5.0 > AUTO_HIVE_INSTANCE] Parser:75 - generating preview for : > ParseOptions{options={OPTIONS_CSV_QUOTE=", OPTIONS_CSV_DELIMITER= , > HEADER=FIRST_RECORD, FILE_TYPE=CSV, OPTIONS_CSV_ESCAPE_CHAR=\}} > 27 Feb 2018 20:13:15,929 DEBUG [ambari-client-thread-38] [HIVE 1.5.0 > AUTO_HIVE_INSTANCE] Parser:83 - Illegal number of preview columns supplied > null > 27 Feb 2018 20:13:15,936 DEBUG [ambari-client-thread-38] [HIVE 1.5.0 > AUTO_HIVE_INSTANCE] ParseUtils:152 - error while parsing as timestamp string > AD > java.lang.IllegalArgumentException: Timestamp format must be -mm-dd > hh:mm:ss[.f] > at java.sql.Timest
[jira] [Commented] (AMBARI-22897) Tez view button doesnt works in ambari hive views 1.5
[ https://issues.apache.org/jira/browse/AMBARI-22897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391122#comment-16391122 ] Hudson commented on AMBARI-22897: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8825 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8825/]) AMBARI-22897 - Tez view button doesnt works in ambari views 1.5 (asnaik: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=34cb92e0ba0252f97ad3228e51f27cfb4fb6a50a]) * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/router.js * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/controllers/query-tabs.js * (delete) contrib/views/hive-next/src/main/resources/ui/hive-web/app/controllers/settings.js * (delete) contrib/views/hive-next/src/main/resources/ui/hive-web/tests/unit/controllers/settings-test.js * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/templates/open-queries.hbs * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/routes/application.js * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/templates/application.hbs * (delete) contrib/views/hive-next/src/main/resources/ui/hive-web/tests/unit/views/visual-explain-test.js * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/controllers/index.js * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/controllers/open-queries.js * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/services/settings.js * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/templates/index.hbs * (delete) contrib/views/hive-next/src/main/resources/ui/hive-web/tests/unit/controllers/messages-test.js * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/styles/query-tabs.scss * (delete) contrib/views/hive-next/src/main/resources/ui/hive-web/app/templates/settings.hbs * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/controllers/application.js * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/styles/app.scss AMBARI-22897 - Tez view button doesnt works in ambari views 1. (asnaik: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=874abb60ca406aae55ad2ed0de3c36cd8f2b1b71]) * (add) contrib/views/hive-next/src/main/resources/ui/hive-web/tests/unit/routes/tez-ui-test.js * (add) contrib/views/hive-next/src/main/resources/ui/hive-web/app/components/query-settings.js * (add) contrib/views/hive-next/src/main/resources/ui/hive-web/app/templates/components/query-settings.hbs * (add) contrib/views/hive-next/src/main/resources/ui/hive-web/tests/unit/components/query-settings-test.js * (add) contrib/views/hive-next/src/main/resources/ui/hive-web/app/routes/tez-ui.js * (add) contrib/views/hive-next/src/main/resources/ui/hive-web/tests/unit/routes/visual-explain-test.js * (add) contrib/views/hive-next/src/main/resources/ui/hive-web/app/routes/visualization-ui.js * (add) contrib/views/hive-next/src/main/resources/ui/hive-web/app/routes/visual-explain.js * (add) contrib/views/hive-next/src/main/resources/ui/hive-web/app/routes/messages.js * (add) contrib/views/hive-next/src/main/resources/ui/hive-web/tests/unit/routes/messages-test.js AMBARI-22897 - Tez view button doesnt works in ambari views 1.5(asnaik) (asnaik: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=0bbb154fbc8ccd32c2846d93009dd1df0be348b1]) * (add) contrib/views/hive-next/src/main/resources/ui/hive-web/tests/unit/routes/tez-ui-test.js * (add) contrib/views/hive-next/src/main/resources/ui/hive-web/app/routes/messages.js * (add) contrib/views/hive-next/src/main/resources/ui/hive-web/app/routes/visualization-ui.js * (add) contrib/views/hive-next/src/main/resources/ui/hive-web/tests/unit/routes/messages-test.js * (add) contrib/views/hive-next/src/main/resources/ui/hive-web/tests/unit/routes/visual-explain-test.js * (add) contrib/views/hive-next/src/main/resources/ui/hive-web/tests/unit/components/query-settings-test.js * (add) contrib/views/hive-next/src/main/resources/ui/hive-web/app/templates/components/query-settings.hbs * (add) contrib/views/hive-next/src/main/resources/ui/hive-web/app/routes/visual-explain.js * (add) contrib/views/hive-next/src/main/resources/ui/hive-web/app/routes/tez-ui.js * (add) contrib/views/hive-next/src/main/resources/ui/hive-web/app/components/query-settings.js AMBARI-22897 - Tez view button doesnt works in ambari views 1.5,Fix the (asnaik: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=a425ed4f5deb7b11b34a6f6e180684b54bed111f]) * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/templates/open-queries.hbs * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/styles/query-tabs.scss * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/controllers/query-tabs.js * (edit) contrib/views/hive-next/src/main/resources/ui/hiv
[jira] [Updated] (AMBARI-22897) Tez view button doesnt works in ambari hive views 1.5
[ https://issues.apache.org/jira/browse/AMBARI-22897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22897: Labels: patch-available pull-request-available (was: patch-available) > Tez view button doesnt works in ambari hive views 1.5 > - > > Key: AMBARI-22897 > URL: https://issues.apache.org/jira/browse/AMBARI-22897 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.1 > Environment: Ambari 2.6.1 >Reporter: Akhil S Naik >Assignee: Akhil S Naik >Priority: Major > Labels: patch-available, pull-request-available > Fix For: 3.0.0 > > Attachments: Screen Shot 2018-02-01 at 8.00.17 PM.png > > > *Issue :* > Login to ambari version 2.6.1 navigate to hive view 1.5 > When click on tez button or visualization or visual explain or settings > button > the page throws a script error and it become a blank page > *Root Cause :* > when click on the tez button, visualization or any other side button , > the following error is thrown from ember : > Assertion Failed: You attempted to render into 'index' but it was not found > attached the image error -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23143) Failure while starting Spark2 service after performing ambari upgrade
[ https://issues.apache.org/jira/browse/AMBARI-23143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391239#comment-16391239 ] Hudson commented on AMBARI-23143: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #649 (See [https://builds.apache.org/job/Ambari-branch-2.6/649/]) AMBARI-23143. Failure while starting Spark2 service after performing (dlysnichenko: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=4bf5d3ce2b475956d2e88fdf7dd5e69a6cb7fb6f]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/properties/stack_packages.json > Failure while starting Spark2 service after performing ambari upgrade > - > > Key: AMBARI-23143 > URL: https://issues.apache.org/jira/browse/AMBARI-23143 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.2 > Environment: ambari-server --version 2.6.2.0-82 > HDP-2.6.1.0-129 >Reporter: Supreeth Sharma >Assignee: Dmitry Lysnichenko >Priority: Blocker > Labels: pull-request-available > Fix For: 2.6.2 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Test steps : > 1) Deploy a cluster with ambari-2.5.1.0-159 + HDP-2.6.1.0-129 > 2) Upgrade ambari to 2.6.2.0-82 > 3) Now try to restart all the services. The operation is failing with below > exception while trying to start Spark2 > {code:java} > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/hook.py", > line 37, in > AfterInstallHook().execute() > File > "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", > line 375, in execute > method(env) > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/hook.py", > line 31, in hook > setup_stack_symlinks(self.stroutfile) > File > "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/shared_initialization.py", > line 49, in setup_stack_symlinks > stack_packages = > stack_select.get_packages(stack_select.PACKAGE_SCOPE_INSTALL) > File > "/usr/lib/ambari-agent/lib/resource_management/libraries/functions/stack_select.py", > line 235, in get_packages > raise Fail("The package {0} is not supported by this version of the > stack-select tool.".format(package)) > resource_management.core.exceptions.Fail: The package livy2-client is not > supported by this version of the stack-select tool.{code} > livy2-client package was added in HDP 2.6.3 and was not present before that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23180) Hide downgrade option from stack upgrade wizard
Vivek Sharma created AMBARI-23180: - Summary: Hide downgrade option from stack upgrade wizard Key: AMBARI-23180 URL: https://issues.apache.org/jira/browse/AMBARI-23180 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.0 Reporter: Vivek Sharma Fix For: 2.7.0 Downgrade button should be removed from the stack upgrade wizard for upgrade paths from HDP-2.6 to 3.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23129) Multiple issues while executing Ambari server upgrade to Ambari 2.7.0
[ https://issues.apache.org/jira/browse/AMBARI-23129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-23129: -- Summary: Multiple issues while executing Ambari server upgrade to Ambari 2.7.0 (was: NPE while initializing Ambari server upgrade to Ambari 2.7.0) > Multiple issues while executing Ambari server upgrade to Ambari 2.7.0 > - > > Key: AMBARI-23129 > URL: https://issues.apache.org/jira/browse/AMBARI-23129 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Robert Levas >Assignee: Robert Levas >Priority: Critical > Fix For: 2.7.0 > > > An NPE is thrown will initializing the Ambari server upgrade catalog: > {code:title=com.google.inject.persist.jpa.JpaPersistService#begin} > public void begin() { > Preconditions.checkState(null == this.entityManager.get(), "Work > already begun on this thread. Looks like you have called UnitOfWork.begin() > twice without a balancing call to end() in between."); > this.entityManager.set(this.emFactory.createEntityManager()); > } > {code} > {{this.emFactory}} is {{null}}. > *Cause* > {{com.google.inject.persist.jpa.JpaPersistService#start()}} was not called > before {{com.google.inject.persist.jpa.JpaPersistService#begin}} to do order > of operations in > {{org.apache.ambari.server.upgrade.SchemaUpgradeHelper#main}}. > *Solution* > Ensure {{com.google.inject.persist.jpa.JpaPersistService#start()}} is being > called before {{com.google.inject.persist.jpa.JpaPersistService#begin}} in > {{org.apache.ambari.server.upgrade.SchemaUpgradeHelper#main}}. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23129) Multiple issues while executing Ambari server upgrade to Ambari 2.7.0
[ https://issues.apache.org/jira/browse/AMBARI-23129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-23129: -- Description: *1. An NPE is thrown will initializing the Ambari server upgrade catalog* {code:title=com.google.inject.persist.jpa.JpaPersistService#begin} public void begin() { Preconditions.checkState(null == this.entityManager.get(), "Work already begun on this thread. Looks like you have called UnitOfWork.begin() twice without a balancing call to end() in between."); this.entityManager.set(this.emFactory.createEntityManager()); } {code} {{this.emFactory}} is {{null}}. *Cause* {{com.google.inject.persist.jpa.JpaPersistService#start()}} was not called before {{com.google.inject.persist.jpa.JpaPersistService#begin}} to do order of operations in {{org.apache.ambari.server.upgrade.SchemaUpgradeHelper#main}}. *Solution* Ensure {{com.google.inject.persist.jpa.JpaPersistService#start()}} is being called before {{com.google.inject.persist.jpa.JpaPersistService#begin}} in {{org.apache.ambari.server.upgrade.SchemaUpgradeHelper#main}}. - *2. Missing repo_os table* The {{repo_os}} table was never added to the UpgradeCatalog implementation. *Solution* Add the {{repo_os}} table while executing {{org.apache.ambari.server.upgrade.UpgradeCatalog270#executeDDLUpdates}}. - *3. Entity classes are initialized before the schema of the underlying database is updated* *Solution* Notify relevant classes that the persistence infrastructure is ready after DDL updates have been applied. The {{org.apache.ambari.server.events.publishers.AmbariEventPublisher}} is to be used for issuing a {{org.apache.ambari.server.events.JpaInitializedEvent}}. was: An NPE is thrown will initializing the Ambari server upgrade catalog: {code:title=com.google.inject.persist.jpa.JpaPersistService#begin} public void begin() { Preconditions.checkState(null == this.entityManager.get(), "Work already begun on this thread. Looks like you have called UnitOfWork.begin() twice without a balancing call to end() in between."); this.entityManager.set(this.emFactory.createEntityManager()); } {code} {{this.emFactory}} is {{null}}. *Cause* {{com.google.inject.persist.jpa.JpaPersistService#start()}} was not called before {{com.google.inject.persist.jpa.JpaPersistService#begin}} to do order of operations in {{org.apache.ambari.server.upgrade.SchemaUpgradeHelper#main}}. *Solution* Ensure {{com.google.inject.persist.jpa.JpaPersistService#start()}} is being called before {{com.google.inject.persist.jpa.JpaPersistService#begin}} in {{org.apache.ambari.server.upgrade.SchemaUpgradeHelper#main}}. > Multiple issues while executing Ambari server upgrade to Ambari 2.7.0 > - > > Key: AMBARI-23129 > URL: https://issues.apache.org/jira/browse/AMBARI-23129 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Robert Levas >Assignee: Robert Levas >Priority: Critical > Fix For: 2.7.0 > > > *1. An NPE is thrown will initializing the Ambari server upgrade catalog* > {code:title=com.google.inject.persist.jpa.JpaPersistService#begin} > public void begin() { > Preconditions.checkState(null == this.entityManager.get(), "Work > already begun on this thread. Looks like you have called UnitOfWork.begin() > twice without a balancing call to end() in between."); > this.entityManager.set(this.emFactory.createEntityManager()); > } > {code} > {{this.emFactory}} is {{null}}. > *Cause* > {{com.google.inject.persist.jpa.JpaPersistService#start()}} was not called > before {{com.google.inject.persist.jpa.JpaPersistService#begin}} to do order > of operations in > {{org.apache.ambari.server.upgrade.SchemaUpgradeHelper#main}}. > *Solution* > Ensure {{com.google.inject.persist.jpa.JpaPersistService#start()}} is being > called before {{com.google.inject.persist.jpa.JpaPersistService#begin}} in > {{org.apache.ambari.server.upgrade.SchemaUpgradeHelper#main}}. > - > *2. Missing repo_os table* > The {{repo_os}} table was never added to the UpgradeCatalog implementation. > *Solution* > Add the {{repo_os}} table while executing > {{org.apache.ambari.server.upgrade.UpgradeCatalog270#executeDDLUpdates}}. > - > *3. Entity classes are initialized before the schema of the underlying > database is updated* > *Solution* > Notify relevant classes that the persistence infrastructure is ready after > DDL updates have been applied. > The {{org.apache.ambari.server.events.publishers.AmbariEventPublisher}} is to > be used for issuing a > {{org.apache.ambari.server.events.JpaInitializedEvent}}. -- This message was sent by Atlassian JIRA (v7.6.3
[jira] [Updated] (AMBARI-23129) Multiple issues while executing Ambari server upgrade to Ambari 2.7.0
[ https://issues.apache.org/jira/browse/AMBARI-23129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-23129: -- Description: *1. An NPE is thrown will initializing the Ambari server upgrade catalog* {code:title=com.google.inject.persist.jpa.JpaPersistService#begin} public void begin() { Preconditions.checkState(null == this.entityManager.get(), "Work already begun on this thread. Looks like you have called UnitOfWork.begin() twice without a balancing call to end() in between."); this.entityManager.set(this.emFactory.createEntityManager()); } {code} {{this.emFactory}} is {{null}}. *Cause* {{com.google.inject.persist.jpa.JpaPersistService#start()}} was not called before {{com.google.inject.persist.jpa.JpaPersistService#begin}} to do order of operations in {{org.apache.ambari.server.upgrade.SchemaUpgradeHelper#main}}. *Solution* Ensure {{com.google.inject.persist.jpa.JpaPersistService#start()}} is being called before {{com.google.inject.persist.jpa.JpaPersistService#begin}} in {{org.apache.ambari.server.upgrade.SchemaUpgradeHelper#main}}. - *2. Missing repo_os table* The {{repo_os}} table was never added to the UpgradeCatalog implementation. *Solution* Add the {{repo_os}} table while executing {{org.apache.ambari.server.upgrade.UpgradeCatalog270#executeDDLUpdates}}. - *3. Entity classes are initialized before the schema of the underlying database is updated* *Solution* Notify relevant classes that the persistence infrastructure is ready after DDL updates have been applied. The {{org.apache.ambari.server.events.publishers.AmbariEventPublisher}} is to be used for issuing a {{org.apache.ambari.server.events.JpaInitializedEvent}}. - *4. JVM does not exit after performing upgrade* After executing {{ambari-server upgrade}}, the JVM process hangs and does not exit. According to the logs, no errors have occurred. *Cause* The cause of this is several non-daemon threads not being shutdown by Ambari code. *Solution* Change relevant non-daemon threads to daemon threads and ensure any thread polls are not forcing one thread to be alive at all times. was: *1. An NPE is thrown will initializing the Ambari server upgrade catalog* {code:title=com.google.inject.persist.jpa.JpaPersistService#begin} public void begin() { Preconditions.checkState(null == this.entityManager.get(), "Work already begun on this thread. Looks like you have called UnitOfWork.begin() twice without a balancing call to end() in between."); this.entityManager.set(this.emFactory.createEntityManager()); } {code} {{this.emFactory}} is {{null}}. *Cause* {{com.google.inject.persist.jpa.JpaPersistService#start()}} was not called before {{com.google.inject.persist.jpa.JpaPersistService#begin}} to do order of operations in {{org.apache.ambari.server.upgrade.SchemaUpgradeHelper#main}}. *Solution* Ensure {{com.google.inject.persist.jpa.JpaPersistService#start()}} is being called before {{com.google.inject.persist.jpa.JpaPersistService#begin}} in {{org.apache.ambari.server.upgrade.SchemaUpgradeHelper#main}}. - *2. Missing repo_os table* The {{repo_os}} table was never added to the UpgradeCatalog implementation. *Solution* Add the {{repo_os}} table while executing {{org.apache.ambari.server.upgrade.UpgradeCatalog270#executeDDLUpdates}}. - *3. Entity classes are initialized before the schema of the underlying database is updated* *Solution* Notify relevant classes that the persistence infrastructure is ready after DDL updates have been applied. The {{org.apache.ambari.server.events.publishers.AmbariEventPublisher}} is to be used for issuing a {{org.apache.ambari.server.events.JpaInitializedEvent}}. > Multiple issues while executing Ambari server upgrade to Ambari 2.7.0 > - > > Key: AMBARI-23129 > URL: https://issues.apache.org/jira/browse/AMBARI-23129 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Robert Levas >Assignee: Robert Levas >Priority: Critical > Fix For: 2.7.0 > > > *1. An NPE is thrown will initializing the Ambari server upgrade catalog* > {code:title=com.google.inject.persist.jpa.JpaPersistService#begin} > public void begin() { > Preconditions.checkState(null == this.entityManager.get(), "Work > already begun on this thread. Looks like you have called UnitOfWork.begin() > twice without a balancing call to end() in between."); > this.entityManager.set(this.emFactory.createEntityManager()); > } > {code} > {{this.emFactory}} is {{null}}. > *Cause* > {{com.google.inject.persist.jpa.JpaPersistService#start()}} was not called > before {{com.google.inject.persist.jpa.J
[jira] [Updated] (AMBARI-23155) Use cluster settings API in install wizard
[ https://issues.apache.org/jira/browse/AMBARI-23155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23155: Labels: pull-request-available (was: ) > Use cluster settings API in install wizard > -- > > Key: AMBARI-23155 > URL: https://issues.apache.org/jira/browse/AMBARI-23155 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Jason Golieb >Assignee: Jason Golieb >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > > Update install wizard to use the new cluster settings API to configure the > cluster. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23106) Use localjceks URL for credential provider for local files
[ https://issues.apache.org/jira/browse/AMBARI-23106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391775#comment-16391775 ] Hudson commented on AMBARI-23106: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8826 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8826/]) AMBARI-23106. Optionally generate localjceks://file/{path} url (#590) (6454655+adoroszlai: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=31bdda57f59a4b1b6ea0502a7e980a04fa3993b5]) * (edit) ambari-common/src/main/python/resource_management/libraries/functions/security_commons.py * (edit) ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie.py > Use localjceks URL for credential provider for local files > -- > > Key: AMBARI-23106 > URL: https://issues.apache.org/jira/browse/AMBARI-23106 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.6.0 >Reporter: Zsombor Gegesy >Priority: Major > Labels: pull-request-available > Time Spent: 3h > Remaining Estimate: 0h > > Ambari generates 'jceks://file/\{filepath}' as a credential provider URL, > which force using the JavaKeyStoreProvider - which uses the hdfs API to > access the local file system. > This cause problems, when the local file system access from that API is > disabled - for security reasons, for example in Oozie. Fortunately, there is > a LocalJavaKeyStoreProvider which can be used in this case, which can be > accessed with a 'localjceks://file/\{filepath}' URL -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23173) Assign Client/Slaves page pagination control static
[ https://issues.apache.org/jira/browse/AMBARI-23173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391776#comment-16391776 ] Hudson commented on AMBARI-23173: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8826 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8826/]) [AMBARI-23173] Assign Client/Slaves page pagination control static. (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=a9a8a59bb817d1c74ff1b0fc40bc4b18bf69dcdb]) * (edit) ambari-web/app/styles/wizard.less * (edit) ambari-web/app/templates/wizard/step6.hbs > Assign Client/Slaves page pagination control static > --- > > Key: AMBARI-23173 > URL: https://issues.apache.org/jira/browse/AMBARI-23173 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Time Spent: 20m > Remaining Estimate: 0h > > pagination controls should not be hidden behind the horizontal scroll -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23181) Express Upgrade to HDP-3.0 failed on history server stop
Sandor Molnar created AMBARI-23181: -- Summary: Express Upgrade to HDP-3.0 failed on history server stop Key: AMBARI-23181 URL: https://issues.apache.org/jira/browse/AMBARI-23181 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.0 Reporter: Sandor Molnar Assignee: Sandor Molnar Fix For: 2.7.0 Upgrading a cluster with YARN+MR2 installed from HDP 2.6.4 to HDP 3.0.0 fails with the following error: {code:java} Traceback (most recent call last): File "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/YARN/package/scripts/historyserver.py", line 132, in HistoryServer().execute() File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 376, in execute method(env) File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 953, in restart self.stop(env, upgrade_type=upgrade_type) File "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/YARN/package/scripts/historyserver.py", line 49, in stop service('historyserver', action='stop', serviceName='mapreduce') File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", line 89, in thunk return fn(*args, **kwargs) File "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/YARN/package/scripts/service.py", line 99, in service Execute(daemon_cmd, user=usr) File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 166, in __init__ self.env.run() File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 160, in run self.run_action(resource, action) File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 124, in run_action provider_action() File "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py", line 262, in action_run tries=self.resource.tries, try_sleep=self.resource.try_sleep) File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 72, in inner result = function(command, **kwargs) File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 102, in checked_call tries=tries, try_sleep=try_sleep, timeout_kill_strategy=timeout_kill_strategy) File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 150, in _call_wrapper result = _call(command, **kwargs_copy) File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 303, in _call raise ExecutionFailed(err_msg, code, out, err) resource_management.core.exceptions.ExecutionFailed: Execution of 'export HADOOP_LIBEXEC_DIR=/usr/hdp/3.0.0.0-820/hadoop/libexec && /usr/hdp/3.0.0.0-820/hadoop-mapreduce/sbin/mr-jobhistory-daemon.sh --config /usr/hdp/3.0.0.0-820/hadoop/conf stop historyserver' returned 1. WARNING: YARN_CONF_DIR has been replaced by HADOOP_CONF_DIR. Using value of YARN_CONF_DIR. WARNING: YARN_LOG_DIR has been replaced by HADOOP_LOG_DIR. Using value of YARN_LOG_DIR. WARNING: YARN_LOGFILE has been replaced by HADOOP_LOGFILE. Using value of YARN_LOGFILE. WARNING: YARN_PID_DIR has been replaced by HADOOP_PID_DIR. Using value of YARN_PID_DIR. WARNING: YARN_OPTS has been replaced by HADOOP_OPTS. Using value of YARN_OPTS. WARNING: Use of this script to stop the MR JobHistory daemon is deprecated. WARNING: Attempting to execute replacement "mapred --daemon stop" instead. ERROR: Cannot find configuration directory "/usr/hdp/2.6.4.0-91/hadoop-yarn/conf" Usage: mapred [OPTIONS] SUBCOMMAND [SUBCOMMAND OPTIONS] or mapred [OPTIONS] CLASSNAME [CLASSNAME OPTIONS] where CLASSNAME is a user-provided Java class OPTIONS is none or any of: tput: No value for $TERM and no -T specified --config dir Hadoop config directory --debug turn on shell script debug mode --help usage information SUBCOMMAND is one of: Admin Commands: tput: No value for $TERM and no -T specified frameworkuploader mapreduce framework upload hsadmin job history server admin interface Client Commands: tput: No value for $TERM and no -T specified classpath prints the class path needed for running mapreduce subcommands envvars display computed Hadoop environment variables job manipulate MapReduce jobs minicluster CLI MiniCluster pipes run a Pipes job queue get information regarding JobQueues sampler sampler version print the version Daemon Commands: tput: No value for $TERM and no -T specified historyserver run job history servers as a standalone daemon SUBCOMMAND may print help when invoked w/o parameters or with -h. {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23173) Assign Client/Slaves page pagination control static
[ https://issues.apache.org/jira/browse/AMBARI-23173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt resolved AMBARI-23173. -- Resolution: Fixed merged to trunk > Assign Client/Slaves page pagination control static > --- > > Key: AMBARI-23173 > URL: https://issues.apache.org/jira/browse/AMBARI-23173 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Time Spent: 20m > Remaining Estimate: 0h > > pagination controls should not be hidden behind the horizontal scroll -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23182) Infra Solr - add custom Ambari commands for backup/migrate/restore index
Olivér Szabó created AMBARI-23182: - Summary: Infra Solr - add custom Ambari commands for backup/migrate/restore index Key: AMBARI-23182 URL: https://issues.apache.org/jira/browse/AMBARI-23182 Project: Ambari Issue Type: Bug Components: ambari-infra, ambari-server Affects Versions: 2.7.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23182) Infra Solr - add custom Ambari commands for backup/migrate/restore index
[ https://issues.apache.org/jira/browse/AMBARI-23182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23182: Labels: pull-request-available (was: ) > Infra Solr - add custom Ambari commands for backup/migrate/restore index > > > Key: AMBARI-23182 > URL: https://issues.apache.org/jira/browse/AMBARI-23182 > Project: Ambari > Issue Type: Bug > Components: ambari-infra, ambari-server >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23172) Build fails for Debian (jdeb plugin not found)
[ https://issues.apache.org/jira/browse/AMBARI-23172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako resolved AMBARI-23172. -- Resolution: Fixed Committed to trunk. > Build fails for Debian (jdeb plugin not found) > -- > > Key: AMBARI-23172 > URL: https://issues.apache.org/jira/browse/AMBARI-23172 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > {code:java} > 22:08:15 2018/03/07 06:08:14 INFO : [ERROR] No plugin found for prefix 'jdeb' > in the current project and in the plugin groups [org.sonatype.plugins, > org.apache.maven.plugins, org.codehaus.mojo] available from the repositories > [local (/grid/0/jenkins/.m2/repository), public > (http://nexus-private.hortonworks.com/nexus/content/groups/public)] -> [Help > 1] > 22:08:15 2018/03/07 06:08:14 INFO : [ERROR] > 22:08:15 2018/03/07 06:08:14 INFO : [ERROR] To see the full stack trace of > the errors, re-run Maven with the -e switch. > 22:08:15 2018/03/07 06:08:14 INFO : [ERROR] Re-run Maven using the -X switch > to enable full debug logging. > 22:08:15 2018/03/07 06:08:14 INFO : [ERROR] > 22:08:15 2018/03/07 06:08:14 INFO : [ERROR] For more information about the > errors and possible solutions, please read the following articles: > 22:08:15 2018/03/07 06:08:14 INFO : [ERROR] [Help 1]{code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23183) Revert UI changes made to branch : "branch-feature-AMBARI-14714".
[ https://issues.apache.org/jira/browse/AMBARI-23183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-23183: - Description: - As we are going for a merge of "branch-feature-AMBARI-14714" (Backend changes) and "branch-feature-AMBARI-14714-ui" (UI changes) branch to and fro, removing the bare minimum changes made in "branch-feature-AMBARI-14714" ambari-web code base, to make the merge smooth. - UI code changes undone: -- AMBARI-22945 : Added UI code in *step8_controller.js* to pass the *default* service_group_name (=core) and service_name for Host component creation, as the "branch-feature-AMBARI-14714" branch assumes that service_group created would be names *"core"*. But, "branch-feature-AMBARI-14714-ui" branch has moved forward using *stack_name* and *version* as the name for the service_group (eg: HDPCore-version). Thus, this UI related changes anyways needs to be revisited. -- AMBARI-23177 : YARN and MR separation. We will bring it back after the merge. was: - As we are going for a merge of "branch-feature-AMBARI-14714" (Backend changes) and "branch-feature-AMBARI-14714-ui" (UI changes) branch to and fro, removing the bare minimum changes made in "branch-feature-AMBARI-14714" ambari-web code base, to make the merge smooth. - UI code changes undone: -- AMBARI-22945 : Added UI code in *step8_controller.js* to pass the *default* service_group_name (=core) and service_name for Host component creation, as the "branch-feature-AMBARI-14714" branch assumes that service_group created would be names *"core"*. But, "branch-feature-AMBARI-14714-ui" branch has moved forward using *stack_name* and *version* as the name for the service_group (eg: HDPCore-version). Thus, this UI related changes anyways needs to be revisited. -- AMBARI-23177 : YARN and MR separation. We will bring it back after the merge. > Revert UI changes made to branch : "branch-feature-AMBARI-14714". > - > > Key: AMBARI-23183 > URL: https://issues.apache.org/jira/browse/AMBARI-23183 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Major > Fix For: 3.0.0 > > > - As we are going for a merge of "branch-feature-AMBARI-14714" (Backend > changes) and "branch-feature-AMBARI-14714-ui" (UI changes) branch to and fro, > removing the bare minimum changes made in "branch-feature-AMBARI-14714" > ambari-web code base, to make the merge smooth. > - UI code changes undone: >-- AMBARI-22945 : Added UI code in *step8_controller.js* to pass the > *default* service_group_name (=core) and service_name for Host component > creation, as the "branch-feature-AMBARI-14714" branch assumes that > service_group created would be names *"core"*. But, > "branch-feature-AMBARI-14714-ui" branch has moved forward using *stack_name* > and *version* as the name for the service_group (eg: HDPCore-version). Thus, > this UI related changes anyways needs to be revisited. > -- AMBARI-23177 : YARN and MR separation. We will bring it back after > the merge. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23183) Revert UI changes made to branch : "branch-feature-AMBARI-14714".
Swapan Shridhar created AMBARI-23183: Summary: Revert UI changes made to branch : "branch-feature-AMBARI-14714". Key: AMBARI-23183 URL: https://issues.apache.org/jira/browse/AMBARI-23183 Project: Ambari Issue Type: Bug Components: ambari-web Reporter: Swapan Shridhar Assignee: Swapan Shridhar Fix For: 3.0.0 - As we are going for a merge of "branch-feature-AMBARI-14714" (Backend changes) and "branch-feature-AMBARI-14714-ui" (UI changes) branch to and fro, removing the bare minimum changes made in "branch-feature-AMBARI-14714" ambari-web code base, to make the merge smooth. - UI code changes undone: -- AMBARI-22945 : Added UI code in *step8_controller.js* to pass the *default* service_group_name (=core) and service_name for Host component creation, as the "branch-feature-AMBARI-14714" branch assumes that service_group created would be names *"core"*. But, "branch-feature-AMBARI-14714-ui" branch has moved forward using *stack_name* and *version* as the name for the service_group (eg: HDPCore-version). Thus, this UI related changes anyways needs to be revisited. -- AMBARI-23177 : YARN and MR separation. We will bring it back after the merge. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23183) Revert UI changes made to branch : "branch-feature-AMBARI-14714".
[ https://issues.apache.org/jira/browse/AMBARI-23183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-23183: - Description: - As we are going for a merge of "branch-feature-AMBARI-14714" (Backend changes) and "branch-feature-AMBARI-14714-ui" (UI changes) branch to and fro, removing the bare minimum changes made in "branch-feature-AMBARI-14714" ambari-web code base, to make the merge smooth. - UI code changes undone: -- AMBARI-22945 : Added UI code in *step8_controller.js* to pass the *default* service_group_name (=core) and service_name for Host component creation, as the "branch-feature-AMBARI-14714" branch assumes that service_group created would be names *"core"*. But, "branch-feature-AMBARI-14714-ui" branch has moved forward using *stack_name* and *version* as the name for the service_group (eg: HDPCore-version). Thus, this UI related changes anyways needs to be revisited. -- AMBARI-23177 : YARN and MR separation. We will bring it back after the merge. was: - As we are going for a merge of "branch-feature-AMBARI-14714" (Backend changes) and "branch-feature-AMBARI-14714-ui" (UI changes) branch to and fro, removing the bare minimum changes made in "branch-feature-AMBARI-14714" ambari-web code base, to make the merge smooth. - UI code changes undone: -- AMBARI-22945 : Added UI code in *step8_controller.js* to pass the *default* service_group_name (=core) and service_name for Host component creation, as the "branch-feature-AMBARI-14714" branch assumes that service_group created would be names *"core"*. But, "branch-feature-AMBARI-14714-ui" branch has moved forward using *stack_name* and *version* as the name for the service_group (eg: HDPCore-version). Thus, this UI related changes anyways needs to be revisited. -- AMBARI-23177 : YARN and MR separation. We will bring it back after the merge. > Revert UI changes made to branch : "branch-feature-AMBARI-14714". > - > > Key: AMBARI-23183 > URL: https://issues.apache.org/jira/browse/AMBARI-23183 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Major > Fix For: 3.0.0 > > > - As we are going for a merge of "branch-feature-AMBARI-14714" (Backend > changes) and "branch-feature-AMBARI-14714-ui" (UI changes) branch to and fro, > removing the bare minimum changes made in "branch-feature-AMBARI-14714" > ambari-web code base, to make the merge smooth. > - UI code changes undone: >-- AMBARI-22945 : Added UI code in *step8_controller.js* to pass the > *default* service_group_name (=core) and service_name for Host component > creation, as the "branch-feature-AMBARI-14714" branch assumes that > service_group created would be names *"core"*. But, > "branch-feature-AMBARI-14714-ui" branch has moved forward using *stack_name* > and *version* as the name for the service_group (eg: HDPCore-version). Thus, > this UI related changes anyways needs to be revisited. > -- AMBARI-23177 : YARN and MR separation. We will bring it back after the > merge. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23183) Revert UI changes made to branch : "branch-feature-AMBARI-14714".
[ https://issues.apache.org/jira/browse/AMBARI-23183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-23183: - Description: - As we are going for a merge of "branch-feature-AMBARI-14714" (Backend changes) and "branch-feature-AMBARI-14714-ui" (UI changes) branch to and fro, removing the bare minimum changes made in "branch-feature-AMBARI-14714" ambari-web code base, to make the merge smooth. - UI code changes undone: -- AMBARI-22945 : Added UI code in *step8_controller.js* to pass the *default* service_group_name (=core) and service_name for Host component creation, as the "branch-feature-AMBARI-14714" branch assumes that service_group created would be names *"core"*. But, "branch-feature-AMBARI-14714-ui" branch has moved forward using *stack_name* and *version* as the name for the service_group (eg: HDPCore-version). Thus, this UI related changes anyways needs to be revisited. -- AMBARI-23177 : YARN and MR separation changes made in ambari-web/app/models/stack_service.js. We will bring it back after the merge. was: - As we are going for a merge of "branch-feature-AMBARI-14714" (Backend changes) and "branch-feature-AMBARI-14714-ui" (UI changes) branch to and fro, removing the bare minimum changes made in "branch-feature-AMBARI-14714" ambari-web code base, to make the merge smooth. - UI code changes undone: -- AMBARI-22945 : Added UI code in *step8_controller.js* to pass the *default* service_group_name (=core) and service_name for Host component creation, as the "branch-feature-AMBARI-14714" branch assumes that service_group created would be names *"core"*. But, "branch-feature-AMBARI-14714-ui" branch has moved forward using *stack_name* and *version* as the name for the service_group (eg: HDPCore-version). Thus, this UI related changes anyways needs to be revisited. -- AMBARI-23177 : YARN and MR separation. We will bring it back after the merge. > Revert UI changes made to branch : "branch-feature-AMBARI-14714". > - > > Key: AMBARI-23183 > URL: https://issues.apache.org/jira/browse/AMBARI-23183 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Major > Fix For: 3.0.0 > > > - As we are going for a merge of "branch-feature-AMBARI-14714" (Backend > changes) and "branch-feature-AMBARI-14714-ui" (UI changes) branch to and fro, > removing the bare minimum changes made in "branch-feature-AMBARI-14714" > ambari-web code base, to make the merge smooth. > - UI code changes undone: >-- AMBARI-22945 : Added UI code in *step8_controller.js* to pass the > *default* service_group_name (=core) and service_name for Host component > creation, as the "branch-feature-AMBARI-14714" branch assumes that > service_group created would be names *"core"*. But, > "branch-feature-AMBARI-14714-ui" branch has moved forward using *stack_name* > and *version* as the name for the service_group (eg: HDPCore-version). Thus, > this UI related changes anyways needs to be revisited. > -- AMBARI-23177 : YARN and MR separation changes made in > ambari-web/app/models/stack_service.js. We will bring it back after the merge. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23183) Revert UI changes made to branch : "branch-feature-AMBARI-14714".
[ https://issues.apache.org/jira/browse/AMBARI-23183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-23183: - Description: - As we are going for a merge of "branch-feature-AMBARI-14714" (Backend changes) and "branch-feature-AMBARI-14714-ui" (UI changes) branch to and fro, removing the bare minimum changes made in "branch-feature-AMBARI-14714" ambari-web code base, to make the merge smooth. - UI code changes undone: -- AMBARI-22945 : Added UI code in *step8_controller.js* to pass the *default* service_group_name (=core) and service_name for Host component creation, as the "branch-feature-AMBARI-14714" branch assumes that service_group created would be names *"core"*. But, "branch-feature-AMBARI-14714-ui" branch has moved forward using *stack_name* and *version* as the name for the service_group (eg: HDPCore-version). Thus, this UI related changes anyways needs to be revisited. -- AMBARI-23177 : YARN and MR separation changes made in *ambari-web/app/models/stack_service.js*. We will bring it back after the merge. was: - As we are going for a merge of "branch-feature-AMBARI-14714" (Backend changes) and "branch-feature-AMBARI-14714-ui" (UI changes) branch to and fro, removing the bare minimum changes made in "branch-feature-AMBARI-14714" ambari-web code base, to make the merge smooth. - UI code changes undone: -- AMBARI-22945 : Added UI code in *step8_controller.js* to pass the *default* service_group_name (=core) and service_name for Host component creation, as the "branch-feature-AMBARI-14714" branch assumes that service_group created would be names *"core"*. But, "branch-feature-AMBARI-14714-ui" branch has moved forward using *stack_name* and *version* as the name for the service_group (eg: HDPCore-version). Thus, this UI related changes anyways needs to be revisited. -- AMBARI-23177 : YARN and MR separation changes made in ambari-web/app/models/stack_service.js. We will bring it back after the merge. > Revert UI changes made to branch : "branch-feature-AMBARI-14714". > - > > Key: AMBARI-23183 > URL: https://issues.apache.org/jira/browse/AMBARI-23183 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Major > Fix For: 3.0.0 > > > - As we are going for a merge of "branch-feature-AMBARI-14714" (Backend > changes) and "branch-feature-AMBARI-14714-ui" (UI changes) branch to and fro, > removing the bare minimum changes made in "branch-feature-AMBARI-14714" > ambari-web code base, to make the merge smooth. > - UI code changes undone: >-- AMBARI-22945 : Added UI code in *step8_controller.js* to pass the > *default* service_group_name (=core) and service_name for Host component > creation, as the "branch-feature-AMBARI-14714" branch assumes that > service_group created would be names *"core"*. But, > "branch-feature-AMBARI-14714-ui" branch has moved forward using *stack_name* > and *version* as the name for the service_group (eg: HDPCore-version). Thus, > this UI related changes anyways needs to be revisited. > -- AMBARI-23177 : YARN and MR separation changes made in > *ambari-web/app/models/stack_service.js*. We will bring it back after the > merge. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23183) Revert UI changes made to branch : "branch-feature-AMBARI-14714".
[ https://issues.apache.org/jira/browse/AMBARI-23183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23183: Labels: pull-request-available (was: ) > Revert UI changes made to branch : "branch-feature-AMBARI-14714". > - > > Key: AMBARI-23183 > URL: https://issues.apache.org/jira/browse/AMBARI-23183 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > > - As we are going for a merge of "branch-feature-AMBARI-14714" (Backend > changes) and "branch-feature-AMBARI-14714-ui" (UI changes) branch to and fro, > removing the bare minimum changes made in "branch-feature-AMBARI-14714" > ambari-web code base, to make the merge smooth. > - UI code changes undone: >-- AMBARI-22945 : Added UI code in *step8_controller.js* to pass the > *default* service_group_name (=core) and service_name for Host component > creation, as the "branch-feature-AMBARI-14714" branch assumes that > service_group created would be names *"core"*. But, > "branch-feature-AMBARI-14714-ui" branch has moved forward using *stack_name* > and *version* as the name for the service_group (eg: HDPCore-version). Thus, > this UI related changes anyways needs to be revisited. > -- AMBARI-23177 : YARN and MR separation changes made in > *ambari-web/app/models/stack_service.js*. We will bring it back after the > merge. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23160) Blueprints need to be updated to pass 'service_group_name' and 'service_name' also while creating Host Components
[ https://issues.apache.org/jira/browse/AMBARI-23160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila resolved AMBARI-23160. Resolution: Done As part of AMBARI-22875 in https://github.com/apache/ambari/pull/581 > Blueprints need to be updated to pass 'service_group_name' and 'service_name' > also while creating Host Components > - > > Key: AMBARI-23160 > URL: https://issues.apache.org/jira/browse/AMBARI-23160 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Swapan Shridhar >Assignee: Doroszlai, Attila >Priority: Major > Fix For: 3.0.0 > > > - As part of making changes for host component APIs being Id based and > supporting multi-component instances > https://github.com/apache/ambari/pull/477/files, there is now a requirement > to pass 'service_group_name' and 'service_name' also while creating Host > Components. > - Thus, BPs need to be updated to do so. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23183) Revert UI changes made to branch : "branch-feature-AMBARI-14714".
[ https://issues.apache.org/jira/browse/AMBARI-23183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar resolved AMBARI-23183. -- Resolution: Fixed > Revert UI changes made to branch : "branch-feature-AMBARI-14714". > - > > Key: AMBARI-23183 > URL: https://issues.apache.org/jira/browse/AMBARI-23183 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > - As we are going for a merge of "branch-feature-AMBARI-14714" (Backend > changes) and "branch-feature-AMBARI-14714-ui" (UI changes) branch to and fro, > removing the bare minimum changes made in "branch-feature-AMBARI-14714" > ambari-web code base, to make the merge smooth. > - UI code changes undone: >-- AMBARI-22945 : Added UI code in *step8_controller.js* to pass the > *default* service_group_name (=core) and service_name for Host component > creation, as the "branch-feature-AMBARI-14714" branch assumes that > service_group created would be names *"core"*. But, > "branch-feature-AMBARI-14714-ui" branch has moved forward using *stack_name* > and *version* as the name for the service_group (eg: HDPCore-version). Thus, > this UI related changes anyways needs to be revisited. > -- AMBARI-23177 : YARN and MR separation changes made in > *ambari-web/app/models/stack_service.js*. We will bring it back after the > merge. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23183) Revert UI changes made to branch : "branch-feature-AMBARI-14714".
[ https://issues.apache.org/jira/browse/AMBARI-23183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-23183: - Description: - As we are going for a merge of "branch-feature-AMBARI-14714" (Backend changes) and "branch-feature-AMBARI-14714-ui " (UI changes) branch to and fro, removing the bare minimum changes made in "branch-feature-AMBARI-14714" ambari-web code base, to make the merge smooth. - UI code changes undone: -- AMBARI-22945 : Added UI code in *step8_controller.js* to pass the *default* service_group_name (=core) and service_name for Host component creation, as the "branch-feature-AMBARI-14714" branch assumes that service_group created would be names *"core"*. But, "branch-feature-AMBARI-14714-ui" branch has moved forward using *stack_name* and *version* as the name for the service_group (eg: HDPCore-version). Thus, this UI related changes anyways needs to be revisited. -- AMBARI-23177 : YARN and MR separation changes made in *ambari-web/app/models/stack_service.js*. We will bring it back after the merge. CC [~mradhakrishnan] | [~jluniya] was: - As we are going for a merge of "branch-feature-AMBARI-14714" (Backend changes) and "branch-feature-AMBARI-14714-ui" (UI changes) branch to and fro, removing the bare minimum changes made in "branch-feature-AMBARI-14714" ambari-web code base, to make the merge smooth. - UI code changes undone: -- AMBARI-22945 : Added UI code in *step8_controller.js* to pass the *default* service_group_name (=core) and service_name for Host component creation, as the "branch-feature-AMBARI-14714" branch assumes that service_group created would be names *"core"*. But, "branch-feature-AMBARI-14714-ui" branch has moved forward using *stack_name* and *version* as the name for the service_group (eg: HDPCore-version). Thus, this UI related changes anyways needs to be revisited. -- AMBARI-23177 : YARN and MR separation changes made in *ambari-web/app/models/stack_service.js*. We will bring it back after the merge. CC [~mradhakrishnan] | [~jluniya] > Revert UI changes made to branch : "branch-feature-AMBARI-14714". > - > > Key: AMBARI-23183 > URL: https://issues.apache.org/jira/browse/AMBARI-23183 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > - As we are going for a merge of "branch-feature-AMBARI-14714" (Backend > changes) and "branch-feature-AMBARI-14714-ui " (UI changes) branch to and > fro, removing the bare minimum changes made in "branch-feature-AMBARI-14714" > ambari-web code base, to make the merge smooth. > - UI code changes undone: >-- AMBARI-22945 : Added UI code in *step8_controller.js* to pass the > *default* service_group_name (=core) and service_name for Host component > creation, as the "branch-feature-AMBARI-14714" branch assumes that > service_group created would be names *"core"*. But, > "branch-feature-AMBARI-14714-ui" branch has moved forward using *stack_name* > and *version* as the name for the service_group (eg: HDPCore-version). Thus, > this UI related changes anyways needs to be revisited. > -- AMBARI-23177 : YARN and MR separation changes made in > *ambari-web/app/models/stack_service.js*. We will bring it back after the > merge. > CC [~mradhakrishnan] | [~jluniya] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23183) Revert UI changes made to branch : "branch-feature-AMBARI-14714".
[ https://issues.apache.org/jira/browse/AMBARI-23183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-23183: - Description: - As we are going for a merge of "branch-feature-AMBARI-14714" (Backend changes) and "branch-feature-AMBARI-14714-ui" (UI changes) branch to and fro, removing the bare minimum changes made in "branch-feature-AMBARI-14714" ambari-web code base, to make the merge smooth. - UI code changes undone: -- AMBARI-22945 : Added UI code in *step8_controller.js* to pass the *default* service_group_name (=core) and service_name for Host component creation, as the "branch-feature-AMBARI-14714" branch assumes that service_group created would be names *"core"*. But, "branch-feature-AMBARI-14714-ui" branch has moved forward using *stack_name* and *version* as the name for the service_group (eg: HDPCore-version). Thus, this UI related changes anyways needs to be revisited. -- AMBARI-23177 : YARN and MR separation changes made in *ambari-web/app/models/stack_service.js*. We will bring it back after the merge. CC [~mradhakrishnan] | [~jluniya] was: - As we are going for a merge of "branch-feature-AMBARI-14714" (Backend changes) and "branch-feature-AMBARI-14714-ui" (UI changes) branch to and fro, removing the bare minimum changes made in "branch-feature-AMBARI-14714" ambari-web code base, to make the merge smooth. - UI code changes undone: -- AMBARI-22945 : Added UI code in *step8_controller.js* to pass the *default* service_group_name (=core) and service_name for Host component creation, as the "branch-feature-AMBARI-14714" branch assumes that service_group created would be names *"core"*. But, "branch-feature-AMBARI-14714-ui" branch has moved forward using *stack_name* and *version* as the name for the service_group (eg: HDPCore-version). Thus, this UI related changes anyways needs to be revisited. -- AMBARI-23177 : YARN and MR separation changes made in *ambari-web/app/models/stack_service.js*. We will bring it back after the merge. > Revert UI changes made to branch : "branch-feature-AMBARI-14714". > - > > Key: AMBARI-23183 > URL: https://issues.apache.org/jira/browse/AMBARI-23183 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > - As we are going for a merge of "branch-feature-AMBARI-14714" (Backend > changes) and "branch-feature-AMBARI-14714-ui" (UI changes) branch to and fro, > removing the bare minimum changes made in "branch-feature-AMBARI-14714" > ambari-web code base, to make the merge smooth. > - UI code changes undone: >-- AMBARI-22945 : Added UI code in *step8_controller.js* to pass the > *default* service_group_name (=core) and service_name for Host component > creation, as the "branch-feature-AMBARI-14714" branch assumes that > service_group created would be names *"core"*. But, > "branch-feature-AMBARI-14714-ui" branch has moved forward using *stack_name* > and *version* as the name for the service_group (eg: HDPCore-version). Thus, > this UI related changes anyways needs to be revisited. > -- AMBARI-23177 : YARN and MR separation changes made in > *ambari-web/app/models/stack_service.js*. We will bring it back after the > merge. > CC [~mradhakrishnan] | [~jluniya] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23183) Revert UI changes made to branch : "branch-feature-AMBARI-14714".
[ https://issues.apache.org/jira/browse/AMBARI-23183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-23183: - Description: - As we are going for a merge of "branch-feature-AMBARI-14714" (Backend changes) and "branch-feature-AMBARI-14714-ui " (UI changes) branch to and fro, removing the bare minimum changes made in "branch-feature-AMBARI-14714" ambari-web code base, to make the merge smooth. - UI code changes undone: -- AMBARI-22945 : Added UI code in *step8_controller.js* to pass the *default* service_group_name (=core) and service_name for Host component creation, as the "branch-feature-AMBARI-14714" branch assumes that service_group created would be names *"core"*. But, "branch-feature-AMBARI-14714-ui" branch has moved forward using *stack_name* and *version* as the name for the service_group (eg: HDPCore-version). Thus, this UI related changes anyways needs to be revisited. -- AMBARI-23177 : YARN and MR separation changes made in *ambari-web/app/models/stack_service.js*. We will bring it back after the merge. CC [~mradhakrishnan] | [~jluniya] was: - As we are going for a merge of "branch-feature-AMBARI-14714" (Backend changes) and "branch-feature-AMBARI-14714-ui " (UI changes) branch to and fro, removing the bare minimum changes made in "branch-feature-AMBARI-14714" ambari-web code base, to make the merge smooth. - UI code changes undone: -- AMBARI-22945 : Added UI code in *step8_controller.js* to pass the *default* service_group_name (=core) and service_name for Host component creation, as the "branch-feature-AMBARI-14714" branch assumes that service_group created would be names *"core"*. But, "branch-feature-AMBARI-14714-ui" branch has moved forward using *stack_name* and *version* as the name for the service_group (eg: HDPCore-version). Thus, this UI related changes anyways needs to be revisited. -- AMBARI-23177 : YARN and MR separation changes made in *ambari-web/app/models/stack_service.js*. We will bring it back after the merge. CC [~mradhakrishnan] | [~jluniya] > Revert UI changes made to branch : "branch-feature-AMBARI-14714". > - > > Key: AMBARI-23183 > URL: https://issues.apache.org/jira/browse/AMBARI-23183 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > - As we are going for a merge of "branch-feature-AMBARI-14714" (Backend > changes) and "branch-feature-AMBARI-14714-ui " (UI changes) branch to and > fro, removing the bare minimum changes made in "branch-feature-AMBARI-14714" > ambari-web code base, to make the merge smooth. > - UI code changes undone: >-- AMBARI-22945 : Added UI code in *step8_controller.js* to pass the > *default* service_group_name (=core) and service_name for Host component > creation, as the "branch-feature-AMBARI-14714" branch assumes that > service_group created would be names *"core"*. But, > "branch-feature-AMBARI-14714-ui" branch has moved forward using *stack_name* > and *version* as the name for the service_group (eg: HDPCore-version). Thus, > this UI related changes anyways needs to be revisited. > -- AMBARI-23177 : YARN and MR separation changes made in > *ambari-web/app/models/stack_service.js*. We will bring it back after the > merge. > CC [~mradhakrishnan] | [~jluniya] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23021) ServiceInfo: credential_store_supported attempts to overwrite maintenance_state
[ https://issues.apache.org/jira/browse/AMBARI-23021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23021: Labels: pull-request-available (was: ) > ServiceInfo: credential_store_supported attempts to overwrite > maintenance_state > --- > > Key: AMBARI-23021 > URL: https://issues.apache.org/jira/browse/AMBARI-23021 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila >Priority: Minor > Labels: pull-request-available > > Try to update {{credential_store_supported}} property of a service: > {noformat} > $ curl -X PUT -d @- > "http://$AMBARI_SERVER:8080/api/v1/clusters/TEST/services/HDFS"; < { "ServiceInfo": { "credential_store_supported": "true" } } > EOF > HTTP/1.1 400 Bad Request > ... > "message" : "java.lang.IllegalArgumentException: No enum constant > org.apache.ambari.server.state.MaintenanceState.true" > {noformat} > Expected response: > {{IllegalArgumentException: Invalid arguments, cannot update > credential_store_supported as it is set only via service definition.}} > The response code is the same as expected due to a coincidence. > The problem is setting the wrong property: > {noformat} > 414 o = properties.get(SERVICE_CREDENTIAL_STORE_SUPPORTED_PROPERTY_ID); > 415 if (null != o) { > 416 svcRequest.setMaintenanceState(o.toString()); > 417 } > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23156) Remove Required Group Name and Expose Lifecycle to API
[ https://issues.apache.org/jira/browse/AMBARI-23156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole resolved AMBARI-23156. Resolution: Fixed > Remove Required Group Name and Expose Lifecycle to API > -- > > Key: AMBARI-23156 > URL: https://issues.apache.org/jira/browse/AMBARI-23156 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The group name is no longer a required field. Expose lifecycle via API -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23021) ServiceInfo: credential_store_supported attempts to overwrite maintenance_state
[ https://issues.apache.org/jira/browse/AMBARI-23021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-23021: --- Fix Version/s: 2.7.0 Status: Patch Available (was: In Progress) > ServiceInfo: credential_store_supported attempts to overwrite > maintenance_state > --- > > Key: AMBARI-23021 > URL: https://issues.apache.org/jira/browse/AMBARI-23021 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila >Priority: Minor > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Try to update {{credential_store_supported}} property of a service: > {noformat} > $ curl -X PUT -d @- > "http://$AMBARI_SERVER:8080/api/v1/clusters/TEST/services/HDFS"; < { "ServiceInfo": { "credential_store_supported": "true" } } > EOF > HTTP/1.1 400 Bad Request > ... > "message" : "java.lang.IllegalArgumentException: No enum constant > org.apache.ambari.server.state.MaintenanceState.true" > {noformat} > Expected response: > {{IllegalArgumentException: Invalid arguments, cannot update > credential_store_supported as it is set only via service definition.}} > The response code is the same as expected due to a coincidence. > The problem is setting the wrong property: > {noformat} > 414 o = properties.get(SERVICE_CREDENTIAL_STORE_SUPPORTED_PROPERTY_ID); > 415 if (null != o) { > 416 svcRequest.setMaintenanceState(o.toString()); > 417 } > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23182) Infra Solr - add custom Ambari commands for backup/migrate/restore index
[ https://issues.apache.org/jira/browse/AMBARI-23182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-23182: -- Status: Patch Available (was: Open) > Infra Solr - add custom Ambari commands for backup/migrate/restore index > > > Key: AMBARI-23182 > URL: https://issues.apache.org/jira/browse/AMBARI-23182 > Project: Ambari > Issue Type: Bug > Components: ambari-infra, ambari-server >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23073) Create custom commands for upgrade and backup Solr collections
[ https://issues.apache.org/jira/browse/AMBARI-23073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-23073. --- Resolution: Duplicate AMBARI-23182 > Create custom commands for upgrade and backup Solr collections > -- > > Key: AMBARI-23073 > URL: https://issues.apache.org/jira/browse/AMBARI-23073 > Project: Ambari > Issue Type: Bug > Components: ambari-infra, ambari-server >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (AMBARI-23073) Create custom commands for upgrade and backup Solr collections
[ https://issues.apache.org/jira/browse/AMBARI-23073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16392238#comment-16392238 ] Olivér Szabó edited comment on AMBARI-23073 at 3/9/18 1:48 AM: --- duplicate: AMBARI-23182 was (Author: oleewere): AMBARI-23182 > Create custom commands for upgrade and backup Solr collections > -- > > Key: AMBARI-23073 > URL: https://issues.apache.org/jira/browse/AMBARI-23073 > Project: Ambari > Issue Type: Bug > Components: ambari-infra, ambari-server >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23099) Let custom service users to access Log Search collections
[ https://issues.apache.org/jira/browse/AMBARI-23099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23099: Labels: pull-request-available (was: ) > Let custom service users to access Log Search collections > - > > Key: AMBARI-23099 > URL: https://issues.apache.org/jira/browse/AMBARI-23099 > Project: Ambari > Issue Type: Bug > Components: ambari-infra, ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)