[jira] [Commented] (AMBARI-26006) Add Safemode and Savenamespace api's in Namenode.py
[ https://issues.apache.org/jira/browse/AMBARI-26006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17773218#comment-17773218 ] Vishal Suvagia commented on AMBARI-26006: - Hi [~hemanthboyina] , Thank-you for your interest in contributing to the Apache Ambari project. You have now been added as a contributor for the project. As a self test can you kindly try assigning the ticket to yourself. Regards Vishal. > Add Safemode and Savenamespace api's in Namenode.py > --- > > Key: AMBARI-26006 > URL: https://issues.apache.org/jira/browse/AMBARI-26006 > Project: Ambari > Issue Type: Sub-task >Reporter: Hemanth Boyina >Priority: Major > > add api's like enter_safemode. leave_safemode , savenamespace in namenode.py -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-25984) Ambari metrics summary API missing daily aggregator info
[
https://issues.apache.org/jira/browse/AMBARI-25984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17753949#comment-17753949
]
Vishal Suvagia commented on AMBARI-25984:
-
Thank-you [~arshad.mohammad] for the fix, it has been merged to
[ambari-metrics/master|https://github.com/apache/ambari-metrics/commit/2c9e5e599239d08de20b21b1b38189056337450a]
and
[ambari/branch-2.7|https://github.com/apache/ambari/commit/d9f95ec97d72a0b2b3cae1f8f4c28c0909790648].
> Ambari metrics summary API missing daily aggregator info
>
>
> Key: AMBARI-25984
> URL: https://issues.apache.org/jira/browse/AMBARI-25984
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: metrics-3.0.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Labels: pull-request-available
> Attachments: screenshot-1.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> API http://{\{HOST_PORT}}/ws/v1/timeline/metrics/summary returns following
> {noformat}
> {
> "timestamp": 1691405233095,
> "metadata": {
> "timeline_metric_store_watcher": "2",
> "datanode": "329",
> "HOST": "154",
> "jobhistoryserver": "67",
> "namenode": "457",
> "ambari_server": "79",
> "hiveserver2": "116",
> "amssmoketestfake": "2",
> "hivemetastore": "438",
> "resourcemanager": "257",
> "Number of Hosts": "7",
> "applicationhistoryserver": "108",
> "nodemanager": "366",
> "hbase": "1950",
> "ams-hbase": "5583"
> },
> "aggregation": {
> "TimelineMetricHostAggregatorHourly": "Mon Aug 07 09:00:00 GMT 2023",
> "TimelineMetricHostAggregatorMinute": "Mon Aug 07 10:45:00 GMT 2023",
> "TimelineClusterAggregatorSecond": "Mon Aug 07 10:46:00 GMT 2023",
> "TimelineClusterAggregatorMinute": "Mon Aug 07 10:45:00 GMT 2023",
> "TimelineClusterAggregatorHourly": "Mon Aug 07 09:00:00 GMT 2023"
> }
> }
> {noformat}
> In above aggregation information TimelineMetricHostAggregatorDaily and
> TimelineClusterAggregatorDaily are missing. Summary API should return these
> aggregation detail also.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-25950) Exclude hosts getting erased when RM, NN are restarted
[ https://issues.apache.org/jira/browse/AMBARI-25950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17732901#comment-17732901 ] Vishal Suvagia commented on AMBARI-25950: - Thank-you [~dmmkr] for the sharing the approaches after quite good enough research. The approach #2 looks fine as the commmand params are only added during stages and not while publishing at the end. [~brahmareddy], [~vjasani] / [~eub] any thoughts ? > Exclude hosts getting erased when RM, NN are restarted > -- > > Key: AMBARI-25950 > URL: https://issues.apache.org/jira/browse/AMBARI-25950 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: D M Murali Krishna Reddy >Assignee: D M Murali Krishna Reddy >Priority: Major > > After decommissioning a Node Manager or a Data node, if Resource Manager or > Namenode are restarted, the exclude hosts file is getting overwritten with > empty contents, causing the NM, DN to get recommisioned. > > During NN, RM restart all_decommissioned_hosts is not set due to which in > params_linux.py the exclude hosts file is getting created with empty content. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-25911) Ambari fails to capture Hive Metastore alerts when HMS is critical or goes OOM
Vishal Suvagia created AMBARI-25911: --- Summary: Ambari fails to capture Hive Metastore alerts when HMS is critical or goes OOM Key: AMBARI-25911 URL: https://issues.apache.org/jira/browse/AMBARI-25911 Project: Ambari Issue Type: Improvement Components: alerts Affects Versions: 2.7.7 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.7.8 Ambari fails to capture Hive Metastore alerts when HMS is critical or goes OOM. Thus rendering the alert check ineffective. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25851) Need to update com.fasterxml.jackson.core :jackson-databind dependency
[ https://issues.apache.org/jira/browse/AMBARI-25851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-25851: Attachment: AMBARI-25851.patch > Need to update com.fasterxml.jackson.core :jackson-databind dependency > -- > > Key: AMBARI-25851 > URL: https://issues.apache.org/jira/browse/AMBARI-25851 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent, ambari-server, contrib, metrics >Affects Versions: 2.7.7 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.7.8 > > Attachments: AMBARI-25851.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Need to update com.fasterxml.jackson.core :jackson-databind dependency -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25851) Need to update com.fasterxml.jackson.core :jackson-databind dependency
[ https://issues.apache.org/jira/browse/AMBARI-25851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-25851: Status: Patch Available (was: In Progress) > Need to update com.fasterxml.jackson.core :jackson-databind dependency > -- > > Key: AMBARI-25851 > URL: https://issues.apache.org/jira/browse/AMBARI-25851 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent, ambari-server, contrib, metrics >Affects Versions: 2.7.7 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.7.8 > > Attachments: AMBARI-25851.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Need to update com.fasterxml.jackson.core :jackson-databind dependency -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-25851) Need to update com.fasterxml.jackson.core :jackson-databind dependency
Vishal Suvagia created AMBARI-25851: --- Summary: Need to update com.fasterxml.jackson.core :jackson-databind dependency Key: AMBARI-25851 URL: https://issues.apache.org/jira/browse/AMBARI-25851 Project: Ambari Issue Type: Improvement Components: ambari-agent, ambari-server, contrib, metrics Affects Versions: 2.7.7 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.7.8 Need to update com.fasterxml.jackson.core :jackson-databind dependency -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25850) Need to update com.h2database:h2 dependency
[ https://issues.apache.org/jira/browse/AMBARI-25850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-25850: Status: Patch Available (was: In Progress) > Need to update com.h2database:h2 dependency > --- > > Key: AMBARI-25850 > URL: https://issues.apache.org/jira/browse/AMBARI-25850 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.7.7 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.7.8 > > Attachments: AMBARI-25850.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Need to update com.h2database:h2 dependency -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25850) Need to update com.h2database:h2 dependency
[ https://issues.apache.org/jira/browse/AMBARI-25850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-25850: Attachment: AMBARI-25850.patch > Need to update com.h2database:h2 dependency > --- > > Key: AMBARI-25850 > URL: https://issues.apache.org/jira/browse/AMBARI-25850 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.7.7 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.7.8 > > Attachments: AMBARI-25850.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Need to update com.h2database:h2 dependency -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-25850) Need to update com.h2database:h2 dependency
Vishal Suvagia created AMBARI-25850: --- Summary: Need to update com.h2database:h2 dependency Key: AMBARI-25850 URL: https://issues.apache.org/jira/browse/AMBARI-25850 Project: Ambari Issue Type: Improvement Components: ambari-server Affects Versions: 2.7.7 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.7.8 Need to update com.h2database:h2 dependency -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25849) Need to update org.jboss.netty: netty dependency
[ https://issues.apache.org/jira/browse/AMBARI-25849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-25849: Status: Patch Available (was: In Progress) > Need to update org.jboss.netty: netty dependency > > > Key: AMBARI-25849 > URL: https://issues.apache.org/jira/browse/AMBARI-25849 > Project: Ambari > Issue Type: Improvement > Components: metrics >Affects Versions: 2.7.7 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.7.8 > > Attachments: AMBARI-25849.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Need to update org.jboss.netty: netty dependency -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25849) Need to update org.jboss.netty: netty dependency
[ https://issues.apache.org/jira/browse/AMBARI-25849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-25849: Attachment: AMBARI-25849.patch > Need to update org.jboss.netty: netty dependency > > > Key: AMBARI-25849 > URL: https://issues.apache.org/jira/browse/AMBARI-25849 > Project: Ambari > Issue Type: Improvement > Components: metrics >Affects Versions: 2.7.7 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.7.8 > > Attachments: AMBARI-25849.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Need to update org.jboss.netty: netty dependency -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-25849) Need to update org.jboss.netty: netty dependency
Vishal Suvagia created AMBARI-25849: --- Summary: Need to update org.jboss.netty: netty dependency Key: AMBARI-25849 URL: https://issues.apache.org/jira/browse/AMBARI-25849 Project: Ambari Issue Type: Improvement Components: metrics Affects Versions: 2.7.7 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.7.8 Need to update org.jboss.netty: netty dependency -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25848) Need to update org.codehaus.jackson:jackson-mapper-asl dependency
[ https://issues.apache.org/jira/browse/AMBARI-25848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-25848: Attachment: AMBARI-25848.patch > Need to update org.codehaus.jackson:jackson-mapper-asl dependency > - > > Key: AMBARI-25848 > URL: https://issues.apache.org/jira/browse/AMBARI-25848 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent, ambari-metrics, ambari-server, contrib >Affects Versions: 2.7.7 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.7.8 > > Attachments: AMBARI-25848.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Need to update org.codehaus.jackson:jackson-mapper-asl dependency -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25848) Need to update org.codehaus.jackson:jackson-mapper-asl dependency
[ https://issues.apache.org/jira/browse/AMBARI-25848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-25848: Status: Patch Available (was: In Progress) > Need to update org.codehaus.jackson:jackson-mapper-asl dependency > - > > Key: AMBARI-25848 > URL: https://issues.apache.org/jira/browse/AMBARI-25848 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent, ambari-metrics, ambari-server, contrib >Affects Versions: 2.7.7 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.7.8 > > Attachments: AMBARI-25848.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Need to update org.codehaus.jackson:jackson-mapper-asl dependency -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-25848) Need to update org.codehaus.jackson:jackson-mapper-asl dependency
Vishal Suvagia created AMBARI-25848: --- Summary: Need to update org.codehaus.jackson:jackson-mapper-asl dependency Key: AMBARI-25848 URL: https://issues.apache.org/jira/browse/AMBARI-25848 Project: Ambari Issue Type: Improvement Components: ambari-agent, ambari-metrics, ambari-server, contrib Affects Versions: 2.7.7 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.7.8 Need to update org.codehaus.jackson:jackson-mapper-asl dependency -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25847) Need to update log4j:log4j dependency
[ https://issues.apache.org/jira/browse/AMBARI-25847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-25847: Status: Patch Available (was: In Progress) > Need to update log4j:log4j dependency > - > > Key: AMBARI-25847 > URL: https://issues.apache.org/jira/browse/AMBARI-25847 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent, contrib, metrics >Affects Versions: 2.7.7 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.7.8 > > Attachments: AMBARI-25847.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Need to update log4j:log4j dependency -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25847) Need to update log4j:log4j dependency
[ https://issues.apache.org/jira/browse/AMBARI-25847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-25847: Attachment: AMBARI-25847.patch > Need to update log4j:log4j dependency > - > > Key: AMBARI-25847 > URL: https://issues.apache.org/jira/browse/AMBARI-25847 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent, contrib, metrics >Affects Versions: 2.7.7 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.7.8 > > Attachments: AMBARI-25847.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Need to update log4j:log4j dependency -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-25847) Need to update log4j:log4j dependency
Vishal Suvagia created AMBARI-25847: --- Summary: Need to update log4j:log4j dependency Key: AMBARI-25847 URL: https://issues.apache.org/jira/browse/AMBARI-25847 Project: Ambari Issue Type: Improvement Components: ambari-agent, contrib, metrics Affects Versions: 2.7.7 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.7.8 Need to update log4j:log4j dependency -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25846) Need to update net.sf.ehcache:ehcache dependency
[ https://issues.apache.org/jira/browse/AMBARI-25846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-25846: Status: Patch Available (was: In Progress) > Need to update net.sf.ehcache:ehcache dependency > > > Key: AMBARI-25846 > URL: https://issues.apache.org/jira/browse/AMBARI-25846 > Project: Ambari > Issue Type: Improvement > Components: ambari-server, metrics >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Attachments: AMBARI-25846.patch > > > Need to update net.sf.ehcache:ehcache dependency -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25846) Need to update net.sf.ehcache:ehcache dependency
[ https://issues.apache.org/jira/browse/AMBARI-25846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-25846: Attachment: AMBARI-25846.patch > Need to update net.sf.ehcache:ehcache dependency > > > Key: AMBARI-25846 > URL: https://issues.apache.org/jira/browse/AMBARI-25846 > Project: Ambari > Issue Type: Improvement > Components: ambari-server, metrics >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Attachments: AMBARI-25846.patch > > > Need to update net.sf.ehcache:ehcache dependency -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-25846) Need to update net.sf.ehcache:ehcache dependency
Vishal Suvagia created AMBARI-25846: --- Summary: Need to update net.sf.ehcache:ehcache dependency Key: AMBARI-25846 URL: https://issues.apache.org/jira/browse/AMBARI-25846 Project: Ambari Issue Type: Improvement Components: ambari-server, metrics Reporter: Vishal Suvagia Assignee: Vishal Suvagia Need to update net.sf.ehcache:ehcache dependency -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25845) Need to update io.netty:netty dependency
[ https://issues.apache.org/jira/browse/AMBARI-25845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-25845: Status: Patch Available (was: In Progress) > Need to update io.netty:netty dependency > > > Key: AMBARI-25845 > URL: https://issues.apache.org/jira/browse/AMBARI-25845 > Project: Ambari > Issue Type: Improvement > Components: ambari-server, metrics >Affects Versions: 2.7.7 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.7.8 > > Attachments: AMBARI-25845.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Need to update io.netty:netty dependency -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25845) Need to update io.netty:netty dependency
[ https://issues.apache.org/jira/browse/AMBARI-25845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-25845: Attachment: AMBARI-25845.patch > Need to update io.netty:netty dependency > > > Key: AMBARI-25845 > URL: https://issues.apache.org/jira/browse/AMBARI-25845 > Project: Ambari > Issue Type: Improvement > Components: ambari-server, metrics >Affects Versions: 2.7.7 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.7.8 > > Attachments: AMBARI-25845.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Need to update io.netty:netty dependency -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-25845) Need to update io.netty:netty dependency
Vishal Suvagia created AMBARI-25845: --- Summary: Need to update io.netty:netty dependency Key: AMBARI-25845 URL: https://issues.apache.org/jira/browse/AMBARI-25845 Project: Ambari Issue Type: Improvement Components: ambari-server, metrics Affects Versions: 2.7.7 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.7.8 Need to update io.netty:netty dependency -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25844) Need to update commons-collection dependency
[ https://issues.apache.org/jira/browse/AMBARI-25844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-25844: Status: Patch Available (was: In Progress) > Need to update commons-collection dependency > > > Key: AMBARI-25844 > URL: https://issues.apache.org/jira/browse/AMBARI-25844 > Project: Ambari > Issue Type: Improvement > Components: ambari-server, metrics >Affects Versions: 2.7.7 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.7.8 > > Attachments: AMBARI-25844.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Need to update commons-collection dependency -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25844) Need to update commons-collection dependency
[ https://issues.apache.org/jira/browse/AMBARI-25844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-25844: Attachment: AMBARI-25844.patch > Need to update commons-collection dependency > > > Key: AMBARI-25844 > URL: https://issues.apache.org/jira/browse/AMBARI-25844 > Project: Ambari > Issue Type: Improvement > Components: ambari-server, metrics >Affects Versions: 2.7.7 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.7.8 > > Attachments: AMBARI-25844.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Need to update commons-collection dependency -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-25844) Need to update commons-collection dependency
Vishal Suvagia created AMBARI-25844: --- Summary: Need to update commons-collection dependency Key: AMBARI-25844 URL: https://issues.apache.org/jira/browse/AMBARI-25844 Project: Ambari Issue Type: Improvement Components: ambari-server, metrics Affects Versions: 2.7.7 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.7.8 Need to update commons-collection dependency -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25843) Update Zookeeper version in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-25843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-25843: Attachment: AMBARI-25843-branch-2.7.7.patch > Update Zookeeper version in Ambari > -- > > Key: AMBARI-25843 > URL: https://issues.apache.org/jira/browse/AMBARI-25843 > Project: Ambari > Issue Type: Improvement > Components: ambari-infra, ambari-logsearch, ambari-metrics >Affects Versions: 2.7.8 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.7.8 > > Attachments: AMBARI-25843-branch-2.7.7.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Need to update zookeeper version in Ambari -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25843) Update Zookeeper version in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-25843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-25843: Status: Patch Available (was: In Progress) > Update Zookeeper version in Ambari > -- > > Key: AMBARI-25843 > URL: https://issues.apache.org/jira/browse/AMBARI-25843 > Project: Ambari > Issue Type: Improvement > Components: ambari-infra, ambari-logsearch, ambari-metrics >Affects Versions: 2.7.8 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.7.8 > > Attachments: AMBARI-25843-branch-2.7.7.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Need to update zookeeper version in Ambari -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-25843) Update Zookeeper version in Ambari
Vishal Suvagia created AMBARI-25843: --- Summary: Update Zookeeper version in Ambari Key: AMBARI-25843 URL: https://issues.apache.org/jira/browse/AMBARI-25843 Project: Ambari Issue Type: Improvement Components: ambari-infra, ambari-logsearch, ambari-metrics Affects Versions: 2.7.8 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.7.8 Need to update zookeeper version in Ambari -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25842) Update Angular version in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-25842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-25842: Status: Patch Available (was: In Progress) Request to kindly review the patch. > Update Angular version in Ambari > - > > Key: AMBARI-25842 > URL: https://issues.apache.org/jira/browse/AMBARI-25842 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: 2.7.8 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.7.8 > > Attachments: AMBARI-25842--branch-2.7.7.patch, > AMBARI-25842--trunk.patch > > Time Spent: 20m > Remaining Estimate: 0h > > Angluar version in Ambari admin-web needs to be updated. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25842) Update Angular version in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-25842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-25842: Attachment: AMBARI-25842--branch-2.7.7.patch AMBARI-25842--trunk.patch > Update Angular version in Ambari > - > > Key: AMBARI-25842 > URL: https://issues.apache.org/jira/browse/AMBARI-25842 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: 2.7.8 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.7.8 > > Attachments: AMBARI-25842--branch-2.7.7.patch, > AMBARI-25842--trunk.patch > > Time Spent: 20m > Remaining Estimate: 0h > > Angluar version in Ambari admin-web needs to be updated. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-25842) Update Angular version in Ambari
Vishal Suvagia created AMBARI-25842: --- Summary: Update Angular version in Ambari Key: AMBARI-25842 URL: https://issues.apache.org/jira/browse/AMBARI-25842 Project: Ambari Issue Type: Improvement Components: ambari-web Affects Versions: 2.7.8 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.7.8 Angluar version in Ambari admin-web needs to be updated. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-25759) Need to update UI libraries and framework
Vishal Suvagia created AMBARI-25759: --- Summary: Need to update UI libraries and framework Key: AMBARI-25759 URL: https://issues.apache.org/jira/browse/AMBARI-25759 Project: Ambari Issue Type: Improvement Components: ambari-web Affects Versions: 2.7.7 Reporter: Vishal Suvagia Fix For: 2.7.7 Need to revisit and update UI libraries and framework -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-25754) Ambari server build is failing due to checkstyle issues
Vishal Suvagia created AMBARI-25754: --- Summary: Ambari server build is failing due to checkstyle issues Key: AMBARI-25754 URL: https://issues.apache.org/jira/browse/AMBARI-25754 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0, 2.7.7 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 3.0.0, 2.7.7 Ambari compilation fails due to unused imports need to remove the unused imports. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-25734) CLUSTER.USER is able to perform actions on service through API calls
[
https://issues.apache.org/jira/browse/AMBARI-25734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17607028#comment-17607028
]
Vishal Suvagia commented on AMBARI-25734:
-
Thank-you [~satheeshakuthota] for reporting the issue, I will try to debug and
fix the issue.
> CLUSTER.USER is able to perform actions on service through API calls
>
>
> Key: AMBARI-25734
> URL: https://issues.apache.org/jira/browse/AMBARI-25734
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.6
>Reporter: Satheesh Akuthota
>Assignee: Vishal Suvagia
>Priority: Major
> Attachments: Screenshot 2022-09-15 at 3.48.19 PM.png
>
>
> Hi Team ,
> CLUSTER.USER is able to perform actions on services (eg . maintenance off/on
> on ambari_mertrics)
>
> [http://abcserver:8080/api/v1/clusters/CERTIFICATION/services/AMBARI_METRICS]
> request:
> {code:java}
> {
> "ServiceInfo" : {
> "maintenance_state" : "OFF"
> }
> }
> {code}
> user previlege details :
> {code:java}
> {
> "href" : "http://hostservername:8080/api/v1/users/svcambaritest4/;,
> "Users" : {
> "active" : true,
> "admin" : false,
> "consecutive_failures" : 0,
> "created" : 1663235359782,
> "display_name" : "svcambaritest4",
> "groups" : [ ],
> "ldap_user" : false,
> "local_user_name" : "svcambaritest4",
> "user_name" : "svcambaritest4",
> "user_type" : "LOCAL"
> },
> "widget_layouts" : [ ],
> "privileges" : [
> {
> "href" :
> "http://hostservername:8080/api/v1/users/svcambaritest4/privileges/4;,
> "PrivilegeInfo" : {
> "privilege_id" : 4,
> "user_name" : "svcambaritest4"
> }
> }
> ],
> "sources" : [
> {
> "href" :
> "http://hostservername:8080/api/v1/users/svcambaritest4/sources/4;,
> "AuthenticationSourceInfo" : {
> "source_id" : 4,
> "user_name" : "svcambaritest4"
> }
> }
> ]
> }
> {code}
> {code:java}
> {
> "href" :
> "http://sserverhostname:8080/api/v1/users/svcambaritest4/privileges/4;,
> "PrivilegeInfo" : {
> "cluster_name" : "CLUSTERNAME",
> "permission_label" : "Cluster User",
> "permission_name" : "CLUSTER.USER",
> "principal_name" : "svcambaritest4",
> "principal_type" : "USER",
> "privilege_id" : 4,
> "type" : "CLUSTER",
> "user_name" : "svcambaritest4"
> }
> }
> {code}
> Note : From UI we are not able to do this action
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Assigned] (AMBARI-25734) CLUSTER.USER is able to perform actions on service through API calls
[
https://issues.apache.org/jira/browse/AMBARI-25734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia reassigned AMBARI-25734:
---
Assignee: Vishal Suvagia
> CLUSTER.USER is able to perform actions on service through API calls
>
>
> Key: AMBARI-25734
> URL: https://issues.apache.org/jira/browse/AMBARI-25734
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.6
>Reporter: Satheesh Akuthota
>Assignee: Vishal Suvagia
>Priority: Major
> Attachments: Screenshot 2022-09-15 at 3.48.19 PM.png
>
>
> Hi Team ,
> CLUSTER.USER is able to perform actions on services (eg . maintenance off/on
> on ambari_mertrics)
>
> [http://abcserver:8080/api/v1/clusters/CERTIFICATION/services/AMBARI_METRICS]
> request:
> {code:java}
> {
> "ServiceInfo" : {
> "maintenance_state" : "OFF"
> }
> }
> {code}
> user previlege details :
> {code:java}
> {
> "href" : "http://hostservername:8080/api/v1/users/svcambaritest4/;,
> "Users" : {
> "active" : true,
> "admin" : false,
> "consecutive_failures" : 0,
> "created" : 1663235359782,
> "display_name" : "svcambaritest4",
> "groups" : [ ],
> "ldap_user" : false,
> "local_user_name" : "svcambaritest4",
> "user_name" : "svcambaritest4",
> "user_type" : "LOCAL"
> },
> "widget_layouts" : [ ],
> "privileges" : [
> {
> "href" :
> "http://hostservername:8080/api/v1/users/svcambaritest4/privileges/4;,
> "PrivilegeInfo" : {
> "privilege_id" : 4,
> "user_name" : "svcambaritest4"
> }
> }
> ],
> "sources" : [
> {
> "href" :
> "http://hostservername:8080/api/v1/users/svcambaritest4/sources/4;,
> "AuthenticationSourceInfo" : {
> "source_id" : 4,
> "user_name" : "svcambaritest4"
> }
> }
> ]
> }
> {code}
> {code:java}
> {
> "href" :
> "http://sserverhostname:8080/api/v1/users/svcambaritest4/privileges/4;,
> "PrivilegeInfo" : {
> "cluster_name" : "CLUSTERNAME",
> "permission_label" : "Cluster User",
> "permission_name" : "CLUSTER.USER",
> "principal_name" : "svcambaritest4",
> "principal_type" : "USER",
> "privilege_id" : 4,
> "type" : "CLUSTER",
> "user_name" : "svcambaritest4"
> }
> }
> {code}
> Note : From UI we are not able to do this action
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-25168) Need to add stack feature constant for kafka-ranger-env.sh removal
[ https://issues.apache.org/jira/browse/AMBARI-25168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia resolved AMBARI-25168. - Resolution: Fixed Committed to Apache [trunk|https://github.com/apache/ambari/commit/5f86977297dfe7a17cc64c7bfacd7fa3d5725b4e] and [branch-2.7|https://github.com/apache/ambari/commit/0c931a1874c7bee1137ebcffa07030e84e003d3e]. > Need to add stack feature constant for kafka-ranger-env.sh removal > -- > > Key: AMBARI-25168 > URL: https://issues.apache.org/jira/browse/AMBARI-25168 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.4 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.7.4 > > > As part of recent fixes in Kafka-2.1, requires removal of kafka-ranger-env.sh > script to be set or executed from the kafka-env.sh script. hence need to add > a stack feature constant to support the feature. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25168) Need to add stack feature constant for kafka-ranger-env.sh removal
Vishal Suvagia created AMBARI-25168: --- Summary: Need to add stack feature constant for kafka-ranger-env.sh removal Key: AMBARI-25168 URL: https://issues.apache.org/jira/browse/AMBARI-25168 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.4 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.7.4 As part of recent fixes in Kafka-2.1, requires removal of kafka-ranger-env.sh script to be set or executed from the kafka-env.sh script. hence need to add a stack feature constant to support the feature. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24886) Add stack feature constant to support Ranger admin users password change
[ https://issues.apache.org/jira/browse/AMBARI-24886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia resolved AMBARI-24886. - Resolution: Fixed Merged in Apache [trunk|https://github.com/apache/ambari/commit/52384fb8e703f7c1c99cc64a3e8e3526cca56b6d] and [branch-2.7|https://github.com/apache/ambari/commit/bf43705dda5640ad37b8b1030af5ebd40fc4c782] branch. > Add stack feature constant to support Ranger admin users password change > > > Key: AMBARI-24886 > URL: https://issues.apache.org/jira/browse/AMBARI-24886 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.3 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 3.5h > Remaining Estimate: 0h > > Current Ambari stack for Ranger supports feature to change Ranger admin users > passwords through multiple calls. Ranger now supports ability to change all > admin users passwords in one call. Need to add stack feature support for the > same. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24886) Add stack feature constant to support Ranger admin users password change
Vishal Suvagia created AMBARI-24886: --- Summary: Add stack feature constant to support Ranger admin users password change Key: AMBARI-24886 URL: https://issues.apache.org/jira/browse/AMBARI-24886 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.3 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.7.3 Current Ambari stack for Ranger supports feature to change Ranger admin users passwords through multiple calls. Ranger now supports ability to change all admin users passwords in one call. Need to add stack feature support for the same. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24716) Restrict user permissions for Atlas configuration file
[ https://issues.apache.org/jira/browse/AMBARI-24716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-24716: Affects Version/s: 2.6.1 > Restrict user permissions for Atlas configuration file > -- > > Key: AMBARI-24716 > URL: https://issues.apache.org/jira/browse/AMBARI-24716 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Need to restrict user permissions for Atlas configuration file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24716) Restrict user permissions for Atlas configuration file
[ https://issues.apache.org/jira/browse/AMBARI-24716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-24716: Affects Version/s: (was: 2.6.1) > Restrict user permissions for Atlas configuration file > -- > > Key: AMBARI-24716 > URL: https://issues.apache.org/jira/browse/AMBARI-24716 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Need to restrict user permissions for Atlas configuration file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24716) Restrict user permissions for Atlas configuration file
[ https://issues.apache.org/jira/browse/AMBARI-24716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia resolved AMBARI-24716. - Resolution: Fixed Fix Version/s: (was: 2.6.2) Merged in branch-2.7 via [pull request 2419|https://github.com/apache/ambari/pull/2419]. Dropping [pull request 2420|https://github.com/apache/ambari/pull/2420] for branch-2.6. > Restrict user permissions for Atlas configuration file > -- > > Key: AMBARI-24716 > URL: https://issues.apache.org/jira/browse/AMBARI-24716 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Need to restrict user permissions for Atlas configuration file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24716) Restrict user permissions for Atlas configuration file
[ https://issues.apache.org/jira/browse/AMBARI-24716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-24716: Affects Version/s: (was: 2.6.1) > Restrict user permissions for Atlas configuration file > -- > > Key: AMBARI-24716 > URL: https://issues.apache.org/jira/browse/AMBARI-24716 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Need to restrict user permissions for Atlas configuration file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24716) Restrict user permissions for Atlas configuration file
[ https://issues.apache.org/jira/browse/AMBARI-24716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-24716: Fix Version/s: 2.6.2 > Restrict user permissions for Atlas configuration file > -- > > Key: AMBARI-24716 > URL: https://issues.apache.org/jira/browse/AMBARI-24716 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.1, 2.7.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.6.2, 2.7.2 > > > Need to restrict user permissions for Atlas configuration file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24716) Restrict user permissions for Atlas configuration file
[ https://issues.apache.org/jira/browse/AMBARI-24716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-24716: Affects Version/s: (was: 2.7.1) > Restrict user permissions for Atlas configuration file > -- > > Key: AMBARI-24716 > URL: https://issues.apache.org/jira/browse/AMBARI-24716 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.1, 2.7.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.7.2 > > > Need to restrict user permissions for Atlas configuration file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24716) Restrict user permissions for Atlas configuration file
[ https://issues.apache.org/jira/browse/AMBARI-24716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-24716: Affects Version/s: 2.6.1 > Restrict user permissions for Atlas configuration file > -- > > Key: AMBARI-24716 > URL: https://issues.apache.org/jira/browse/AMBARI-24716 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.1, 2.7.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.7.2 > > > Need to restrict user permissions for Atlas configuration file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24716) Restrict user permissions for Atlas configuration file
Vishal Suvagia created AMBARI-24716: --- Summary: Restrict user permissions for Atlas configuration file Key: AMBARI-24716 URL: https://issues.apache.org/jira/browse/AMBARI-24716 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.0, 2.7.1 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.7.2 Need to restrict user permissions for Atlas configuration file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-24199) Fix Atlas HA support in Ambari via blueprint deployment
[
https://issues.apache.org/jira/browse/AMBARI-24199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia reassigned AMBARI-24199:
---
Assignee: Robert Nettleton (was: Vishal Suvagia)
> Fix Atlas HA support in Ambari via blueprint deployment
> ---
>
> Key: AMBARI-24199
> URL: https://issues.apache.org/jira/browse/AMBARI-24199
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Vishal Suvagia
>Assignee: Robert Nettleton
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Currently deploying Atlas in HA mode via blueprint is not possible due to
> property
> [{{atlas.server.bind.address}}|https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java#L3156]
> being set by Blueprint Processor, need to remove the property from being
> processed in Blueprint Processor and let the default value to be effective.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24199) Fix Atlas HA support in Ambari via blueprint deployment
Vishal Suvagia created AMBARI-24199:
---
Summary: Fix Atlas HA support in Ambari via blueprint deployment
Key: AMBARI-24199
URL: https://issues.apache.org/jira/browse/AMBARI-24199
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Vishal Suvagia
Assignee: Vishal Suvagia
Fix For: 2.7.0
Currently deploying Atlas in HA mode via blueprint is not possible due to
property
[{{atlas.server.bind.address}}|https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java#L3156]
being set by Blueprint Processor, need to remove the property from being
processed in Blueprint Processor and let the default value to be effective.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-23864) Need to add new property for Ranger-Tagsync when enabling federation for Namenode-HA via Blueprints
[
https://issues.apache.org/jira/browse/AMBARI-23864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia resolved AMBARI-23864.
-
Resolution: Fixed
committed to
[trunk|https://github.com/apache/ambari/commit/e2ce601032d2dd1f047793aa51d749749017774b].
> Need to add new property for Ranger-Tagsync when enabling federation for
> Namenode-HA via Blueprints
> ---
>
> Key: AMBARI-23864
> URL: https://issues.apache.org/jira/browse/AMBARI-23864
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> Need to dynamically add properties in config-type {{ranger-tagsync-site}}
> when cluster is being setup via blueprint . This should be done when Atlas
> and Ranger-Tagsync service is installed.
> When federation is Enabled for HDFS, in this case for each name-service, we
> will need to add a property in config-type {{ranger-tagsync-site}} using
> below format:
> {noformat}ranger.tagsync.atlas.hdfs.instance..nameservice..ranger.service=
> {noformat}
> The Ranger service name can be derived from logic as below:
> If the value for property {{ranger.plugin.hdfs.service.name}} is default i.e.
> repo_name then the value for above property will be in the format:
> {noformat}_hadoop_{noformat}
> for e.g if the cluster-name is {{testcl1}} and the name-services are {{ns1}}
> , {{ns2}} and the {{ranger.plugin.hdfs.service.name}} has value
> repo_name then the property-value will be as below:
> ranger.tagsync.atlas.hdfs.instance.testcl1.nameservice.ns1.ranger.service=testcl1_hadoop_ns1
> ranger.tagsync.atlas.hdfs.instance.testcl1.nameservice.ns2.ranger.service=testcl1_hadoop_ns2
> If the user has a custom-value for the property
> {{ranger.plugin.hdfs.service.name}} i.e. not repo_name, then we will
> need to use the value provided in for property
> {{ranger.plugin.hdfs.service.name}} and use the format as
> _.
> for e.g if the cluster-name is {{testcl1}} and the name-services are {{ns1}}
> , {{ns2}} and the {{ranger.plugin.hdfs.service.name}} has value
> {{hadoop_service}} then the property-value will be as below:
> ranger.tagsync.atlas.hdfs.instance.testcl1.nameservice.ns1.ranger.service=hadoop_service_ns1
> ranger.tagsync.atlas.hdfs.instance.testcl1.nameservice.ns2.ranger.service=hadoop_service_ns2
> PS : Related NN-Federation UI-wizard changes are already handled in
> AMBARI-23424, This issue is created to handle addition of properties via
> blueprint.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23864) Need to add new property for Ranger-Tagsync when enabling federation for Namenode-HA via Blueprints
Vishal Suvagia created AMBARI-23864:
---
Summary: Need to add new property for Ranger-Tagsync when enabling
federation for Namenode-HA via Blueprints
Key: AMBARI-23864
URL: https://issues.apache.org/jira/browse/AMBARI-23864
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Vishal Suvagia
Assignee: Vishal Suvagia
Fix For: 2.7.0
Need to dynamically add properties in config-type {{ranger-tagsync-site}} when
cluster is being setup via blueprint . This should be done when Atlas and
Ranger-Tagsync service is installed.
When federation is Enabled for HDFS, in this case for each name-service, we
will need to add a property in config-type {{ranger-tagsync-site}} using below
format:
{noformat}ranger.tagsync.atlas.hdfs.instance..nameservice..ranger.service=
{noformat}
The Ranger service name can be derived from logic as below:
If the value for property {{ranger.plugin.hdfs.service.name}} is default i.e.
repo_name then the value for above property will be in the format:
{noformat}_hadoop_{noformat}
for e.g if the cluster-name is {{testcl1}} and the name-services are {{ns1}} ,
{{ns2}} and the {{ranger.plugin.hdfs.service.name}} has value repo_name
then the property-value will be as below:
ranger.tagsync.atlas.hdfs.instance.testcl1.nameservice.ns1.ranger.service=testcl1_hadoop_ns1
ranger.tagsync.atlas.hdfs.instance.testcl1.nameservice.ns2.ranger.service=testcl1_hadoop_ns2
If the user has a custom-value for the property
{{ranger.plugin.hdfs.service.name}} i.e. not repo_name, then we will
need to use the value provided in for property
{{ranger.plugin.hdfs.service.name}} and use the format as
_.
for e.g if the cluster-name is {{testcl1}} and the name-services are {{ns1}} ,
{{ns2}} and the {{ranger.plugin.hdfs.service.name}} has value
{{hadoop_service}} then the property-value will be as below:
ranger.tagsync.atlas.hdfs.instance.testcl1.nameservice.ns1.ranger.service=hadoop_service_ns1
ranger.tagsync.atlas.hdfs.instance.testcl1.nameservice.ns2.ranger.service=hadoop_service_ns2
PS : Related NN-Federation UI-wizard changes are already handled in
AMBARI-23424, This issue is created to handle addition of properties via
blueprint.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-23832) Support Atlas HBase hook from Ambari
[ https://issues.apache.org/jira/browse/AMBARI-23832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia resolved AMBARI-23832. - Resolution: Fixed Merged via pull request [1259|https://github.com/apache/ambari/pull/1259] > Support Atlas HBase hook from Ambari > > > Key: AMBARI-23832 > URL: https://issues.apache.org/jira/browse/AMBARI-23832 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Atlas hook for HBase is now available and can be enabled with patch for > ATLAS-1805. This feature needs to be supported from Ambari, similar to > existing hooks for Hive, Storm, Sqoop and Falcon. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23832) Support Atlas HBase hook from Ambari
Vishal Suvagia created AMBARI-23832: --- Summary: Support Atlas HBase hook from Ambari Key: AMBARI-23832 URL: https://issues.apache.org/jira/browse/AMBARI-23832 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.0 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.7.0 Atlas hook for HBase is now available and can be enabled with patch for ATLAS-1805. This feature needs to be supported from Ambari, similar to existing hooks for Hive, Storm, Sqoop and Falcon. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23738) Need to add pre-upgrade check for Atlas service during stack upgrade
[
https://issues.apache.org/jira/browse/AMBARI-23738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-23738:
Description:
While upgrading to stack 3.0, Atlas needs to migrate data from existing version
to upgraded versions. To migrate the data we need to provide
{{atlas.migration.data.filename}} property in the application-properties before
upgrading the stack.
Hence prior to upgrading from existing stack to 3.0 stack we will need to check
if the property {{atlas.migration.data.filename}} exists or not.
Reference ATLAS-2460.
was:
While upgrading to stack 3.0, Atlas needs to migrate data from existing version
to upgraded versions. Hence to migrate the data we need to provide
\{{atlas.migration.data.filename}} property in the application-properties
before upgrading the stack.
Reference [ATLAS-2460|https://issues.apache.org/jira/browse/ATLAS-2460].
> Need to add pre-upgrade check for Atlas service during stack upgrade
>
>
> Key: AMBARI-23738
> URL: https://issues.apache.org/jira/browse/AMBARI-23738
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Major
> Fix For: 2.7.0
>
>
> While upgrading to stack 3.0, Atlas needs to migrate data from existing
> version to upgraded versions. To migrate the data we need to provide
> {{atlas.migration.data.filename}} property in the application-properties
> before upgrading the stack.
> Hence prior to upgrading from existing stack to 3.0 stack we will need to
> check if the property {{atlas.migration.data.filename}} exists or not.
> Reference ATLAS-2460.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23738) Need to add pre-upgrade check for Atlas service during stack upgrade
Vishal Suvagia created AMBARI-23738:
---
Summary: Need to add pre-upgrade check for Atlas service during
stack upgrade
Key: AMBARI-23738
URL: https://issues.apache.org/jira/browse/AMBARI-23738
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Vishal Suvagia
Assignee: Vishal Suvagia
Fix For: 2.7.0
While upgrading to stack 3.0, Atlas needs to migrate data from existing version
to upgraded versions. Hence to migrate the data we need to provide
\{{atlas.migration.data.filename}} property in the application-properties
before upgrading the stack.
Reference [ATLAS-2460|https://issues.apache.org/jira/browse/ATLAS-2460].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-23515) Rearranging configuration file creation for Ranger Plugins.
[ https://issues.apache.org/jira/browse/AMBARI-23515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia resolved AMBARI-23515. - Resolution: Fixed Committed to [trunk|https://github.com/apache/ambari/commit/391de63db4e9e35f857bee77de0a17d4a7c3d898] branch. > Rearranging configuration file creation for Ranger Plugins. > --- > > Key: AMBARI-23515 > URL: https://issues.apache.org/jira/browse/AMBARI-23515 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > When enabling Ranger plug-ins for Storm, Knox and Kafka certain configuration > files are created for the plug-in enabled components, need to re-arrange > logic to create the configuration files to allow better flexibility. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23529) Utility function to get namenode logical hostname and namespace for a given hostname
[ https://issues.apache.org/jira/browse/AMBARI-23529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-23529: Resolution: Fixed Status: Resolved (was: Patch Available) Merged by pull [request-954|https://github.com/apache/ambari/pull/954]. > Utility function to get namenode logical hostname and namespace for a given > hostname > > > Key: AMBARI-23529 > URL: https://issues.apache.org/jira/browse/AMBARI-23529 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-23529.patch > > Time Spent: 1h 40m > Remaining Estimate: 0h > > The goal is to create a utility function to get namenode-logical name and > namespace for a given hostname. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23529) Utility function to get namenode logical hostname and namespace for a given hostname
[ https://issues.apache.org/jira/browse/AMBARI-23529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-23529: Attachment: AMBARI-23529.patch > Utility function to get namenode logical hostname and namespace for a given > hostname > > > Key: AMBARI-23529 > URL: https://issues.apache.org/jira/browse/AMBARI-23529 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-23529.patch > > Time Spent: 10m > Remaining Estimate: 0h > > The goal is to create a utility function to get namenode-logical name and > namespace for a given hostname. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23529) Utility function to get namenode logical hostname and namespace for a given hostname
[ https://issues.apache.org/jira/browse/AMBARI-23529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-23529: Status: Patch Available (was: In Progress) > Utility function to get namenode logical hostname and namespace for a given > hostname > > > Key: AMBARI-23529 > URL: https://issues.apache.org/jira/browse/AMBARI-23529 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-23529.patch > > Time Spent: 10m > Remaining Estimate: 0h > > The goal is to create a utility function to get namenode-logical name and > namespace for a given hostname. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23529) Utility function to get namenode logical hostname and namespace for a given hostname
Vishal Suvagia created AMBARI-23529: --- Summary: Utility function to get namenode logical hostname and namespace for a given hostname Key: AMBARI-23529 URL: https://issues.apache.org/jira/browse/AMBARI-23529 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.0 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.7.0 The goal is to create a utility function to get namenode-logical name and namespace for a given hostname. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23457) Hive-server-interactive service needs to be started after Ranger-Admin.
[
https://issues.apache.org/jira/browse/AMBARI-23457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-23457:
Resolution: Fixed
Status: Resolved (was: Patch Available)
Merged to [trunk|https://github.com/apache/ambari/pull/905] and [branch-2.6
|https://github.com/apache/ambari/pull/906]
> Hive-server-interactive service needs to be started after Ranger-Admin.
> ---
>
> Key: AMBARI-23457
> URL: https://issues.apache.org/jira/browse/AMBARI-23457
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.6.2
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Major
> Labels: pull-request-available
> Fix For: trunk, 2.6.2
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> When {{Hive-Server-Interactive}} is enabled for Hive service and
> {{Ranger-Hive plugin}} is enabled, {{Hive-Server-Interactive}} is started
> before {{Ranger-Admin}} starts. This can cause start of
> Hive-Server-Interactive start with errors. Hence need to start
> {{Hive-Server-Interactive}} after {{Ranger-Admin}} starts.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23515) Rearranging configuration file creation for Ranger Plugins.
Vishal Suvagia created AMBARI-23515: --- Summary: Rearranging configuration file creation for Ranger Plugins. Key: AMBARI-23515 URL: https://issues.apache.org/jira/browse/AMBARI-23515 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.0 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.7.0 When enabling Ranger plug-ins for Storm, Knox and Kafka certain configuration files are created for the plug-in enabled components, need to re-arrange logic to create the configuration files to allow better flexibility. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23457) Hive-server-interactive service needs to be started after Ranger-Admin.
[
https://issues.apache.org/jira/browse/AMBARI-23457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-23457:
Status: Patch Available (was: In Progress)
> Hive-server-interactive service needs to be started after Ranger-Admin.
> ---
>
> Key: AMBARI-23457
> URL: https://issues.apache.org/jira/browse/AMBARI-23457
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.6.2
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Major
> Labels: pull-request-available
> Fix For: trunk, 2.6.2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When {{Hive-Server-Interactive}} is enabled for Hive service and
> {{Ranger-Hive plugin}} is enabled, {{Hive-Server-Interactive}} is started
> before {{Ranger-Admin}} starts. This can cause start of
> Hive-Server-Interactive start with errors. Hence need to start
> {{Hive-Server-Interactive}} after {{Ranger-Admin}} starts.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23457) Hive-server-interactive service needs to be started after Ranger-Admin.
Vishal Suvagia created AMBARI-23457:
---
Summary: Hive-server-interactive service needs to be started after
Ranger-Admin.
Key: AMBARI-23457
URL: https://issues.apache.org/jira/browse/AMBARI-23457
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: trunk, 2.6.2
Reporter: Vishal Suvagia
Assignee: Vishal Suvagia
Fix For: trunk, 2.6.2
When {{Hive-Server-Interactive}} is enabled for Hive service and {{Ranger-Hive
plugin}} is enabled, {{Hive-Server-Interactive}} is started before
{{Ranger-Admin}} starts. This can cause start of Hive-Server-Interactive start
with errors. Hence need to start {{Hive-Server-Interactive}} after
{{Ranger-Admin}} starts.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22635) Ambari should create a dummy core-site.xml for Ranger plugins when namenode is not installed
[ https://issues.apache.org/jira/browse/AMBARI-22635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-22635: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to [trunk|https://github.com/apache/ambari/commit/a3d4c3da56eeec22e864978a7a8be39586948ff5], [trunk-addendum|https://github.com/apache/ambari/commit/f1f730229fe559439189726c0cd40cd58cbf0135] and [branch-2.6|https://github.com/apache/ambari/commit/21fb855c6be7adb473c13cb677474a74da3c5003]. > Ambari should create a dummy core-site.xml for Ranger plugins when namenode > is not installed > > > Key: AMBARI-22635 > URL: https://issues.apache.org/jira/browse/AMBARI-22635 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0, 2.6.1 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: trunk, 2.6.2 > > Attachments: AMBARI-22635-branch-2.6.1.patch, > AMBARI-22635-branch-2.6.2.patch, AMBARI-22635-branch-2.6.patch, > AMBARI-22635-trunk.1-addendum.patch, AMBARI-22635-trunk.1.patch, > AMBARI-22635-trunk.patch > > > For Ranger plugins to work properly in kerberised environments where HDFS is > not installed. We need to create a core-site.xml for Storm and Kafka plugins > so that the plugins can work to fetch latest policies from with kerberised > calls from Ranger. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22635) Ambari should create a dummy core-site.xml for Ranger plugins when namenode is not installed
[ https://issues.apache.org/jira/browse/AMBARI-22635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292073#comment-16292073 ] Vishal Suvagia commented on AMBARI-22635: - [^AMBARI-22635-trunk.1-addendum.patch] pushed to [trunk|https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=f1f730229fe559439189726c0cd40cd58cbf0135] > Ambari should create a dummy core-site.xml for Ranger plugins when namenode > is not installed > > > Key: AMBARI-22635 > URL: https://issues.apache.org/jira/browse/AMBARI-22635 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0, 2.6.1 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: trunk, 2.6.2 > > Attachments: AMBARI-22635-branch-2.6.1.patch, > AMBARI-22635-branch-2.6.2.patch, AMBARI-22635-branch-2.6.patch, > AMBARI-22635-trunk.1-addendum.patch, AMBARI-22635-trunk.1.patch, > AMBARI-22635-trunk.patch > > > For Ranger plugins to work properly in kerberised environments where HDFS is > not installed. We need to create a core-site.xml for Storm and Kafka plugins > so that the plugins can work to fetch latest policies from with kerberised > calls from Ranger. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22635) Ambari should create a dummy core-site.xml for Ranger plugins when namenode is not installed
[ https://issues.apache.org/jira/browse/AMBARI-22635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-22635: Attachment: AMBARI-22635-branch-2.6.2.patch AMBARI-22635-trunk.1-addendum.patch Addendum fix for trunk branch, and updating revised patch for branch-2.6 > Ambari should create a dummy core-site.xml for Ranger plugins when namenode > is not installed > > > Key: AMBARI-22635 > URL: https://issues.apache.org/jira/browse/AMBARI-22635 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0, 2.6.1 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: trunk, 2.6.2 > > Attachments: AMBARI-22635-branch-2.6.1.patch, > AMBARI-22635-branch-2.6.2.patch, AMBARI-22635-branch-2.6.patch, > AMBARI-22635-trunk.1-addendum.patch, AMBARI-22635-trunk.1.patch, > AMBARI-22635-trunk.patch > > > For Ranger plugins to work properly in kerberised environments where HDFS is > not installed. We need to create a core-site.xml for Storm and Kafka plugins > so that the plugins can work to fetch latest policies from with kerberised > calls from Ranger. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22635) Ambari should create a dummy core-site.xml for Ranger plugins when namenode is not installed
[ https://issues.apache.org/jira/browse/AMBARI-22635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-22635: Attachment: AMBARI-22635-branch-2.6.1.patch AMBARI-22635-trunk.1.patch > Ambari should create a dummy core-site.xml for Ranger plugins when namenode > is not installed > > > Key: AMBARI-22635 > URL: https://issues.apache.org/jira/browse/AMBARI-22635 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0, 2.6.1 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: trunk, 2.6.2 > > Attachments: AMBARI-22635-branch-2.6.1.patch, > AMBARI-22635-branch-2.6.patch, AMBARI-22635-trunk.1.patch, > AMBARI-22635-trunk.patch > > > For Ranger plugins to work properly in kerberised environments where HDFS is > not installed. We need to create a core-site.xml for Storm and Kafka plugins > so that the plugins can work to fetch latest policies from with kerberised > calls from Ranger. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22635) Ambari should create a dummy core-site.xml for Ranger plugins when namenode is not installed
[ https://issues.apache.org/jira/browse/AMBARI-22635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-22635: Status: Patch Available (was: In Progress) > Ambari should create a dummy core-site.xml for Ranger plugins when namenode > is not installed > > > Key: AMBARI-22635 > URL: https://issues.apache.org/jira/browse/AMBARI-22635 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0, 2.6.1 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: trunk, 2.6.1 > > Attachments: AMBARI-22635-branch-2.6.patch, AMBARI-22635-trunk.patch > > > For Ranger plugins to work properly in kerberised environments where HDFS is > not installed. We need to create a core-site.xml for Storm and Kafka plugins > so that the plugins can work to fetch latest policies from with kerberised > calls from Ranger. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22635) Ambari should create a dummy core-site.xml for Ranger plugins when namenode is not installed
[ https://issues.apache.org/jira/browse/AMBARI-22635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-22635: Attachment: AMBARI-22635-branch-2.6.patch AMBARI-22635-trunk.patch Attaching patch > Ambari should create a dummy core-site.xml for Ranger plugins when namenode > is not installed > > > Key: AMBARI-22635 > URL: https://issues.apache.org/jira/browse/AMBARI-22635 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0, 2.6.1 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: trunk, 2.6.1 > > Attachments: AMBARI-22635-branch-2.6.patch, AMBARI-22635-trunk.patch > > > For Ranger plugins to work properly in kerberised environments where HDFS is > not installed. We need to create a core-site.xml for Storm and Kafka plugins > so that the plugins can work to fetch latest policies from with kerberised > calls from Ranger. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22635) Ambari should create a dummy core-site.xml for Ranger plugins when namenode is not installed
[ https://issues.apache.org/jira/browse/AMBARI-22635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-22635: Affects Version/s: 2.6.1 2.6.0 Fix Version/s: 2.6.1 trunk Description: For Ranger plugins to work properly in kerberised environments where HDFS is not installed. We need to create a core-site.xml for Storm and Kafka plugins so that the plugins can work to fetch latest policies from with kerberised calls from Ranger. Component/s: ambari-server > Ambari should create a dummy core-site.xml for Ranger plugins when namenode > is not installed > > > Key: AMBARI-22635 > URL: https://issues.apache.org/jira/browse/AMBARI-22635 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0, 2.6.1 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: trunk, 2.6.1 > > > For Ranger plugins to work properly in kerberised environments where HDFS is > not installed. We need to create a core-site.xml for Storm and Kafka plugins > so that the plugins can work to fetch latest policies from with kerberised > calls from Ranger. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22635) Ambari should create a dummy core-site.xml for Ranger plugins when namenode is not installed
Vishal Suvagia created AMBARI-22635: --- Summary: Ambari should create a dummy core-site.xml for Ranger plugins when namenode is not installed Key: AMBARI-22635 URL: https://issues.apache.org/jira/browse/AMBARI-22635 Project: Ambari Issue Type: Bug Reporter: Vishal Suvagia -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-22635) Ambari should create a dummy core-site.xml for Ranger plugins when namenode is not installed
[ https://issues.apache.org/jira/browse/AMBARI-22635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia reassigned AMBARI-22635: --- Assignee: Vishal Suvagia > Ambari should create a dummy core-site.xml for Ranger plugins when namenode > is not installed > > > Key: AMBARI-22635 > URL: https://issues.apache.org/jira/browse/AMBARI-22635 > Project: Ambari > Issue Type: Bug >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22232) Need to add a new property to support proxy users property for Atlas service
[
https://issues.apache.org/jira/browse/AMBARI-22232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-22232:
Status: Patch Available (was: In Progress)
removing unused imports
> Need to add a new property to support proxy users property for Atlas service
>
>
> Key: AMBARI-22232
> URL: https://issues.apache.org/jira/browse/AMBARI-22232
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-22232_Addendum.1.patch,
> AMBARI-22232_Addendum.patch, AMBARI-22232_branch-2.6.1.patch,
> AMBARI-22232_branch-2.6.patch, AMBARI-22232_trunk.1.patch,
> AMBARI-22232_trunk.patch
>
>
> When Atlas is enabled via proxy needs to know the proxy-users to authorize
> them while accessing the Atlas service via proxy support using property
> {{atlas.proxyusers}} with default value knox. Additional details on ATLAS-2166
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22232) Need to add a new property to support proxy users property for Atlas service
[
https://issues.apache.org/jira/browse/AMBARI-22232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-22232:
Attachment: AMBARI-22232_Addendum.1.patch
Attaching patch for removing unused imports.
> Need to add a new property to support proxy users property for Atlas service
>
>
> Key: AMBARI-22232
> URL: https://issues.apache.org/jira/browse/AMBARI-22232
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-22232_Addendum.1.patch,
> AMBARI-22232_Addendum.patch, AMBARI-22232_branch-2.6.1.patch,
> AMBARI-22232_branch-2.6.patch, AMBARI-22232_trunk.1.patch,
> AMBARI-22232_trunk.patch
>
>
> When Atlas is enabled via proxy needs to know the proxy-users to authorize
> them while accessing the Atlas service via proxy support using property
> {{atlas.proxyusers}} with default value knox. Additional details on ATLAS-2166
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Reopened] (AMBARI-22232) Need to add a new property to support proxy users property for Atlas service
[
https://issues.apache.org/jira/browse/AMBARI-22232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia reopened AMBARI-22232:
-
need to remove unused imports.
> Need to add a new property to support proxy users property for Atlas service
>
>
> Key: AMBARI-22232
> URL: https://issues.apache.org/jira/browse/AMBARI-22232
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-22232_Addendum.patch,
> AMBARI-22232_branch-2.6.1.patch, AMBARI-22232_branch-2.6.patch,
> AMBARI-22232_trunk.1.patch, AMBARI-22232_trunk.patch
>
>
> When Atlas is enabled via proxy needs to know the proxy-users to authorize
> them while accessing the Atlas service via proxy support using property
> {{atlas.proxyusers}} with default value knox. Additional details on ATLAS-2166
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22232) Need to add a new property to support proxy users property for Atlas service
[
https://issues.apache.org/jira/browse/AMBARI-22232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-22232:
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed addendum patch to
[trunk|https://github.com/apache/ambari/commit/d4458daa9bf5209eb2f86409185221cdbd749b13]
and
[branch-2.6|https://github.com/apache/ambari/commit/2d1100deda79195c39e4f42f7a9d4504b10c6af5]
> Need to add a new property to support proxy users property for Atlas service
>
>
> Key: AMBARI-22232
> URL: https://issues.apache.org/jira/browse/AMBARI-22232
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-22232_Addendum.patch,
> AMBARI-22232_branch-2.6.1.patch, AMBARI-22232_branch-2.6.patch,
> AMBARI-22232_trunk.1.patch, AMBARI-22232_trunk.patch
>
>
> When Atlas is enabled via proxy needs to know the proxy-users to authorize
> them while accessing the Atlas service via proxy support using property
> {{atlas.proxyusers}} with default value knox. Additional details on ATLAS-2166
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22232) Need to add a new property to support proxy users property for Atlas service
[
https://issues.apache.org/jira/browse/AMBARI-22232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-22232:
Status: Patch Available (was: In Progress)
> Need to add a new property to support proxy users property for Atlas service
>
>
> Key: AMBARI-22232
> URL: https://issues.apache.org/jira/browse/AMBARI-22232
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-22232_Addendum.patch,
> AMBARI-22232_branch-2.6.1.patch, AMBARI-22232_branch-2.6.patch,
> AMBARI-22232_trunk.1.patch, AMBARI-22232_trunk.patch
>
>
> When Atlas is enabled via proxy needs to know the proxy-users to authorize
> them while accessing the Atlas service via proxy support using property
> {{atlas.proxyusers}} with default value knox. Additional details on ATLAS-2166
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22232) Need to add a new property to support proxy users property for Atlas service
[
https://issues.apache.org/jira/browse/AMBARI-22232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-22232:
Attachment: AMBARI-22232_Addendum.patch
Addendum patch for missing apache license in new files
> Need to add a new property to support proxy users property for Atlas service
>
>
> Key: AMBARI-22232
> URL: https://issues.apache.org/jira/browse/AMBARI-22232
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-22232_Addendum.patch,
> AMBARI-22232_branch-2.6.1.patch, AMBARI-22232_branch-2.6.patch,
> AMBARI-22232_trunk.1.patch, AMBARI-22232_trunk.patch
>
>
> When Atlas is enabled via proxy needs to know the proxy-users to authorize
> them while accessing the Atlas service via proxy support using property
> {{atlas.proxyusers}} with default value knox. Additional details on ATLAS-2166
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Reopened] (AMBARI-22232) Need to add a new property to support proxy users property for Atlas service
[
https://issues.apache.org/jira/browse/AMBARI-22232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia reopened AMBARI-22232:
-
Need to add Apache license for new Java classes
> Need to add a new property to support proxy users property for Atlas service
>
>
> Key: AMBARI-22232
> URL: https://issues.apache.org/jira/browse/AMBARI-22232
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-22232_branch-2.6.1.patch,
> AMBARI-22232_branch-2.6.patch, AMBARI-22232_trunk.1.patch,
> AMBARI-22232_trunk.patch
>
>
> When Atlas is enabled via proxy needs to know the proxy-users to authorize
> them while accessing the Atlas service via proxy support using property
> {{atlas.proxyusers}} with default value knox. Additional details on ATLAS-2166
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22232) Need to add a new property to support proxy users property for Atlas service
[
https://issues.apache.org/jira/browse/AMBARI-22232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-22232:
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to
[trunk|https://github.com/apache/ambari/commit/df1081378e51c309589540673e140faaf9329ee4]
and
[branch-2.6|https://github.com/apache/ambari/commit/34dc3094194f78cc3c143390b162d3dc38aa5860]
> Need to add a new property to support proxy users property for Atlas service
>
>
> Key: AMBARI-22232
> URL: https://issues.apache.org/jira/browse/AMBARI-22232
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-22232_branch-2.6.1.patch,
> AMBARI-22232_branch-2.6.patch, AMBARI-22232_trunk.1.patch,
> AMBARI-22232_trunk.patch
>
>
> When Atlas is enabled via proxy needs to know the proxy-users to authorize
> them while accessing the Atlas service via proxy support using property
> {{atlas.proxyusers}} with default value knox. Additional details on ATLAS-2166
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22232) Need to add a new property to support proxy users property for Atlas service
[
https://issues.apache.org/jira/browse/AMBARI-22232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-22232:
Attachment: AMBARI-22232_branch-2.6.1.patch
AMBARI-22232_trunk.1.patch
> Need to add a new property to support proxy users property for Atlas service
>
>
> Key: AMBARI-22232
> URL: https://issues.apache.org/jira/browse/AMBARI-22232
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-22232_branch-2.6.1.patch,
> AMBARI-22232_branch-2.6.patch, AMBARI-22232_trunk.1.patch,
> AMBARI-22232_trunk.patch
>
>
> When Atlas is enabled via proxy needs to know the proxy-users to authorize
> them while accessing the Atlas service via proxy support using property
> {{atlas.proxyusers}} with default value knox. Additional details on ATLAS-2166
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22232) Need to add a new property to support proxy users property for Atlas service
[
https://issues.apache.org/jira/browse/AMBARI-22232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-22232:
Attachment: AMBARI-22232_branch-2.6.patch
AMBARI-22232_trunk.patch
Revised original patch
> Need to add a new property to support proxy users property for Atlas service
>
>
> Key: AMBARI-22232
> URL: https://issues.apache.org/jira/browse/AMBARI-22232
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-22232_branch-2.6.patch, AMBARI-22232_trunk.patch
>
>
> When Atlas is enabled via proxy needs to know the proxy-users to authorize
> them while accessing the Atlas service via proxy support using property
> {{atlas.proxyusers}} with default value knox. Additional details on ATLAS-2166
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22232) Need to add a new property to support proxy users property for Atlas service
[
https://issues.apache.org/jira/browse/AMBARI-22232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-22232:
Attachment: (was: AMBARI-22232_trunk.patch)
> Need to add a new property to support proxy users property for Atlas service
>
>
> Key: AMBARI-22232
> URL: https://issues.apache.org/jira/browse/AMBARI-22232
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Blocker
> Fix For: 2.6.0
>
>
> When Atlas is enabled via proxy needs to know the proxy-users to authorize
> them while accessing the Atlas service via proxy support using property
> {{atlas.proxyusers}} with default value knox. Additional details on ATLAS-2166
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22232) Need to add a new property to support proxy users property for Atlas service
[
https://issues.apache.org/jira/browse/AMBARI-22232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-22232:
Attachment: (was: AMBARI-22232_branch-2.6.patch)
> Need to add a new property to support proxy users property for Atlas service
>
>
> Key: AMBARI-22232
> URL: https://issues.apache.org/jira/browse/AMBARI-22232
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Blocker
> Fix For: 2.6.0
>
>
> When Atlas is enabled via proxy needs to know the proxy-users to authorize
> them while accessing the Atlas service via proxy support using property
> {{atlas.proxyusers}} with default value knox. Additional details on ATLAS-2166
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22232) Need to add a new property to support proxy users property for Atlas service
[
https://issues.apache.org/jira/browse/AMBARI-22232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-22232:
Attachment: AMBARI-22232_branch-2.6.patch
AMBARI-22232_trunk.patch
Attaching patch fot trnk and branch-2.6
> Need to add a new property to support proxy users property for Atlas service
>
>
> Key: AMBARI-22232
> URL: https://issues.apache.org/jira/browse/AMBARI-22232
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-22232_branch-2.6.patch, AMBARI-22232_trunk.patch
>
>
> When Atlas is enabled via proxy needs to know the proxy-users to authorize
> them while accessing the Atlas service via proxy support using property
> {{atlas.proxyusers}} with default value knox. Additional details on ATLAS-2166
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22232) Need to add a new property to support proxy users property for Atlas service
[
https://issues.apache.org/jira/browse/AMBARI-22232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-22232:
Status: Patch Available (was: In Progress)
> Need to add a new property to support proxy users property for Atlas service
>
>
> Key: AMBARI-22232
> URL: https://issues.apache.org/jira/browse/AMBARI-22232
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-22232_branch-2.6.patch, AMBARI-22232_trunk.patch
>
>
> When Atlas is enabled via proxy needs to know the proxy-users to authorize
> them while accessing the Atlas service via proxy support using property
> {{atlas.proxyusers}} with default value knox. Additional details on ATLAS-2166
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (AMBARI-22232) Need to add a new property to support proxy users property for Atlas service
[
https://issues.apache.org/jira/browse/AMBARI-22232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204077#comment-16204077
]
Vishal Suvagia edited comment on AMBARI-22232 at 10/13/17 7:44 PM:
---
Attaching patch for trunk and branch-2.6
was (Author: vishalsuvagia):
Attaching patch fot trnk and branch-2.6
> Need to add a new property to support proxy users property for Atlas service
>
>
> Key: AMBARI-22232
> URL: https://issues.apache.org/jira/browse/AMBARI-22232
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-22232_branch-2.6.patch, AMBARI-22232_trunk.patch
>
>
> When Atlas is enabled via proxy needs to know the proxy-users to authorize
> them while accessing the Atlas service via proxy support using property
> {{atlas.proxyusers}} with default value knox. Additional details on ATLAS-2166
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22232) Need to add a new property to support proxy users property for Atlas service
Vishal Suvagia created AMBARI-22232:
---
Summary: Need to add a new property to support proxy users
property for Atlas service
Key: AMBARI-22232
URL: https://issues.apache.org/jira/browse/AMBARI-22232
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.6.0
Reporter: Vishal Suvagia
Assignee: Vishal Suvagia
Priority: Blocker
Fix For: 2.6.0
When Atlas is enabled via proxy needs to know the proxy-users to authorize them
while accessing the Atlas service via proxy support using property
{{atlas.proxyusers}} with default value knox. Additional details on ATLAS-2166
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21925) Facilitate a parameter to provide HBase conf directory for atlas-env configurations.
[
https://issues.apache.org/jira/browse/AMBARI-21925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-21925:
Resolution: Fixed
Status: Resolved (was: Patch Available)
committed to
[trunk|https://github.com/apache/ambari/commit/1f321e35693a1c8fe2c6c5a4ac3e1f454bf847e1]
and [branch-2.6|
https://github.com/apache/ambari/commit/9a11f0512d3a97fe667e5683b5a55b9193a60abe]
> Facilitate a parameter to provide HBase conf directory for atlas-env
> configurations.
>
>
> Key: AMBARI-21925
> URL: https://issues.apache.org/jira/browse/AMBARI-21925
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.6.0
>
> Attachments: AMBARI-21925-branch-2.6.patch, AMBARI-21925-trunk.patch
>
>
> Current configuration for Atlas atlas-env contains {{hbase_conf_dir}} which
> is set in environment as {{export HBASE_CONF_DIR=hbase_conf_dir}}
> However, hbase_conf_dir is currently not exposed in ambari and hence its not
> possible to set just {{hbase_conf_dir}} instead through blueprints we need to
> pass full atlas-env.sh content.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21925) Facilitate a parameter to provide HBase conf directory for atlas-env configurations.
[
https://issues.apache.org/jira/browse/AMBARI-21925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171207#comment-16171207
]
Vishal Suvagia commented on AMBARI-21925:
-
committed to
[trunk|https://github.com/apache/ambari/commit/1f321e35693a1c8fe2c6c5a4ac3e1f454bf847e1]
and [branch-2.6|
https://github.com/apache/ambari/commit/9a11f0512d3a97fe667e5683b5a55b9193a60abe]
> Facilitate a parameter to provide HBase conf directory for atlas-env
> configurations.
>
>
> Key: AMBARI-21925
> URL: https://issues.apache.org/jira/browse/AMBARI-21925
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.6.0
>
> Attachments: AMBARI-21925-branch-2.6.patch, AMBARI-21925-trunk.patch
>
>
> Current configuration for Atlas atlas-env contains {{hbase_conf_dir}} which
> is set in environment as {{export HBASE_CONF_DIR=hbase_conf_dir}}
> However, hbase_conf_dir is currently not exposed in ambari and hence its not
> possible to set just {{hbase_conf_dir}} instead through blueprints we need to
> pass full atlas-env.sh content.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21925) Facilitate a parameter to provide HBase conf directory for atlas-env configurations.
[
https://issues.apache.org/jira/browse/AMBARI-21925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-21925:
Attachment: AMBARI-21925-branch-2.6.patch
AMBARI-21925-trunk.patch
> Facilitate a parameter to provide HBase conf directory for atlas-env
> configurations.
>
>
> Key: AMBARI-21925
> URL: https://issues.apache.org/jira/browse/AMBARI-21925
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.6.0
>
> Attachments: AMBARI-21925-branch-2.6.patch, AMBARI-21925-trunk.patch
>
>
> Current configuration for Atlas atlas-env contains {{hbase_conf_dir}} which
> is set in environment as {{export HBASE_CONF_DIR=hbase_conf_dir}}
> However, hbase_conf_dir is currently not exposed in ambari and hence its not
> possible to set just {{hbase_conf_dir}} instead through blueprints we need to
> pass full atlas-env.sh content.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21925) Facilitate a parameter to provide HBase conf directory for atlas-env configurations.
[
https://issues.apache.org/jira/browse/AMBARI-21925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-21925:
Status: Patch Available (was: In Progress)
> Facilitate a parameter to provide HBase conf directory for atlas-env
> configurations.
>
>
> Key: AMBARI-21925
> URL: https://issues.apache.org/jira/browse/AMBARI-21925
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.6.0
>
> Attachments: AMBARI-21925-branch-2.6.patch, AMBARI-21925-trunk.patch
>
>
> Current configuration for Atlas atlas-env contains {{hbase_conf_dir}} which
> is set in environment as {{export HBASE_CONF_DIR=hbase_conf_dir}}
> However, hbase_conf_dir is currently not exposed in ambari and hence its not
> possible to set just {{hbase_conf_dir}} instead through blueprints we need to
> pass full atlas-env.sh content.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21925) Facilitate a parameter to provide HBase conf directory for atlas-env configurations.
Vishal Suvagia created AMBARI-21925:
---
Summary: Facilitate a parameter to provide HBase conf directory
for atlas-env configurations.
Key: AMBARI-21925
URL: https://issues.apache.org/jira/browse/AMBARI-21925
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.6.0
Reporter: Vishal Suvagia
Assignee: Vishal Suvagia
Fix For: 2.6.0
Current configuration for Atlas atlas-env contains {{hbase_conf_dir}} which is
set in environment as {{export HBASE_CONF_DIR=hbase_conf_dir}}
However, hbase_conf_dir is currently not exposed in ambari and hence its not
possible to set just {{hbase_conf_dir}} instead through blueprints we need to
pass full atlas-env.sh content.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21649) Update Atlas log4j to reflect latest configurations
[ https://issues.apache.org/jira/browse/AMBARI-21649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-21649: Resolution: Fixed Status: Resolved (was: Patch Available) committed to [trunk|https://github.com/apache/ambari/commit/faf5d90799deee6509b1398f762616219e241f68] and [branch-2.6|https://github.com/apache/ambari/commit/6ddd4ac76f426e31386822b37b20ec3fa7b133e5] > Update Atlas log4j to reflect latest configurations > --- > > Key: AMBARI-21649 > URL: https://issues.apache.org/jira/browse/AMBARI-21649 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.3 > > Attachments: AMBARI-21649-branch-2.6.patch, > AMBARI-21649-trunk.1.patch, AMBARI-21649-trunk.patch > > > Need to update Atlas log4j configurations to reflect latest configurations as > per update in ATLAS-1996 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21649) Update Atlas log4j to reflect latest configurations
[ https://issues.apache.org/jira/browse/AMBARI-21649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-21649: Attachment: AMBARI-21649-trunk.1.patch Adding atlas-log4j changes. > Update Atlas log4j to reflect latest configurations > --- > > Key: AMBARI-21649 > URL: https://issues.apache.org/jira/browse/AMBARI-21649 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.3 > > Attachments: AMBARI-21649-branch-2.6.patch, > AMBARI-21649-trunk.1.patch, AMBARI-21649-trunk.patch > > > Need to update Atlas log4j configurations to reflect latest configurations as > per update in ATLAS-1996 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21649) Update Atlas log4j to reflect latest configurations
[ https://issues.apache.org/jira/browse/AMBARI-21649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-21649: Status: Patch Available (was: In Progress) > Update Atlas log4j to reflect latest configurations > --- > > Key: AMBARI-21649 > URL: https://issues.apache.org/jira/browse/AMBARI-21649 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.3 > > Attachments: AMBARI-21649-branch-2.6.patch, AMBARI-21649-trunk.patch > > > Need to update Atlas log4j configurations to reflect latest configurations as > per update in ATLAS-1996 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
