[
https://issues.apache.org/jira/browse/PHOENIX-6064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17183415#comment-17183415
]
Lars Hofhansl commented on PHOENIX-6064:
----------------------------------------
{quote}Anyone who wants to make Tephra work can show up and do the work to make
it happen. Same operating model we've always followed.
{quote}
I do not agree with that statement. At all!
Next time we find a hard problem with (say) local indexes we also just going
to make them optional?
If things are broken we should fix them, not make them optional.
I do agree that an expedient - temporary - workaround here is OK.
> Make Tephra support optional
> ----------------------------
>
> Key: PHOENIX-6064
> URL: https://issues.apache.org/jira/browse/PHOENIX-6064
> Project: Phoenix
> Issue Type: Improvement
> Components: core, tephra
> Affects Versions: 5.1.0
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
> Fix For: 5.1.0
>
> Attachments: PHOENIX-6064.master.v1.patch
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Tephra has and old Guava dependency, that cannot be removed due to Twill
> depending on it. Removing the Twill dependency from Tephra is possible, but
> not trivial.
> This Guava has CVEs, which will show up in static analysis tools, which will
> cause some potential users not to adopt Phoenix.
> Provide an option to build Phoenix without Tephra, and its problematic
> dependencies.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
