[
https://issues.apache.org/jira/browse/MAPREDUCE-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Douglas updated MAPREDUCE-1097:
-------------------------------------
Resolution: Fixed
Hadoop Flags: [Incompatible change, Reviewed] (was: [Incompatible change])
Status: Resolved (was: Patch Available)
bq. Thought about this some more - since 0.21 hasn't been released and this is
the first version that has this contrib seems like its ok to not handle the
case of a persisted Writable with a double instead of a decimal. Changed to
incompatible to make explicit.
Since you're the sole contributor to this module, I view this as your decision.
FWIW, as it hasn't yet been released, an incompatible change is exactly the
risk early adopters take, in my opinion.
I committed this. Thanks, Omer!
> 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
> Components: contrib/vertica
> 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-3.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.
