[jira] [Created] (AMBARI-19078) Atlas service check reports faise positive
Ayub Khan created AMBARI-19078:
--
Summary: Atlas service check reports faise positive
Key: AMBARI-19078
URL: https://issues.apache.org/jira/browse/AMBARI-19078
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.0
Reporter: Ayub Khan
Atlas service check is successful even if the service does not return 200 ok.
{noformat}
2016-12-05 07:24:23,768 - Stack Feature Version Info: stack_version=2.5,
version=None, current_cluster_version=2.5.3.0-35 -> 2.5
2016-12-05 07:24:23,777 - Using hadoop conf dir:
/usr/hdp/current/hadoop-client/conf
2016-12-05 07:24:23,795 - Execute['/usr/bin/kinit -kt
/etc/security/keytabs/smokeuser.headless.keytab ambari-qa-...@example.com']
{'user': 'ambari-qa'}
2016-12-05 07:24:23,899 - Execute['curl --negotiate -u : -b ~/cookiejar.txt -c
~/cookiejar.txt -s -o /dev/null -w "%{http_code}"
https://ctr-e61-1479789298070-4849-01-03.hwx.site:21443/'] {'tries': 5,
'user': 'ambari-qa', 'try_sleep': 10}
2016-12-05 07:24:24,162 - Retrying after 10 seconds. Reason: Execution of 'curl
--negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null -w
"%{http_code}" https://ctr-e61-1479789298070-4849-01-03.hwx.site:21443/'
returned 60. 000
2016-12-05 07:24:34,451 - Retrying after 10 seconds. Reason: Execution of 'curl
--negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null -w
"%{http_code}" https://ctr-e61-1479789298070-4849-01-03.hwx.site:21443/'
returned 60. 000
2016-12-05 07:24:44,714 - Retrying after 10 seconds. Reason: Execution of 'curl
--negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null -w
"%{http_code}" https://ctr-e61-1479789298070-4849-01-03.hwx.site:21443/'
returned 60. 000
2016-12-05 07:24:55,031 - Retrying after 10 seconds. Reason: Execution of 'curl
--negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null -w
"%{http_code}" https://ctr-e61-1479789298070-4849-01-03.hwx.site:21443/'
returned 60. 000
Command completed successfully!
{noformat}
And ideally this should check for this API "/api/atlas/admin/status" and return
true if the http response code is 200 OK.
CC; [~mneethiraj] [~skoneru]
{noformat}
[root@ctr-e61-1479789298070-4849-01-03 scripts]# rpm -qa | grep
ambari-server
ambari-server-2.4.2.0-136.x86_64
[root@ctr-e61-1479789298070-4849-01-03 scripts]# rpm -qa | grep atlas
atlas-metadata_2_5_3_0_35-0.7.0.2.5.3.0-35.el6.noarch
ranger_2_5_3_0_35-atlas-plugin-0.6.0.2.5.3.0-35.el6.x86_64
atlas-metadata_2_5_3_0_35-hive-plugin-0.7.0.2.5.3.0-35.el6.noarch
atlas-3.10.1-10.el7.x86_64
[root@ctr-e61-1479789298070-4849-01-03 scripts]#
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19036) Add default roles to auto created views
[ https://issues.apache.org/jira/browse/AMBARI-19036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Rajeev updated AMBARI-19036: --- Attachment: AMBARI-19036.trunk.2.patch > Add default roles to auto created views > --- > > Key: AMBARI-19036 > URL: https://issues.apache.org/jira/browse/AMBARI-19036 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Ashwin Rajeev >Assignee: Ashwin Rajeev > Fix For: 2.5.0 > > Attachments: AMBARI-19036.trunk.2.patch, AMBARI-19036.trunk.patch > > Original Estimate: 1h > Remaining Estimate: 1h > > Add the following roles to auto instances > ||View||Role|| > |Pig|CLUSTER.USER| > |Hive|CLUSTER.USER| > |Tez|CLUSTER.USER| > |File browser|CLUSTER.USER| > |Zepplin|CLUSTER.USER| > |Capacity Scheduler|CLUSTER.ADMINISTRATOR| -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19024) Handle Ambari upgrade changes to set hook flag if Atlas is available in cluster
[ https://issues.apache.org/jira/browse/AMBARI-19024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-19024: - Resolution: Fixed Status: Resolved (was: Patch Available) Fix committed to apache trunk: https://github.com/apache/ambari/commit/8ad494e97302d5da69224c7ce9e493d5f20797c1 branch-2.5: https://github.com/apache/ambari/commit/d2d7b07744855de692c231ca6b0b7f1fdd25d00c > Handle Ambari upgrade changes to set hook flag if Atlas is available in > cluster > --- > > Key: AMBARI-19024 > URL: https://issues.apache.org/jira/browse/AMBARI-19024 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: 3.0.0, 2.5.0 > > > As a part of changes done in AMBARI-19007, need to handle Ambari upgrade > scenario which will update the hook flag if ATLAS and hook supported services > are present in existing cluster. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19076) Broken links in ambari-server/docs/api/v1/schemas.md
[
https://issues.apache.org/jira/browse/AMBARI-19076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15721329#comment-15721329
]
Hadoop QA commented on AMBARI-19076:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12841668/AMBARI-19076.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation patch that doesn't require tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9517//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9517//console
This message is automatically generated.
> Broken links in ambari-server/docs/api/v1/schemas.md
>
>
> Key: AMBARI-19076
> URL: https://issues.apache.org/jira/browse/AMBARI-19076
> Project: Ambari
> Issue Type: Documentation
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Trivial
> Fix For: trunk
>
> Attachments: AMBARI-19076.patch
>
>
> This is very trivial thing. When I see API document on
> https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md,
> I can't jump to {code} [POST/PUT/DELETE resource] {code} by clicking the
> link.
> We can jump to there by using
> https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md#postputdelete-resource.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19007) Atlas to support configuration of hooks from separate cluster
[ https://issues.apache.org/jira/browse/AMBARI-19007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15721287#comment-15721287 ] Hudson commented on AMBARI-19007: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #452 (See [https://builds.apache.org/job/Ambari-branch-2.5/452/]) AMBARI-19007 Atlas to support configuration of hooks from separate (mugdha: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d2d7b07744855de692c231ca6b0b7f1fdd25d00c]) * (edit) ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py * (edit) ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/configuration/sqoop-env.xml * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/configuration/hive-env.xml * (edit) ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/package/scripts/params_linux.py * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java * (edit) ambari-common/src/main/python/resource_management/libraries/functions/setup_atlas_hook.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/services/HIVE/configuration/hive-site.xml * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py * (edit) ambari-server/src/main/resources/common-services/STORM/0.9.1/package/scripts/storm.py * (edit) ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/package/scripts/params_linux.py * (edit) ambari-server/src/main/resources/common-services/STORM/0.10.0/configuration/storm-env.xml * (edit) ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/package/scripts/sqoop.py * (edit) ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/package/scripts/falcon.py * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/services/stack_advisor.py * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hcat.py * (edit) ambari-server/src/main/resources/common-services/STORM/0.9.1/package/scripts/params_linux.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/services/STORM/configuration/storm-site.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/webhcat.py * (edit) ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/configuration/falcon-env.xml * (edit) ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/configuration/sqoop-site.xml > Atlas to support configuration of hooks from separate cluster > - > > Key: AMBARI-19007 > URL: https://issues.apache.org/jira/browse/AMBARI-19007 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Blocker > Fix For: 3.0.0, 2.5.0 > > Attachments: AMBARI-19007-rebase.02.patch, > AMBARI-19007-trunk.01.patch, AMBARI-19007-trunk.02.patch, > AMBARI-19007-trunk.patch, AMBARI-19007.01.patch, AMBARI-19007.02.patch, > AMBARI-19007.patch > > > *Need support in ambari to allow atlas to communicate with hooks installed on > separate clusters* > # Ambari Stack definition changes (for all four hooks being installed on > Separate Cluster) - this information will be stored in blueprints. > # Need to be able to sync with Atlas to leverage tag based security via > tagsync service > # Ambari driven configuration and addition of flags to support the feature. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19007) Atlas to support configuration of hooks from separate cluster
[ https://issues.apache.org/jira/browse/AMBARI-19007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15721284#comment-15721284 ] Hudson commented on AMBARI-19007: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6153 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6153/]) AMBARI-19007 Atlas to support configuration of hooks from separate (mugdha: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8ad494e97302d5da69224c7ce9e493d5f20797c1]) * (edit) ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/package/scripts/falcon.py * (edit) ambari-server/src/main/resources/common-services/STORM/0.9.1/package/scripts/params_linux.py * (edit) ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/package/scripts/sqoop.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/services/STORM/configuration/storm-site.xml * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java * (edit) ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/configuration/falcon-env.xml * (edit) ambari-common/src/main/python/resource_management/libraries/functions/setup_atlas_hook.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py * (edit) ambari-server/src/main/resources/common-services/STORM/0.10.0/configuration/storm-env.xml * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py * (edit) ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py * (edit) ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/configuration/sqoop-env.xml * (edit) ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/package/scripts/params_linux.py * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hcat.py * (edit) ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/configuration/sqoop-site.xml * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/configuration/hive-env.xml * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/services/stack_advisor.py * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/webhcat.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/services/HIVE/configuration/hive-site.xml * (edit) ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/package/scripts/params_linux.py * (edit) ambari-server/src/main/resources/common-services/STORM/0.9.1/package/scripts/storm.py > Atlas to support configuration of hooks from separate cluster > - > > Key: AMBARI-19007 > URL: https://issues.apache.org/jira/browse/AMBARI-19007 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Blocker > Fix For: 3.0.0, 2.5.0 > > Attachments: AMBARI-19007-rebase.02.patch, > AMBARI-19007-trunk.01.patch, AMBARI-19007-trunk.02.patch, > AMBARI-19007-trunk.patch, AMBARI-19007.01.patch, AMBARI-19007.02.patch, > AMBARI-19007.patch > > > *Need support in ambari to allow atlas to communicate with hooks installed on > separate clusters* > # Ambari Stack definition changes (for all four hooks being installed on > Separate Cluster) - this information will be stored in blueprints. > # Need to be able to sync with Atlas to leverage tag based security via > tagsync service > # Ambari driven configuration and addition of flags to support the feature. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19007) Atlas to support configuration of hooks from separate cluster
[ https://issues.apache.org/jira/browse/AMBARI-19007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-19007: - Resolution: Fixed Status: Resolved (was: Patch Available) > Atlas to support configuration of hooks from separate cluster > - > > Key: AMBARI-19007 > URL: https://issues.apache.org/jira/browse/AMBARI-19007 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Blocker > Fix For: 3.0.0, 2.5.0 > > Attachments: AMBARI-19007-rebase.02.patch, > AMBARI-19007-trunk.01.patch, AMBARI-19007-trunk.02.patch, > AMBARI-19007-trunk.patch, AMBARI-19007.01.patch, AMBARI-19007.02.patch, > AMBARI-19007.patch > > > *Need support in ambari to allow atlas to communicate with hooks installed on > separate clusters* > # Ambari Stack definition changes (for all four hooks being installed on > Separate Cluster) - this information will be stored in blueprints. > # Need to be able to sync with Atlas to leverage tag based security via > tagsync service > # Ambari driven configuration and addition of flags to support the feature. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19007) Atlas to support configuration of hooks from separate cluster
[ https://issues.apache.org/jira/browse/AMBARI-19007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15721223#comment-15721223 ] Mugdha Varadkar commented on AMBARI-19007: -- committed to trunk: https://github.com/apache/ambari/commit/8ad494e97302d5da69224c7ce9e493d5f20797c1 branch-2.5: https://github.com/apache/ambari/commit/d2d7b07744855de692c231ca6b0b7f1fdd25d00c > Atlas to support configuration of hooks from separate cluster > - > > Key: AMBARI-19007 > URL: https://issues.apache.org/jira/browse/AMBARI-19007 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Blocker > Fix For: 3.0.0, 2.5.0 > > Attachments: AMBARI-19007-rebase.02.patch, > AMBARI-19007-trunk.01.patch, AMBARI-19007-trunk.02.patch, > AMBARI-19007-trunk.patch, AMBARI-19007.01.patch, AMBARI-19007.02.patch, > AMBARI-19007.patch > > > *Need support in ambari to allow atlas to communicate with hooks installed on > separate clusters* > # Ambari Stack definition changes (for all four hooks being installed on > Separate Cluster) - this information will be stored in blueprints. > # Need to be able to sync with Atlas to leverage tag based security via > tagsync service > # Ambari driven configuration and addition of flags to support the feature. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19007) Atlas to support configuration of hooks from separate cluster
[ https://issues.apache.org/jira/browse/AMBARI-19007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-19007: - Attachment: AMBARI-19007-rebase.02.patch > Atlas to support configuration of hooks from separate cluster > - > > Key: AMBARI-19007 > URL: https://issues.apache.org/jira/browse/AMBARI-19007 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Blocker > Fix For: 3.0.0, 2.5.0 > > Attachments: AMBARI-19007-rebase.02.patch, > AMBARI-19007-trunk.01.patch, AMBARI-19007-trunk.02.patch, > AMBARI-19007-trunk.patch, AMBARI-19007.01.patch, AMBARI-19007.02.patch, > AMBARI-19007.patch > > > *Need support in ambari to allow atlas to communicate with hooks installed on > separate clusters* > # Ambari Stack definition changes (for all four hooks being installed on > Separate Cluster) - this information will be stored in blueprints. > # Need to be able to sync with Atlas to leverage tag based security via > tagsync service > # Ambari driven configuration and addition of flags to support the feature. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17346) Dependent components should be shutdown before stopping hdfs
[ https://issues.apache.org/jira/browse/AMBARI-17346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-17346: Description: Sometimes admin shuts down hdfs first, then hbase. By the time hbase is shutdown, no data can be persisted (including metadata). This results in large number of inconsistencies when hbase cluster is brought back up. Before hdfs is shutdown, the components dependent on hdfs should be shutdown first. was: Sometimes admin shuts down hdfs first, then hbase. By the time hbase is shutdown, no data can be persisted (including metadata). This results in large number of inconsistencies when hbase cluster is brought back up. Before hdfs is shutdown, the components dependent on hdfs should be shutdown first. > Dependent components should be shutdown before stopping hdfs > > > Key: AMBARI-17346 > URL: https://issues.apache.org/jira/browse/AMBARI-17346 > Project: Ambari > Issue Type: Bug >Reporter: Ted Yu > > Sometimes admin shuts down hdfs first, then hbase. > By the time hbase is shutdown, no data can be persisted (including metadata). > This results in large number of inconsistencies when hbase cluster is brought > back up. > Before hdfs is shutdown, the components dependent on hdfs should be shutdown > first. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19077) Ambari-server: Gather dependent configuration types and password properties for a service component
Nahappan Somasundaram created AMBARI-19077: -- Summary: Ambari-server: Gather dependent configuration types and password properties for a service component Key: AMBARI-19077 URL: https://issues.apache.org/jira/browse/AMBARI-19077 Project: Ambari Issue Type: Task Components: ambari-agent, ambari-server Affects Versions: 2.5.0 Reporter: Nahappan Somasundaram Assignee: Nahappan Somasundaram Fix For: 2.5.0 In the command JSON, we need the list of configurations and the corresponding password properties on which a service component is dependent upon. This will help ambari agent create the JCEKS provider files for just those affected configuration types instead of for all configuration types that contain password properties. We also need to provide the password properties and the properties that use it. This will ensure that we are able to correctly map the value provided by the user property to the value provided by the password property. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19076) Broken links in ambari-server/docs/api/v1/schemas.md
[
https://issues.apache.org/jira/browse/AMBARI-19076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15720621#comment-15720621
]
Doroszlai, Attila commented on AMBARI-19076:
+1 for the patch
> Broken links in ambari-server/docs/api/v1/schemas.md
>
>
> Key: AMBARI-19076
> URL: https://issues.apache.org/jira/browse/AMBARI-19076
> Project: Ambari
> Issue Type: Documentation
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Trivial
> Fix For: trunk
>
> Attachments: AMBARI-19076.patch
>
>
> This is very trivial thing. When I see API document on
> https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md,
> I can't jump to {code} [POST/PUT/DELETE resource] {code} by clicking the
> link.
> We can jump to there by using
> https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md#postputdelete-resource.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19076) Broken links in ambari-server/docs/api/v1/schemas.md
[
https://issues.apache.org/jira/browse/AMBARI-19076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-19076:
-
Status: Patch Available (was: Open)
> Broken links in ambari-server/docs/api/v1/schemas.md
>
>
> Key: AMBARI-19076
> URL: https://issues.apache.org/jira/browse/AMBARI-19076
> Project: Ambari
> Issue Type: Documentation
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Trivial
> Fix For: trunk
>
> Attachments: AMBARI-19076.patch
>
>
> This is very trivial thing. When I see API document on
> https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md,
> I can't jump to {code} [POST/PUT/DELETE resource] {code} by clicking the
> link.
> We can jump to there by using
> https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md#postputdelete-resource.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19076) Broken links in ambari-server/docs/api/v1/schemas.md
[
https://issues.apache.org/jira/browse/AMBARI-19076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-19076:
-
Attachment: AMBARI-19076.patch
> Broken links in ambari-server/docs/api/v1/schemas.md
>
>
> Key: AMBARI-19076
> URL: https://issues.apache.org/jira/browse/AMBARI-19076
> Project: Ambari
> Issue Type: Documentation
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Trivial
> Fix For: trunk
>
> Attachments: AMBARI-19076.patch
>
>
> This is very trivial thing. When I see API document on
> https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md,
> I can't jump to {code} [POST/PUT/DELETE resource] {code} by clicking the
> link.
> We can jump to there by using
> https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md#postputdelete-resource.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19076) Broken links in ambari-server/docs/api/v1/schemas.md
[
https://issues.apache.org/jira/browse/AMBARI-19076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-19076:
-
Description:
This is very trivial thing. When I see API document on
https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md,
I can't jump to {code} [POST/PUT/DELETE resource] {code} by clicking the link.
We can jump to there by using
https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md#postputdelete-resource.
was:This is very trivial thing. When I see API document on
https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md,
I can't jump to {code} [POST/PUT/DELETE resource] {code} by clicking the link.
> Broken links in ambari-server/docs/api/v1/schemas.md
>
>
> Key: AMBARI-19076
> URL: https://issues.apache.org/jira/browse/AMBARI-19076
> Project: Ambari
> Issue Type: Documentation
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Trivial
> Fix For: trunk
>
>
> This is very trivial thing. When I see API document on
> https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md,
> I can't jump to {code} [POST/PUT/DELETE resource] {code} by clicking the
> link.
> We can jump to there by using
> https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md#postputdelete-resource.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19076) Broken links in ambari-server/docs/api/v1/schemas.md
[
https://issues.apache.org/jira/browse/AMBARI-19076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-19076:
-
Description: This is very trivial thing. When I see API document on
https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md,
I can't jump to {code} [POST/PUT/DELETE resource] {code} by clicking the link.
(was: This is very trivial thing. When I see API document on
[github](https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md),
I can't jump to {{{POST/PUT/DELETE resource]}}} by clicking the link.)
> Broken links in ambari-server/docs/api/v1/schemas.md
>
>
> Key: AMBARI-19076
> URL: https://issues.apache.org/jira/browse/AMBARI-19076
> Project: Ambari
> Issue Type: Documentation
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Trivial
> Fix For: trunk
>
>
> This is very trivial thing. When I see API document on
> https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md,
> I can't jump to {code} [POST/PUT/DELETE resource] {code} by clicking the
> link.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19076) Broken links in ambari-server/docs/api/v1/schemas.md
Masahiro Tanaka created AMBARI-19076:
Summary: Broken links in ambari-server/docs/api/v1/schemas.md
Key: AMBARI-19076
URL: https://issues.apache.org/jira/browse/AMBARI-19076
Project: Ambari
Issue Type: Documentation
Affects Versions: trunk
Reporter: Masahiro Tanaka
Assignee: Masahiro Tanaka
Priority: Trivial
Fix For: trunk
This is very trivial thing. When I see API document on
[github](https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md),
I can't jump to {{{POST/PUT/DELETE resource]}}} by clicking the link.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
