[
https://issues.apache.org/jira/browse/PHOENIX-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14612494#comment-14612494
]
Josh Mahonin commented on PHOENIX-2088:
---------------------------------------
I'm just reading through this thread again and I should clarify that this
updated patch is only meant to prove that it's possible to use the
phoenix-spark integration without the ColumnInfoEncoderDecoder, if that's
necessary for the full solution.
All of the spark-specific column / delimiter stuff works pretty much the same
as the Pig / MapReduce integration, so whatever the right fix is that works for
both of them should be fine for Spark too.
> Prevent splitting and recombining select expressions for MR integration
> -----------------------------------------------------------------------
>
> Key: PHOENIX-2088
> URL: https://issues.apache.org/jira/browse/PHOENIX-2088
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: maghamravikiran
> Attachments: PHOENIX-2088-wip-v2.patch, PHOENIX-2088-wip.patch
>
>
> We currently send in the select expressions for the MR integration with a
> delimiter separated string, split based on the delimiter, and then recombine
> again using a comma separator. This is problematic because the delimiter
> character may appear in a select expression, thus breaking this logic.
> Instead, we should use a comma as the delimiter and avoid splitting and
> recombining as it's not necessary in that case. Instead, the entire string
> can be used as-is in that case to form the select expressions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
