Description
I understand HADOOP-16730/HADOOP-16916 is specifically made for Ranger, but I am not sure how Ranger consumes this feature. The interface SASTokenProvider has a number of member fields that changed variable names in HADOOP-16916, breaking the compatibility between 3.3.0 and 3.3.1.
As a matter of fact, the feature HADOOP-16730 itself was merged in 3.3.0 not 3.3.1. I just corrected it today.
Raise this jira and mark it as a blocker for 3.3.1. But if this isn't a big deal then we can downgrade, because, well, this feature was not officially in the 3.3.0 release.
Attachments
Issue Links
- relates to
-
HADOOP-17671 Run jacc to check for Hadoop's Java API compat
- Resolved