[
https://issues.apache.org/jira/browse/PIG-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12900566#action_12900566
]
Ashutosh Chauhan commented on PIG-1420:
---------------------------------------
> I could not figure out how to re-open this issue.
Issues marked as resolved cannot be reopened. Once the patch is committed,
commiter should mark issue as resolved, since resolved issues can be reopened
before release is rolled out. When the release is rolled out, resolved issues
should be marked as closed, since there is no point in reopening an issue which
has already been released. If more work needs to be done on that issue new jira
should be created for it for future releases.
> Make CONCAT act on all fields of a tuple, instead of just the first two
> fields of a tuple
> -----------------------------------------------------------------------------------------
>
> Key: PIG-1420
> URL: https://issues.apache.org/jira/browse/PIG-1420
> Project: Pig
> Issue Type: Improvement
> Components: impl
> Affects Versions: 0.8.0
> Reporter: Russell Jurney
> Assignee: Russell Jurney
> Fix For: 0.8.0
>
> Attachments: addconcat2.patch, PIG-1420.2.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> org.apache.pig.builtin.CONCAT (which acts on DataByteArray's internally) and
> org.apache.pig.builtin.StringConcat (which acts on Strings internally), both
> act on the first two fields of a tuple. This results in ugly nested CONCAT
> calls like:
> CONCAT(CONCAT(A, ' '), B)
> The more desirable form is:
> CONCAT(A, ' ', B)
> This change will be backwards compatible, provided that no one was relying on
> the fact that CONCAT ignores fields after the first two in a tuple. This
> seems a reasonable assumption to make, or at least a small break in
> compatibility for a sizable improvement.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
