[
https://issues.apache.org/jira/browse/PHOENIX-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15859783#comment-15859783
]
Josh Elser commented on PHOENIX-3214:
-------------------------------------
bq. Definitely would appreciate a second set of eyes on it though. An ounce of
prevention is worth at least a pound of cure when it comes to potential
classpath issues.
I took a look at the dependency list and I don't see anything outwardly bad
that Kafka brought in which is good.
Sadly, I saw other things that were inherited that we were already doing wrong
:). I think we're good for this contribution.
> Kafka Phoenix Consumer
> ----------------------
>
> Key: PHOENIX-3214
> URL: https://issues.apache.org/jira/browse/PHOENIX-3214
> Project: Phoenix
> Issue Type: New Feature
> Reporter: Kalyan
> Assignee: Josh Mahonin
> Fix For: 4.10.0
>
> Attachments: PHOENIX-3214.addendum-0.98.patch,
> PHOENIX-3214.addendum-1.1.patch, PHOENIX-3214-docs.patch,
> PHOENIX-3214-final.patch, PHOENIX-3214_license-2.patch,
> PHOENIX-3214_license.patch, PHOENIX-3214.patch, PHOENIX-3214-updated-1.patch,
> PHOENIX-3214-updated-2.patch, PHOENIX-3214-updated.patch
>
>
> Providing a new feature to Phoenix.
> Directly ingest Kafka messages to Phoenix.
> Similar to flume phoenix integration.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
