[jira] [Commented] (AMBARI-12546) Once I released a view in Ambari-view, I want users can view it without login step. Guest user and log in automatically can solve this problem.
[
https://issues.apache.org/jira/browse/AMBARI-12546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14642252#comment-14642252
]
Hadoop QA commented on AMBARI-12546:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12747279/AMBARI-12546.0.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/3474//console
This message is automatically generated.
> Once I released a view in Ambari-view, I want users can view it without login
> step. Guest user and log in automatically can solve this problem.
> ---
>
> Key: AMBARI-12546
> URL: https://issues.apache.org/jira/browse/AMBARI-12546
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-web
>Affects Versions: trunk
>Reporter: Hua Li
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-12546.0.patch
>
>
> Once I released a view in Ambari-view, I want users can view it without login
> step. Guest user and log in automatically can solve this problem. What's
> more, this patch can work with the patch: AMBARI-12545 (for example:
> your_url:port/?from=init&dest=CAPACITY/1.1.7/canon). User can own visitors
> permissions to go to the view directly without logging in and choosing view.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-12546) Once I released a view in Ambari-view, I want users can view it without login step. Guest user and log in automatically can solve this problem.
[ https://issues.apache.org/jira/browse/AMBARI-12546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hua Li updated AMBARI-12546: Attachment: AMBARI-12546.0.patch > Once I released a view in Ambari-view, I want users can view it without login > step. Guest user and log in automatically can solve this problem. > --- > > Key: AMBARI-12546 > URL: https://issues.apache.org/jira/browse/AMBARI-12546 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: trunk >Reporter: Hua Li >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-12546.0.patch > > > Once I released a view in Ambari-view, I want users can view it without login > step. Guest user and log in automatically can solve this problem. What's > more, this patch can work with the patch: AMBARI-12545 (for example: > your_url:port/?from=init&dest=CAPACITY/1.1.7/canon). User can own visitors > permissions to go to the view directly without logging in and choosing view. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12546) Once I released a view in Ambari-view, I want users can view it without login step. Guest user and log in automatically can solve this problem.
[ https://issues.apache.org/jira/browse/AMBARI-12546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hua Li updated AMBARI-12546: Description: Once I released a view in Ambari-view, I want users can view it without login step. Guest user and log in automatically can solve this problem. What's more, this patch can work with the patch: AMBARI-12545 (for example: your_url:port/?from=init&dest=CAPACITY/1.1.7/canon). User can own visitors permissions to go to the view directly without logging in and choosing view. (was: Once I released a view in Ambari-view, I want users can view it without login step. Guest user and log in automatically can solve this problem. What's more, this patch can work with the patch: AMBARI-12545. User can own visitors permissions to go to the view directly without logging in and choosing view.) > Once I released a view in Ambari-view, I want users can view it without login > step. Guest user and log in automatically can solve this problem. > --- > > Key: AMBARI-12546 > URL: https://issues.apache.org/jira/browse/AMBARI-12546 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: trunk >Reporter: Hua Li >Priority: Minor > Fix For: trunk > > > Once I released a view in Ambari-view, I want users can view it without login > step. Guest user and log in automatically can solve this problem. What's > more, this patch can work with the patch: AMBARI-12545 (for example: > your_url:port/?from=init&dest=CAPACITY/1.1.7/canon). User can own visitors > permissions to go to the view directly without logging in and choosing view. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12546) Once I released a view in Ambari-view, I want users can view it without login step. Guest user and log in automatically can solve this problem.
[ https://issues.apache.org/jira/browse/AMBARI-12546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hua Li updated AMBARI-12546: Description: Once I released a view in Ambari-view, I want users can view it without login step. Guest user and log in automatically can solve this problem. What's more, this patch can work with the patch: AMBARI-12545. User can own visitors permissions to go to the view directly without logging in and choosing view. > Once I released a view in Ambari-view, I want users can view it without login > step. Guest user and log in automatically can solve this problem. > --- > > Key: AMBARI-12546 > URL: https://issues.apache.org/jira/browse/AMBARI-12546 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: trunk >Reporter: Hua Li >Priority: Minor > Fix For: trunk > > > Once I released a view in Ambari-view, I want users can view it without login > step. Guest user and log in automatically can solve this problem. What's > more, this patch can work with the patch: AMBARI-12545. User can own visitors > permissions to go to the view directly without logging in and choosing view. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-12546) Once I released a view in Ambari-view, I want users can view it without login step. Guest user and log in automatically can solve this problem.
Hua Li created AMBARI-12546: --- Summary: Once I released a view in Ambari-view, I want users can view it without login step. Guest user and log in automatically can solve this problem. Key: AMBARI-12546 URL: https://issues.apache.org/jira/browse/AMBARI-12546 Project: Ambari Issue Type: Improvement Components: ambari-web Affects Versions: trunk Reporter: Hua Li Priority: Minor Fix For: trunk -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12545) Once I released a view in Ambari-view, I want users can go to the view directly without the step of choosing in the Main view list. It will be a better user experien
[
https://issues.apache.org/jira/browse/AMBARI-12545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14642198#comment-14642198
]
Hadoop QA commented on AMBARI-12545:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12747269/AMBARI-12545.0.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/3473//console
This message is automatically generated.
> Once I released a view in Ambari-view, I want users can go to the view
> directly without the step of choosing in the Main view list. It will be a
> better user experience.
> -
>
> Key: AMBARI-12545
> URL: https://issues.apache.org/jira/browse/AMBARI-12545
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-web
>Affects Versions: trunk
>Reporter: Hua Li
>Priority: Minor
> Labels: patch
> Fix For: trunk
>
> Attachments: AMBARI-12545.0.patch
>
>
> For a developer: Once I released a view in Ambari-view, I want users can go
> to the view directly without the step of choosing in the Main view list. It
> will be a better user experience.
> For an user: user can go to the view directly and don't need to search the
> view in the main view list.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-12545) Once I released a view in Ambari-view, I want users can go to the view directly without the step of choosing in the Main view list. It will be a better user experience
[ https://issues.apache.org/jira/browse/AMBARI-12545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hua Li updated AMBARI-12545: Attachment: AMBARI-12545.0.patch > Once I released a view in Ambari-view, I want users can go to the view > directly without the step of choosing in the Main view list. It will be a > better user experience. > - > > Key: AMBARI-12545 > URL: https://issues.apache.org/jira/browse/AMBARI-12545 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: trunk >Reporter: Hua Li >Priority: Minor > Labels: patch > Fix For: trunk > > Attachments: AMBARI-12545.0.patch > > > For a developer: Once I released a view in Ambari-view, I want users can go > to the view directly without the step of choosing in the Main view list. It > will be a better user experience. > For an user: user can go to the view directly and don't need to search the > view in the main view list. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12545) Once I released a view in Ambari-view, I want users can go to the view directly without the step of choosing in the Main view list. It will be a better user experience
[ https://issues.apache.org/jira/browse/AMBARI-12545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hua Li updated AMBARI-12545: Attachment: (was: patch_HuaLi.txt) > Once I released a view in Ambari-view, I want users can go to the view > directly without the step of choosing in the Main view list. It will be a > better user experience. > - > > Key: AMBARI-12545 > URL: https://issues.apache.org/jira/browse/AMBARI-12545 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: trunk >Reporter: Hua Li >Priority: Minor > Labels: patch > Fix For: trunk > > > For a developer: Once I released a view in Ambari-view, I want users can go > to the view directly without the step of choosing in the Main view list. It > will be a better user experience. > For an user: user can go to the view directly and don't need to search the > view in the main view list. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12545) Once I released a view in Ambari-view, I want users can go to the view directly without the step of choosing in the Main view list. It will be a better user experience
[ https://issues.apache.org/jira/browse/AMBARI-12545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hua Li updated AMBARI-12545: Attachment: patch_HuaLi.txt > Once I released a view in Ambari-view, I want users can go to the view > directly without the step of choosing in the Main view list. It will be a > better user experience. > - > > Key: AMBARI-12545 > URL: https://issues.apache.org/jira/browse/AMBARI-12545 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: trunk >Reporter: Hua Li >Priority: Minor > Labels: patch > Fix For: trunk > > Attachments: patch_HuaLi.txt > > > For a developer: Once I released a view in Ambari-view, I want users can go > to the view directly without the step of choosing in the Main view list. It > will be a better user experience. > For an user: user can go to the view directly and don't need to search the > view in the main view list. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-12545) Once I released a view in Ambari-view, I want users can go to the view directly without the step of choosing in the Main view list. It will be a better user experience
Hua Li created AMBARI-12545: --- Summary: Once I released a view in Ambari-view, I want users can go to the view directly without the step of choosing in the Main view list. It will be a better user experience. Key: AMBARI-12545 URL: https://issues.apache.org/jira/browse/AMBARI-12545 Project: Ambari Issue Type: Improvement Components: ambari-web Affects Versions: trunk Reporter: Hua Li Priority: Minor Fix For: trunk For a developer: Once I released a view in Ambari-view, I want users can go to the view directly without the step of choosing in the Main view list. It will be a better user experience. For an user: user can go to the view directly and don't need to search the view in the main view list. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Review Request 36808: FE: Hosts page table takes atleast 4.2s to populate 100 host entries
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36808/#review93061 --- Ship it! Ship It! - Alejandro Fernandez On July 25, 2015, 1:37 a.m., Richard Zang wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/36808/ > --- > > (Updated July 25, 2015, 1:37 a.m.) > > > Review request for Ambari, Andrii Tkach, Srimanth Gunturi, and Yusaku Sako. > > > Bugs: AMBARI-12543 > https://issues.apache.org/jira/browse/AMBARI-12543 > > > Repository: ambari > > > Description > --- > > Avoid redundant update triggerred by filter > initialization(App.TableView.initFilters) during host page load. > > > Diffs > - > > ambari-web/app/views/main/host.js b204985 > > Diff: https://reviews.apache.org/r/36808/diff/ > > > Testing > --- > > Manually tested on live cluster. > All unit test passed. > 6478 tests complete (9 seconds) > 94 tests pending > > > Thanks, > > Richard Zang > >
[jira] [Commented] (AMBARI-12179) Tez View should automatically configuration settings based on http/https policy
[ https://issues.apache.org/jira/browse/AMBARI-12179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14642096#comment-14642096 ] Mahadev konar commented on AMBARI-12179: +1 the patch looks good. [~hitesh] wnat to go ahead and commit to trunk adn branch-2.1? > Tez View should automatically configuration settings based on http/https > policy > --- > > Key: AMBARI-12179 > URL: https://issues.apache.org/jira/browse/AMBARI-12179 > Project: Ambari > Issue Type: Bug >Reporter: Hitesh Shah >Assignee: Hitesh Shah > Fix For: 2.1.1 > > Attachments: AMBARI-12179.1.patch, AMBARI-12179.2.patch > > > The current tez view impl always defaults to the http addresses instead of > relying on the http policy setting. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12179) Tez View should automatically configuration settings based on http/https policy
[ https://issues.apache.org/jira/browse/AMBARI-12179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated AMBARI-12179: --- Fix Version/s: 2.1.1 > Tez View should automatically configuration settings based on http/https > policy > --- > > Key: AMBARI-12179 > URL: https://issues.apache.org/jira/browse/AMBARI-12179 > Project: Ambari > Issue Type: Bug >Reporter: Hitesh Shah >Assignee: Hitesh Shah > Fix For: 2.1.1 > > Attachments: AMBARI-12179.1.patch, AMBARI-12179.2.patch > > > The current tez view impl always defaults to the http addresses instead of > relying on the http policy setting. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12134) Update poms to target 1.7 JRE
[ https://issues.apache.org/jira/browse/AMBARI-12134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14642000#comment-14642000 ] Hudson commented on AMBARI-12134: - FAILURE: Integrated in Ambari-trunk-Commit #3171 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3171/]) AMBARI-12134: Update poms to target 1.7 JRE (Jonathan Halterman via jluniya) (jluniya: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6b3009397acbd701a2216c24d9bda53f11e528b0) * ambari-metrics/pom.xml * ambari-metrics/ambari-metrics-kafka-sink/pom.xml * ambari-server/pom.xml * ambari-metrics/ambari-metrics-timelineservice/pom.xml * pom.xml * ambari-metrics/ambari-metrics-storm-sink/pom.xml * ambari-shell/ambari-groovy-shell/pom.xml * ambari-server/src/test/java/org/apache/ambari/server/proxy/ProxyServiceTest.java * ambari-metrics/ambari-metrics-flume-sink/pom.xml * contrib/views/hive/pom.xml * ambari-project/pom.xml > Update poms to target 1.7 JRE > - > > Key: AMBARI-12134 > URL: https://issues.apache.org/jira/browse/AMBARI-12134 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.1.0 >Reporter: Jonathan Halterman >Assignee: Jayush Luniya > Fix For: 2.1.1 > > Attachments: AMBARI-12134-7.patch > > > The ambari parent pom is targeted towards Java 1.6 while ambari uses 1.7 > APIs. The ambari metrics pom is targeted at java 1.5 (by default) while > ambari-metrics uses 1.6 APIs. This causes basic compilation and test > failures, depending on how you build the projects and what tools you use to > work on them. Additionally, right now Ambari users will hit unexpected > exceptions when they execute and 1.7 code (of which there is some in > ambari-server) since the compilation target is currently 1.6. > AFAIK Ambari 2.1 and beyond are targeted at 1.7, so the Java versions in the > POMs should be updated to reflect this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12134) Update poms to target 1.7 JRE
[ https://issues.apache.org/jira/browse/AMBARI-12134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14641969#comment-14641969 ] Jayush Luniya commented on AMBARI-12134: commit 6b3009397acbd701a2216c24d9bda53f11e528b0 Author: Jayush Luniya Date: Sun Jul 26 06:49:03 2015 -0700 AMBARI-12134: Update poms to target 1.7 JRE (Jonathan Halterman via jluniya) > Update poms to target 1.7 JRE > - > > Key: AMBARI-12134 > URL: https://issues.apache.org/jira/browse/AMBARI-12134 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.1.0 >Reporter: Jonathan Halterman >Assignee: Jayush Luniya > Fix For: 2.1.1 > > Attachments: AMBARI-12134-7.patch > > > The ambari parent pom is targeted towards Java 1.6 while ambari uses 1.7 > APIs. The ambari metrics pom is targeted at java 1.5 (by default) while > ambari-metrics uses 1.6 APIs. This causes basic compilation and test > failures, depending on how you build the projects and what tools you use to > work on them. Additionally, right now Ambari users will hit unexpected > exceptions when they execute and 1.7 code (of which there is some in > ambari-server) since the compilation target is currently 1.6. > AFAIK Ambari 2.1 and beyond are targeted at 1.7, so the Java versions in the > POMs should be updated to reflect this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12134) Update poms to target 1.7 JRE
[ https://issues.apache.org/jira/browse/AMBARI-12134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14641968#comment-14641968 ] Jayush Luniya commented on AMBARI-12134: mvn clean test [INFO] [INFO] Reactor Summary: [INFO] [INFO] Ambari Main ... SUCCESS [3.251s] [INFO] Apache Ambari Project POM . SUCCESS [0.031s] [INFO] Ambari Web SUCCESS [36.674s] [INFO] Ambari Views .. SUCCESS [2.536s] [INFO] Ambari Admin View . SUCCESS [9.583s] [INFO] ambari-metrics SUCCESS [0.274s] [INFO] Ambari Metrics Common . SUCCESS [1.298s] [INFO] Ambari Metrics Hadoop Sink SUCCESS [2.973s] [INFO] Ambari Metrics Flume Sink . SUCCESS [1.645s] [INFO] Ambari Metrics Kafka Sink . SUCCESS [2.952s] [INFO] Ambari Metrics Storm Sink . SUCCESS [1.262s] [INFO] Ambari Metrics Collector .. SUCCESS [6:20.949s] [INFO] Ambari Metrics Monitor SUCCESS [1.924s] [INFO] Ambari Metrics Assembly ... SUCCESS [3:03.988s] [INFO] Ambari Server . SUCCESS [48:39.989s] [INFO] Ambari Agent .. SUCCESS [9.282s] [INFO] Ambari Client . SUCCESS [0.030s] [INFO] Ambari Python Client .. SUCCESS [0.353s] [INFO] Ambari Groovy Client .. SUCCESS [10.509s] [INFO] Ambari Shell .. SUCCESS [0.029s] [INFO] Ambari Python Shell ... SUCCESS [0.037s] [INFO] Ambari Groovy Shell ... SUCCESS [7.165s] [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 59:37.625s [INFO] Finished at: Sun Jul 26 06:30:14 PDT 2015 [INFO] Final Memory: 100M/1079M [INFO] > Update poms to target 1.7 JRE > - > > Key: AMBARI-12134 > URL: https://issues.apache.org/jira/browse/AMBARI-12134 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.1.0 >Reporter: Jonathan Halterman >Assignee: Jayush Luniya > Fix For: 2.1.1 > > Attachments: AMBARI-12134-7.patch > > > The ambari parent pom is targeted towards Java 1.6 while ambari uses 1.7 > APIs. The ambari metrics pom is targeted at java 1.5 (by default) while > ambari-metrics uses 1.6 APIs. This causes basic compilation and test > failures, depending on how you build the projects and what tools you use to > work on them. Additionally, right now Ambari users will hit unexpected > exceptions when they execute and 1.7 code (of which there is some in > ambari-server) since the compilation target is currently 1.6. > AFAIK Ambari 2.1 and beyond are targeted at 1.7, so the Java versions in the > POMs should be updated to reflect this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Review Request 35844: Update poms to target 1.7 and 1.6 JREs
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/35844/#review93042 --- Ship it! Verified on Mac mvn clean test [INFO] [INFO] Reactor Summary: [INFO] [INFO] Ambari Main ... SUCCESS [3.251s] [INFO] Apache Ambari Project POM . SUCCESS [0.031s] [INFO] Ambari Web SUCCESS [36.674s] [INFO] Ambari Views .. SUCCESS [2.536s] [INFO] Ambari Admin View . SUCCESS [9.583s] [INFO] ambari-metrics SUCCESS [0.274s] [INFO] Ambari Metrics Common . SUCCESS [1.298s] [INFO] Ambari Metrics Hadoop Sink SUCCESS [2.973s] [INFO] Ambari Metrics Flume Sink . SUCCESS [1.645s] [INFO] Ambari Metrics Kafka Sink . SUCCESS [2.952s] [INFO] Ambari Metrics Storm Sink . SUCCESS [1.262s] [INFO] Ambari Metrics Collector .. SUCCESS [6:20.949s] [INFO] Ambari Metrics Monitor SUCCESS [1.924s] [INFO] Ambari Metrics Assembly ... SUCCESS [3:03.988s] [INFO] Ambari Server . SUCCESS [48:39.989s] [INFO] Ambari Agent .. SUCCESS [9.282s] [INFO] Ambari Client . SUCCESS [0.030s] [INFO] Ambari Python Client .. SUCCESS [0.353s] [INFO] Ambari Groovy Client .. SUCCESS [10.509s] [INFO] Ambari Shell .. SUCCESS [0.029s] [INFO] Ambari Python Shell ... SUCCESS [0.037s] [INFO] Ambari Groovy Shell ... SUCCESS [7.165s] [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 59:37.625s [INFO] Finished at: Sun Jul 26 06:30:14 PDT 2015 [INFO] Final Memory: 100M/1079M [INFO] - Jayush Luniya On July 25, 2015, 3:45 p.m., Jonathan Halterman wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/35844/ > --- > > (Updated July 25, 2015, 3:45 p.m.) > > > Review request for Ambari, Jayush Luniya, Sid Wagle, and Yusaku Sako. > > > Bugs: AMBARI-12134 > https://issues.apache.org/jira/browse/AMBARI-12134 > > > Repository: ambari > > > Description > --- > > The ambari parent pom is targeted towards Java 1.6 while ambari uses 1.7 > APIs. The ambari metrics pom is targeted at java 1.5 (by default) while > ambari-metrics uses 1.6 APIs. This causes basic compilation failures, > depending on how you build the projects and what tools you use to work on > them. AFAIK Ambari 2.1 and beyond are targeted at 1.7, so the Java versions > in the POMs should be updated to reflect this. > > Aside from changing the target version for the compiler plugin, some other > dependencies had to be updated to more recent versions that support 1.7 > compilation. > > > Diffs > - > > ambari-metrics/ambari-metrics-flume-sink/pom.xml 01c2c7f > ambari-metrics/ambari-metrics-kafka-sink/pom.xml adb655b > ambari-metrics/ambari-metrics-storm-sink/pom.xml c4bc676 > ambari-metrics/ambari-metrics-timelineservice/pom.xml 999005a > ambari-metrics/pom.xml b4f4ed3 > ambari-project/pom.xml 0913bff > ambari-server/pom.xml 717d331 > > ambari-server/src/test/java/org/apache/ambari/server/proxy/ProxyServiceTest.java > ba8f01e > ambari-shell/ambari-groovy-shell/pom.xml 7d2f6da > contrib/views/hive/pom.xml 6a8a392 > pom.xml ffb4d84 > > Diff: https://reviews.apache.org/r/35844/diff/ > > > Testing > --- > > All tests pass! > > > File Attachments > > > AMBARI-12134-6.patch > > https://reviews.apache.org/media/uploaded/files/2015/07/24/8526aa86-3aa4-4fa3-8316-91dec4a1adca__AMBARI-12134-6.patch > > > Thanks, > > Jonathan Halterman > >
Re: Review Request 36800: Windows TP: Agent fails to start the Zookeeper
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36800/#review93039 --- Ship it! Ship It! - Jayush Luniya On July 24, 2015, 10:57 p.m., Florian Barca wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/36800/ > --- > > (Updated July 24, 2015, 10:57 p.m.) > > > Review request for Ambari, Artem Baranchuk, Andrew Onischuk, Eugene > Chekanskiy, and Jayush Luniya. > > > Bugs: AMBARI-12539 > https://issues.apache.org/jira/browse/AMBARI-12539 > > > Repository: ambari > > > Description > --- > > Fixed the rolling_restart parameter which Python requires in the member > method's prototype. > > > Diffs > - > > > ambari-server/src/main/resources/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/zookeeper_service.py > b983983f224d973c62c65c3ba22026e6fb101b8b > > Diff: https://reviews.apache.org/r/36800/diff/ > > > Testing > --- > > mvn clean test > > [INFO] > > [INFO] Reactor Summary: > [INFO] > [INFO] Apache Ambari Project POM .. SUCCESS [ 1.415 > s] > [INFO] Ambari Web . SUCCESS [ 47.020 > s] > [INFO] Ambari Views ... SUCCESS [ 3.042 > s] > [INFO] Ambari Admin View .. SUCCESS [ 14.339 > s] > [INFO] ambari-metrics . SUCCESS [ 0.941 > s] > [INFO] Ambari Metrics Common .. SUCCESS [ 1.859 > s] > [INFO] Ambari Metrics Hadoop Sink . SUCCESS [ 4.649 > s] > [INFO] Ambari Metrics Flume Sink .. SUCCESS [ 2.502 > s] > [INFO] Ambari Metrics Kafka Sink .. SUCCESS [ 4.771 > s] > [INFO] Ambari Metrics Storm Sink .. SUCCESS [ 3.700 > s] > [INFO] Ambari Metrics Collector ... SUCCESS [06:16 > min] > [INFO] Ambari Metrics Monitor . SUCCESS [ 3.054 > s] > [INFO] Ambari Metrics Assembly SUCCESS [02:36 > min] > [INFO] Ambari Server .. SUCCESS [02:08 > min] > [INFO] Ambari Agent ... SUCCESS [ 27.082 > s] > [INFO] Ambari Client .. SUCCESS [ 0.057 > s] > [INFO] Ambari Python Client ... SUCCESS [ 1.066 > s] > [INFO] Ambari Groovy Client ... SUCCESS [ 10.242 > s] > [INFO] Ambari Shell ... SUCCESS [ 0.036 > s] > [INFO] Ambari Python Shell SUCCESS [ 0.451 > s] > [INFO] Ambari Groovy Shell SUCCESS [ 7.209 > s] > [INFO] > > [INFO] BUILD SUCCESS > [INFO] > > [INFO] Total time: 13:15 min > [INFO] Finished at: 2015-07-24T15:54:43-07:00 > [INFO] Final Memory: 165M/1014M > [INFO] > > > > Thanks, > > Florian Barca > >
[jira] [Commented] (AMBARI-12544) Ambari server throws error while running stack-recommendations on windows
[
https://issues.apache.org/jira/browse/AMBARI-12544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14641934#comment-14641934
]
Arshad Mohammad commented on AMBARI-12544:
--
{quote}
{color:red}-1 core tests.{color} The test build failed in ambari-server
{quote}
Test case failures are not related to this patch. This patch added test case in
org.apache.ambari.server.api.services.stackadvisor.StackAdvisorRunnerTest, in
which all test cases are passing.
{quote}
Running
org.apache.ambari.server.api.services.stackadvisor.StackAdvisorRunnerTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.552 sec
{quote}
> Ambari server throws error while running stack-recommendations on windows
> -
>
> Key: AMBARI-12544
> URL: https://issues.apache.org/jira/browse/AMBARI-12544
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.1.0
> Environment: Windows
>Reporter: Arshad Mohammad
> Attachments: AMBARI-12544.patch
>
>
> Ambari server throws following error while running stack-recommendations on
> windows
> {code}
> Error message: Stack Advisor reported an error: operable program or batch
> file.
> StdOut file: \var\run\ambari-server\stack-recommendations\8\stackadvisor.out
> StdErr file: \var\run\ambari-server\stack-recommendations\8\stackadvisor.err
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
