Reply
Contributor
Posts: 26
Registered: ‎09-05-2018

Cloudera Pavigator PARTITION output format change

We used to use Cloudera Enterprise 5.8 and implemented some code to fetch partitions info from Cloudera Navigator API. But after updating to current Cloudera Enterprise we got that code failing to process partitions.

Unfortunately we can't revert back to check what actually was changed.

Could you please help with providing sample JSON output for the same PARTITION for old and new versions? Did you change something in output JSON (any fields addded\removed\renamed)?

Cloudera Employee
Posts: 5
Registered: ‎03-26-2018

Re: Cloudera Pavigator PARTITION output format change

Hello @Nukala,

 

You updated from 5.8 to a newer version?  What is the new version?

Contributor
Posts: 26
Registered: ‎09-05-2018

Re: Cloudera Pavigator PARTITION output format change

5.13
Cloudera Employee
Posts: 5
Registered: ‎03-26-2018

Re: Cloudera Pavigator PARTITION output format change

@Nukala

Have you reviewed the 5.13.x API documentation found at the link below?

https://www.cloudera.com/documentation/enterprise/5-13-x/topics/cn_navigator_api_overview.html

Since you have an Enterprise license, suggest you submit a case as this is very unlikely to be resolved here..
Contributor
Posts: 26
Registered: ‎09-05-2018

Re: Cloudera Pavigator PARTITION output format change

Could you please let me know how to submit a case?
Cloudera Employee
Posts: 5
Registered: ‎03-26-2018

Re: Cloudera Pavigator PARTITION output format change

[ Edited ]

Hello Nukala,

 

The first requirement is that you in fact have a Cloudera license, which dictates the level of support your organization has.  However the Community was not designed to be a place from which to submit cases.  So primarily you would need to be an existing and supported Cloudera customer.  Are you such?

 

Thank You,

 

Bob Wells

Posts: 877
Kudos: 102
Solutions: 54
Registered: ‎04-06-2015

Re: Cloudera Pavigator PARTITION output format change

@Nukala

 

Thanks for your reply and the additional information. Since this issue is not caused by any Cloudera product defects, we’ve reached the limit of what assistance can be provided via Community support. This thread will remain open if other community peers want to contribute.

 

If you’re a Cloudera Subscription Support customer, we can connect you with your Account team to explore a possible Services engagement for this request. Let us know if you’re interested in this path, we’ll private message you to collect more information.



Cy Jervis, Community Manager


Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.

Learn more about the Cloudera Community:

Terms of Service

Community Guidelines

How to use the forum

Announcements
New solutions