You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Philip Zeyliger (JIRA)" <ji...@apache.org> on 2010/01/11 19:13:54 UTC
[jira] Commented: (MAPREDUCE-1368) Vertica adapter doesn't use
explicity transactions or report progress
[ https://issues.apache.org/jira/browse/MAPREDUCE-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798758#action_12798758 ]
Philip Zeyliger commented on MAPREDUCE-1368:
--------------------------------------------
Would transactions help you? A speculative task can show up right after the map task decides to commit the transaction, and you're in the same place.
> Vertica adapter doesn't use explicity transactions or report progress
> ---------------------------------------------------------------------
>
> Key: MAPREDUCE-1368
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1368
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 0.21.0
> Reporter: Omer Trajman
> Assignee: Omer Trajman
> Fix For: 0.21.0
>
>
> The vertica adapter doesn't use explicit transactions, so speculative tasks can result in duplicate loads. The JDBC driver supports it so the fix is pretty minor. Also the JDBC driver commits synchronously and the adapter needs to report progress even if it takes longer than the timeout.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.