[
https://issues.apache.org/jira/browse/RANGER-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057110#comment-15057110
]
Alok Lal commented on RANGER-777:
---------------------------------
Committed version that empties the kafka-security profile but leave it in place:
master - 40f225f0f103a8ad47683219afd6814c0e2d99b7
Keeping jira open for subsequent commit and for port to 0.5
> Kafka plugin should build/work with the kafka v0.9 jar with authorization
> support that have been pushed to public repos
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: RANGER-777
> URL: https://issues.apache.org/jira/browse/RANGER-777
> Project: Ranger
> Issue Type: Bug
> Components: plugins
> Affects Versions: 0.5.0
> Reporter: Alok Lal
> Assignee: Alok Lal
> Fix For: 0.5.1, 0.6.0
>
>
> Kafka team has publicly release the authorization support on version 0.9 and
> have pushed those jars into public repos.
> - With this, ranger should start compiling kafka plugins by default against
> the public interfaces.
> - If v0.9 jars do not have something that plugin was relying on then port
> those pieces to new stable released version.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
