You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Alok Lal (JIRA)" <ji...@apache.org> on 2015/12/15 06:02:46 UTC
[jira] [Comment Edited] (RANGER-777) Kafka plugin should build/work
with the kafka v0.9 jar with authorization support that have been pushed to
public repos
[ https://issues.apache.org/jira/browse/RANGER-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057110#comment-15057110 ]
Alok Lal edited comment on RANGER-777 at 12/15/15 5:01 AM:
-----------------------------------------------------------
Committed version that empties the kafka-security profile but leave it in place:
master - 40f225f0f103a8ad47683219afd6814c0e2d99b7
0.5 - 0b73cdfbbe3130eb881d8516ae7d92e0e237c541
Keeping jira open for subsequent commit (to completely get rid of {{kafka-security}} profile from the {{pom}} file).
was (Author: aloklal99):
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)