[
https://issues.apache.org/jira/browse/MAPREDUCE-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12777516#action_12777516
]
Enis Soztutar commented on MAPREDUCE-1203:
------------------------------------------
Yes, unfortunatelly, JDBC does not specify the behavior for this. As far as I
remember, execute batch returns the number of documents that it is able to
send.
Another use case, that I want at some point is to enable processing even after
some records fail. Logically, failing to send a few records should be
acceptable. Considering this use case and yours implementing different fail
strategies makes sense. I guess we could first try execute batch, then fall
back to execute update one by one.
Alternatively, we could write a wrapper Input format, which limits the number
of records in the map tasks so that there is less to send at each task.
> DBOutputFormat: add batch size support for JDBC and recieve DBWritable
> object in value not in key
> --------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-1203
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1203
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Reporter: Alexander Schwid
> Assignee: Aaron Kimball
> Priority: Minor
> Attachments: HADOOP-4331.patch, patch.txt
>
>
> package mapred.lib.db
> added batch size support for JDBC in DBOutputFormat
> recieve DBWritable object in value not in key in DBOutputFormat
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
