[jira] [Commented] (AMBARI-19161) Hadoop native library location need to be changed in mapred-site.xml for PPC
[
https://issues.apache.org/jira/browse/AMBARI-19161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15738141#comment-15738141
]
Hadoop QA commented on AMBARI-19161:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842671/AMBARI-19161.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/9617//console
This message is automatically generated.
> Hadoop native library location need to be changed in mapred-site.xml for PPC
> -
>
> Key: AMBARI-19161
> URL: https://issues.apache.org/jira/browse/AMBARI-19161
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19161.patch, AMBARI-19161.patch
>
>
> ppc64le hadoop native library location to be changed to :
> /usr/hdp/2.5.0.0-1245/hadoop/lib/native/Linux-ppc64le-64/ for IBM
> We need to modify /usr/hdp/2.5.0.0-1245/hadoop/conf/mapred-site.xml
>
>
>
> FROM:
>
> mapreduce.admin.user.env
>
> LD_LIBRARY_PATH=/usr/hdp/${hdp.version}/hadoop/lib/native:/usr/hdp/${hdp.version}/hadoop/lib/native/Linux-amd64-64
>
>
> TO:
>
> mapreduce.admin.user.env
>
> LD_LIBRARY_PATH=/usr/hdp/${hdp.version}/hadoop/lib/native:/usr/hdp/${hdp.version}/hadoop/lib/native/Linux-ppc64le-64
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19156) Install Packages fails with the old stack has services removed in the new stack
[
https://issues.apache.org/jira/browse/AMBARI-19156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15738137#comment-15738137
]
Hadoop QA commented on AMBARI-19156:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842612/AMBARI-19156.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9616//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9616//console
This message is automatically generated.
> Install Packages fails with the old stack has services removed in the new
> stack
> ---
>
> Key: AMBARI-19156
> URL: https://issues.apache.org/jira/browse/AMBARI-19156
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Di Li
>Assignee: Di Li
> Attachments: AMBARI-19156.patch
>
>
> Install packages step (before RU/EU) fails with err "Cannot enumerate
> services" if the current stack has services that have been removed in the new
> stack. For example, mystack-1.0 has Spark, but mystakc-2.0 only has Spark2,
> where Spark's metainfo.xml in mystack-2.0 has the true
> section.
> Workaround is to remove Spark before attempting the install packages.
> The error is below:
> 02 Dec 2016 12:53:43,928 ERROR [ambari-client-thread-27]
> BaseManagementHandler:61 - Caught a system exception while attempting to
> create a resource: Cannot enumerate services
> org.apache.ambari.server.controller.spi.SystemException: Cannot enumerate
> services
> at
> org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.getHostVersionInstallCommand(ClusterStackVersionResourceProvider.java:606)
> at
> org.apache.ambari.server.controller.internal.ClusterStackVersionResourceProvider.createResourcesAuthorized(ClusterStackVersionResourceProvider.java:508)
> at
> org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.createResources(AbstractAuthorizedResourceProvider.java:220)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298)
> at
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
> at
> org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37)
> at
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
> at
> org.apache.ambari.server.api.services.ClusterStackVersionService.createRequests(ClusterStackVersionService.java:121)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19158) Plugin configuration ignored when directly running checkstyle goals
[
https://issues.apache.org/jira/browse/AMBARI-19158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15738078#comment-15738078
]
Hadoop QA commented on AMBARI-19158:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842618/AMBARI-19158.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9615//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9615//console
This message is automatically generated.
> Plugin configuration ignored when directly running checkstyle goals
> ---
>
> Key: AMBARI-19158
> URL: https://issues.apache.org/jira/browse/AMBARI-19158
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19158.patch
>
>
> Checkstyle uses the default checks when running {{mvn checkstyle:check}} on
> {{ambari-server}} instead of the custom list defined in
> {{ambari-server/checkstyle.xml}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19161) Hadoop native library location need to be changed in mapred-site.xml for PPC
[
https://issues.apache.org/jira/browse/AMBARI-19161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-19161:
-
Attachment: AMBARI-19161.patch
> Hadoop native library location need to be changed in mapred-site.xml for PPC
> -
>
> Key: AMBARI-19161
> URL: https://issues.apache.org/jira/browse/AMBARI-19161
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19161.patch, AMBARI-19161.patch
>
>
> ppc64le hadoop native library location to be changed to :
> /usr/hdp/2.5.0.0-1245/hadoop/lib/native/Linux-ppc64le-64/ for IBM
> We need to modify /usr/hdp/2.5.0.0-1245/hadoop/conf/mapred-site.xml
>
>
>
> FROM:
>
> mapreduce.admin.user.env
>
> LD_LIBRARY_PATH=/usr/hdp/${hdp.version}/hadoop/lib/native:/usr/hdp/${hdp.version}/hadoop/lib/native/Linux-amd64-64
>
>
> TO:
>
> mapreduce.admin.user.env
>
> LD_LIBRARY_PATH=/usr/hdp/${hdp.version}/hadoop/lib/native:/usr/hdp/${hdp.version}/hadoop/lib/native/Linux-ppc64le-64
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19161) Hadoop native library location need to be changed in mapred-site.xml for PPC
[
https://issues.apache.org/jira/browse/AMBARI-19161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-19161:
-
Status: Patch Available (was: Open)
> Hadoop native library location need to be changed in mapred-site.xml for PPC
> -
>
> Key: AMBARI-19161
> URL: https://issues.apache.org/jira/browse/AMBARI-19161
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19161.patch
>
>
> ppc64le hadoop native library location to be changed to :
> /usr/hdp/2.5.0.0-1245/hadoop/lib/native/Linux-ppc64le-64/ for IBM
> We need to modify /usr/hdp/2.5.0.0-1245/hadoop/conf/mapred-site.xml
>
>
>
> FROM:
>
> mapreduce.admin.user.env
>
> LD_LIBRARY_PATH=/usr/hdp/${hdp.version}/hadoop/lib/native:/usr/hdp/${hdp.version}/hadoop/lib/native/Linux-amd64-64
>
>
> TO:
>
> mapreduce.admin.user.env
>
> LD_LIBRARY_PATH=/usr/hdp/${hdp.version}/hadoop/lib/native:/usr/hdp/${hdp.version}/hadoop/lib/native/Linux-ppc64le-64
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19161) Hadoop native library location need to be changed in mapred-site.xml for PPC
[
https://issues.apache.org/jira/browse/AMBARI-19161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-19161:
-
Attachment: AMBARI-19161.patch
> Hadoop native library location need to be changed in mapred-site.xml for PPC
> -
>
> Key: AMBARI-19161
> URL: https://issues.apache.org/jira/browse/AMBARI-19161
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19161.patch
>
>
> ppc64le hadoop native library location to be changed to :
> /usr/hdp/2.5.0.0-1245/hadoop/lib/native/Linux-ppc64le-64/ for IBM
> We need to modify /usr/hdp/2.5.0.0-1245/hadoop/conf/mapred-site.xml
>
>
>
> FROM:
>
> mapreduce.admin.user.env
>
> LD_LIBRARY_PATH=/usr/hdp/${hdp.version}/hadoop/lib/native:/usr/hdp/${hdp.version}/hadoop/lib/native/Linux-amd64-64
>
>
> TO:
>
> mapreduce.admin.user.env
>
> LD_LIBRARY_PATH=/usr/hdp/${hdp.version}/hadoop/lib/native:/usr/hdp/${hdp.version}/hadoop/lib/native/Linux-ppc64le-64
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19161) Hadoop native library location need to be changed in mapred-site.xml for PPC
Andrew Onischuk created AMBARI-19161:
Summary: Hadoop native library location need to be changed in
mapred-site.xml for PPC
Key: AMBARI-19161
URL: https://issues.apache.org/jira/browse/AMBARI-19161
Project: Ambari
Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
Fix For: 2.5.0
Attachments: AMBARI-19161.patch
ppc64le hadoop native library location to be changed to :
/usr/hdp/2.5.0.0-1245/hadoop/lib/native/Linux-ppc64le-64/ for IBM
We need to modify /usr/hdp/2.5.0.0-1245/hadoop/conf/mapred-site.xml
FROM:
mapreduce.admin.user.env
LD_LIBRARY_PATH=/usr/hdp/${hdp.version}/hadoop/lib/native:/usr/hdp/${hdp.version}/hadoop/lib/native/Linux-amd64-64
TO:
mapreduce.admin.user.env
LD_LIBRARY_PATH=/usr/hdp/${hdp.version}/hadoop/lib/native:/usr/hdp/${hdp.version}/hadoop/lib/native/Linux-ppc64le-64
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18952) Register BackupObserver and BackupHFileCleaner
[ https://issues.apache.org/jira/browse/AMBARI-18952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-18952: Description: Over in HBASE-14417, two new classes are added. BackupHFileCleaner should be registered through hbase.master.hfilecleaner.plugins . It is responsible for keeping bulk loaded hfiles so that incremental backup can pick them up. BackupObserver should be registered through hbase.coprocessor.region.classes It is notified when bulk load completes and writes records into hbase:backup table. was: Over in HBASE-14417, two new classes are added. BackupHFileCleaner should be registered through hbase.master.hfilecleaner.plugins . It is responsible for keeping bulk loaded hfiles so that incremental backup can pick them up. BackupObserver should be registered through hbase.coprocessor.region.classes It is notified when bulk load completes and writes records into hbase:backup table. > Register BackupObserver and BackupHFileCleaner > -- > > Key: AMBARI-18952 > URL: https://issues.apache.org/jira/browse/AMBARI-18952 > Project: Ambari > Issue Type: Improvement >Reporter: Ted Yu > > Over in HBASE-14417, two new classes are added. > BackupHFileCleaner should be registered through > hbase.master.hfilecleaner.plugins . It is responsible for keeping bulk loaded > hfiles so that incremental backup can pick them up. > BackupObserver should be registered through hbase.coprocessor.region.classes > It is notified when bulk load completes and writes records into hbase:backup > table. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19160) Add ReviewBoard config file
[
https://issues.apache.org/jira/browse/AMBARI-19160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15738053#comment-15738053
]
Hadoop QA commented on AMBARI-19160:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842630/AMBARI-19160_branch-2.5.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9614//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9614//console
This message is automatically generated.
> Add ReviewBoard config file
> ---
>
> Key: AMBARI-19160
> URL: https://issues.apache.org/jira/browse/AMBARI-19160
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Trivial
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19160_branch-2.5.patch, AMBARI-19160_trunk.patch
>
>
> ReviewBoard has [command-line
> tools|https://www.reviewboard.org/docs/rbtools/] for working with review
> requests. The goal of this task is to add a small [config
> file|https://www.reviewboard.org/docs/rbtools/0.7/rbt/configuration/repositories/#reviewboardrc]
> to the Ambari project, so that {{rbt}} can talk to the right RB server
> out-of-the box.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19117) Implement Create Alerts: PORT alert configs page (step 2)
[
https://issues.apache.org/jira/browse/AMBARI-19117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15738028#comment-15738028
]
Hadoop QA commented on AMBARI-19117:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842635/AMBARI-19117.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9613//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9613//console
This message is automatically generated.
> Implement Create Alerts: PORT alert configs page (step 2)
> -
>
> Key: AMBARI-19117
> URL: https://issues.apache.org/jira/browse/AMBARI-19117
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 3.0.0
>
> Attachments: AMBARI-19117.patch, AMBARI-19117.patch,
> AMBARI-19117.patch, Step2-PORT-40% done.png
>
>
> This is a FE task to implement the "Create Alerts Wizard " based on the
> design attached.
> This task is to create Step 2 of PORT alert. see the design for details.
> Pay attention to the dependencies on selecting different options. The further
> fields will determined by the current selection.
> eg. Selecting HDP service (such as HDFS, YARN) or Custom service will display
> totally different UI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-19149) Clean up Ambari Server source code warnings
[
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15738018#comment-15738018
]
Nate Cole edited comment on AMBARI-19149 at 12/10/16 3:18 PM:
--
Rarely (I'm assuming) will developers remember to do these commands, which will
mean we'll get all these inconsistent code warnings creeping in, likely in
about a day :). I was hoping that it could be done as part of regular compile
lifecycle. The test phase is probably acceptable, but we know that not
everyone actually fully executes tests before pushing code.
was (Author: nc...@hortonworks.com):
Rarely (I'm assuming) will developers remember to do these commands, which will
mean we'll get all these inconsistent code warnings creeping in, likely in
about a day :). I was hoping that it could be done as part of regular compile
lifecycle.
> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19149-1.patch, IDEA_Ambari_v1.xml
>
>
> Eclipse's default warnings generated for {{ambari-server}} number roughly
> over 3300. Out of these, at least half of them are:
> * Unused imports
> * Type safety due to forgotten {{<>}}
> * Missing Serialization IDs from anonymous {{HashMap}} implementations
> * Unused variables
> * {{Capture}} in tests
> * {{switch}} fall-through and missing {{case statements}}: *only makes
> changes which won't affect existing functionality*
> This makes spotting actual problems, like missing {{case}} statements a
> nightmare. We need to go through and clean out as many of these warnings as
> possible.
> Note: With respect to the import cleanup, the IDE of choice should have the
> following import order setup. They should always be expanded and never use
> {{*}}.
> # {{java}}
> # {{javax}}
> # {{org}}
> # {{com}}
> # other
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19149) Clean up Ambari Server source code warnings
[
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15738018#comment-15738018
]
Nate Cole commented on AMBARI-19149:
Rarely (I'm assuming) will developers remember to do these commands, which will
mean we'll get all these inconsistent code warnings creeping in, likely in
about a day :). I was hoping that it could be done as part of regular compile
lifecycle.
> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19149-1.patch, IDEA_Ambari_v1.xml
>
>
> Eclipse's default warnings generated for {{ambari-server}} number roughly
> over 3300. Out of these, at least half of them are:
> * Unused imports
> * Type safety due to forgotten {{<>}}
> * Missing Serialization IDs from anonymous {{HashMap}} implementations
> * Unused variables
> * {{Capture}} in tests
> * {{switch}} fall-through and missing {{case statements}}: *only makes
> changes which won't affect existing functionality*
> This makes spotting actual problems, like missing {{case}} statements a
> nightmare. We need to go through and clean out as many of these warnings as
> possible.
> Note: With respect to the import cleanup, the IDE of choice should have the
> following import order setup. They should always be expanded and never use
> {{*}}.
> # {{java}}
> # {{javax}}
> # {{org}}
> # {{com}}
> # other
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19157) hive_heapsize property should not auto add m
[
https://issues.apache.org/jira/browse/AMBARI-19157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15737999#comment-15737999
]
Hadoop QA commented on AMBARI-19157:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842613/AMBARI-19157.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/9612//console
This message is automatically generated.
> hive_heapsize property should not auto add m
>
>
> Key: AMBARI-19157
> URL: https://issues.apache.org/jira/browse/AMBARI-19157
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web, stacks
>Affects Versions: 2.5.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
> Fix For: 2.5.0
>
> Attachments: AMBARI-19157.patch
>
>
> ambari web auto adds 'm' to hive_heapsize property and that leads to an extra
> m in the hive-env.sh file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19123) Update zeppelin configuration for ambari 2.5
[
https://issues.apache.org/jira/browse/AMBARI-19123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15737996#comment-15737996
]
Hadoop QA commented on AMBARI-19123:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842646/AMBARI-19123_branch-2.5-v4.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9611//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9611//console
This message is automatically generated.
> Update zeppelin configuration for ambari 2.5
>
>
> Key: AMBARI-19123
> URL: https://issues.apache.org/jira/browse/AMBARI-19123
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Prabhjyot Singh
>Assignee: Prabhjyot Singh
> Fix For: 2.5.0
>
> Attachments: AMBARI-19123_branch-2.5-v1.patch,
> AMBARI-19123_branch-2.5-v2.patch, AMBARI-19123_branch-2.5-v3.patch,
> AMBARI-19123_branch-2.5-v4.patch
>
>
> Update zeppelin configuration for ambari 2.5, and add more configuration
> template for shiro.ini
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18901) LLAP integration enhancements
[
https://issues.apache.org/jira/browse/AMBARI-18901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15737962#comment-15737962
]
Hadoop QA commented on AMBARI-18901:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842645/AMBARI-18901.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/9610//console
This message is automatically generated.
> LLAP integration enhancements
> -
>
> Key: AMBARI-18901
> URL: https://issues.apache.org/jira/browse/AMBARI-18901
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18901.patch
>
>
> The attached patch is a merged patch for all the changes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18874) Provide SSL related configurations for Ranger-Tagsync.
[ https://issues.apache.org/jira/browse/AMBARI-18874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15737941#comment-15737941 ] Hudson commented on AMBARI-18874: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #503 (See [https://builds.apache.org/job/Ambari-branch-2.5/503/]) AMBARI-18874 : Provide SSL related configurations for Ranger-Tagsync (mugdha: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=61477b9bd59a84f3e3e1486bd4b6dd7520e1400b]) * (edit) ambari-server/src/test/python/stacks/2.6/configs/ranger-admin-default.json * (add) ambari-server/src/main/resources/stacks/HDP/2.6/services/RANGER/configuration/ranger-ugsync-site.xml * (edit) ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/ranger_tagsync.py * (edit) ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/setup_ranger_xml.py * (add) ambari-server/src/main/resources/common-services/RANGER/0.7.0/configuration/ranger-tagsync-site.xml * (edit) ambari-common/src/main/python/resource_management/libraries/functions/constants.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/RANGER/metainfo.xml * (add) ambari-server/src/main/resources/stacks/HDP/2.6/services/RANGER/configuration/ranger-tagsync-site.xml * (add) ambari-server/src/test/python/stacks/2.6/RANGER/test_ranger_tagsync.py * (edit) ambari-server/src/test/python/stacks/2.6/configs/ranger-admin-secured.json * (add) ambari-server/src/main/resources/common-services/RANGER/0.7.0/metainfo.xml * (add) ambari-server/src/main/resources/common-services/RANGER/0.7.0/configuration/atlas-tagsync-ssl.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/params.py * (add) ambari-server/src/main/resources/common-services/RANGER/0.7.0/configuration/ranger-tagsync-policymgr-ssl.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/properties/stack_features.json > Provide SSL related configurations for Ranger-Tagsync. > -- > > Key: AMBARI-18874 > URL: https://issues.apache.org/jira/browse/AMBARI-18874 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.5.0 > Environment: Need to provide ssl related configurations for > Ranger-Tagsync service. >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-18874.1.patch, AMBARI-18874.2.patch, > AMBARI-18874.3.patch, AMBARI-18874.4.patch, AMBARI-18874.5.patch, > AMBARI-18874.5_branch-2.5.patch, AMBARI-18874.patch > > > Need to provide ssl related configurations for Ranger-Tagsync service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18874) Provide SSL related configurations for Ranger-Tagsync.
[ https://issues.apache.org/jira/browse/AMBARI-18874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-18874: Resolution: Fixed Status: Resolved (was: Patch Available) Committed on [trunk|https://github.com/apache/ambari/commit/646cfc681f9438ac56f4e3b864c0fd2402091082] and [branch-2.5|https://github.com/apache/ambari/commit/61477b9bd59a84f3e3e1486bd4b6dd7520e1400b] > Provide SSL related configurations for Ranger-Tagsync. > -- > > Key: AMBARI-18874 > URL: https://issues.apache.org/jira/browse/AMBARI-18874 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.5.0 > Environment: Need to provide ssl related configurations for > Ranger-Tagsync service. >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-18874.1.patch, AMBARI-18874.2.patch, > AMBARI-18874.3.patch, AMBARI-18874.4.patch, AMBARI-18874.5.patch, > AMBARI-18874.5_branch-2.5.patch, AMBARI-18874.patch > > > Need to provide ssl related configurations for Ranger-Tagsync service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18874) Provide SSL related configurations for Ranger-Tagsync.
[ https://issues.apache.org/jira/browse/AMBARI-18874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-18874: Attachment: AMBARI-18874.5_branch-2.5.patch > Provide SSL related configurations for Ranger-Tagsync. > -- > > Key: AMBARI-18874 > URL: https://issues.apache.org/jira/browse/AMBARI-18874 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.5.0 > Environment: Need to provide ssl related configurations for > Ranger-Tagsync service. >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-18874.1.patch, AMBARI-18874.2.patch, > AMBARI-18874.3.patch, AMBARI-18874.4.patch, AMBARI-18874.5.patch, > AMBARI-18874.5_branch-2.5.patch, AMBARI-18874.patch > > > Need to provide ssl related configurations for Ranger-Tagsync service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
