hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Kimball (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1097) Changes/fixes to support Vertica 3.5
Date Wed, 09 Dec 2009 19:20:18 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788248#action_12788248

Aaron Kimball commented on MAPREDUCE-1097:

VerticaRecord does implement Writable, so it's conceivable that users may have stored VerticaRecord
instances in SequenceFiles on HDFS; regardless of whether you intended this to be an internal-only
class, users do funny things.. but hopefully not too many will have done so. I don't think
it's a big problem, especially since this is a fairly young contrib module. Some volatility
should probably be expected here.

At the very least, though, you should mark this issue as an "incompatible change" (see the
"Edit this issue" link on the left).

Thanks for making the other changes. I'm +0.75 on this patch -- would appreciate it if someone
else could weigh in on the issue of whether they think persistent VerticaRecord incompatibility
is problematic or if they've got a creative solution. (Some day we'll all just use Avro and
schema evolution will take care of all of this... but until then..)

> Changes/fixes to support Vertica 3.5
> ------------------------------------
>                 Key: MAPREDUCE-1097
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1097
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>    Affects Versions: 0.21.0
>         Environment: Hadoop 0.21.0 pre-release and Vertica 3.5
>            Reporter: Omer Trajman
>            Assignee: Omer Trajman
>            Priority: Minor
>             Fix For: 0.21.0
>         Attachments: MAPREDUCE-1097-2.patch, MAPREDUCE-1097.patch
> Vertica 3.5 includes three changes that the formatters should handle:
> 1) deploy_design function that handles much of the logic in the optimize method.  This
improvement uses deploy_design if the server version supports it instead of orchestrating
in the formatter function.
> 2) truncate table instead of recreating the table
> 3) numeric, decimal, money, number types (all the same path)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message