question 'Role type configuration is supported only up to API v2' in CM API V32 in Support Questions

'Role type configuration is supported only up to API v2' in CM API V32

SandeepSingh — Wed, 04 Sep 2019 15:54:51 GMT

Hi All,

I've been using CM API V32 to update various service configuration and I noticed it works as long as we set service level attributes. However, while trying to update attributes at roleType level, the API responds with error code 400, stating "'Role type configuration is supported only up to API v2' in CM API V32.

Interestingly, the model schema provided by Cloudera recommends using the same attribute for the service config update.

I am using PUT `/clusters/{clusterName}/services/{serviceName}/config` API.

Anyone else facing a similar issue or knows how to deal with this issue?

Thanks.

Re: 'Role type configuration is supported only up to API v2' in CM API V32

lwang — Wed, 04 Sep 2019 21:43:04 GMT

Hi @SandeepSingh ,

Please use role config groups instead of role types. You can see relevant methods in ApiService to get and create groups. You may want to read this thread which people experienced the similar error message.

https://grokbase.com/t/cloudera/scm-users/1373r4h204/cm-api-create-cluster-error

Thanks and hope this helps,

Re: 'Role type configuration is supported only up to API v2' in CM API V32

SandeepSingh — Thu, 12 Sep 2019 08:45:05 GMT

Hi @lwang,

Thanks for your answer.

Indeed I was able to do it using RoleConfigGroup API's. However, my concern is more with the fact that the recommended model schema provided by Cloudera lists the attribute that it doesn't support.

Regards

Sandeep

Re: 'Role type configuration is supported only up to API v2' in CM API V32

lwang — Thu, 12 Sep 2019 19:58:24 GMT

Hi @SandeepSingh ,

Glad to hear the issue got resolved. When you get a chance, could you please share more details on the "recommended model schema" so I can follow up internally to see what we can improve?

Thanks,