- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
How to add properties using rest api that are not seen in the full get request
- Labels:
-
Apache HBase
-
Apache Oozie
-
Cloudera Manager
Created on ‎10-25-2016 02:36 PM - edited ‎09-16-2022 03:45 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
How to I add a value the following properties using the Cloudera Manager rest api. I can see these values in the respective service configuration in the UI, but when I do a rest call using
curl -X GET -u "admin:admin" -i http://<server>:7180/api/v13/clusters/Cluster1/services/<servicename>/config?view=full
// used "oozie" or "hbase" as servicenames.
I see all other properties, but not these particular settings:
Hbase service:
1. HBase Client Advanced Configuration Snippet (Safety Valve) for hbase-site.xml
2. RegionServer Logging Advanced Configuration Snippet (Safety Valve)
3. HBase Client Environment Advanced Configuration Snippet (Safety Valve) for hbase-env.sh
Oozie Service:
1. Oozie Server Advanced Configuration Snippet (Safety Valve) for oozie-site.xml
Created ‎10-25-2016 06:43 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You'll need to POST to the relevant name/values in the roleConfigGroup [0] endpoint.
Modify the configuration in the CM UI and then check the changes in that you've made by doing [1]. Then you should be able to use it in your curl -X POST [...]
[1] curl -X GET http://<server>:7180/api/v13/clusters/Cluster1/services/<servicename>/<servicename>/roleConfigGroups
Created ‎10-25-2016 06:43 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You'll need to POST to the relevant name/values in the roleConfigGroup [0] endpoint.
Modify the configuration in the CM UI and then check the changes in that you've made by doing [1]. Then you should be able to use it in your curl -X POST [...]
[1] curl -X GET http://<server>:7180/api/v13/clusters/Cluster1/services/<servicename>/<servicename>/roleConfigGroups
Created ‎10-28-2016 02:23 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Minor correction POST meant to be PUT but I trust you've figured this out.
Created ‎10-28-2016 02:49 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
