avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Carey (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AVRO-513) java mapreduce api should pass iterator of matching objects to reduce
Date Mon, 14 Jun 2010 22:14:16 GMT

    [ https://issues.apache.org/jira/browse/AVRO-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878775#action_12878775

Scott Carey commented on AVRO-513:

bq. Not sure about an interrupt signal being intercepted, or not being delivered. But I think
it's possible that the interrupt occurs between the check on "done" and the call to take(),
so the call to take() would go ahead and cause a deadlock.

I think all Java blocking I/O and queue operations check the interrupted status on the thread
before sleeping/waiting.  Or more precisely --the JVM checks it before the thread yields,
and will throw the interrupted exception if the flag is set.

> java mapreduce api should pass iterator of matching objects to reduce
> ---------------------------------------------------------------------
>                 Key: AVRO-513
>                 URL: https://issues.apache.org/jira/browse/AVRO-513
>             Project: Avro
>          Issue Type: Improvement
>          Components: java
>            Reporter: Doug Cutting
>            Assignee: Doug Cutting
>             Fix For: 1.4.0
>         Attachments: AVRO-513.patch, AVRO-513.patch
> The Java mapreduce API added in AVRO-493 requires reducers implementations to explicitly
detect sequences of matching data.
> Rather the reduce method might better look something like:
>    void reduce(Iterator<IN>, Collector<OUT>);
> Where all equal values are passed in a single call.

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

View raw message