drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-3641) Document RecordBatch.IterOutcome (enumerators and possible sequences)
Date Mon, 17 Aug 2015 04:10:45 GMT

    [ https://issues.apache.org/jira/browse/DRILL-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698989#comment-14698989

ASF GitHub Bot commented on DRILL-3641:

Github user dsbos commented on the pull request:

    Hey, what happens (what is a caller supposed to do) if the caller receives NOT_YET but
the caller has no local work to do?
    (Re-calling next() immediately would yield a spin wait, so presumably we avoid that if
    A timed wait would involve a (probably) arbitrary time, so presumably we avoid that if
    (Delegating to the next-level caller by returning NOT_YET just devolves back to this same
    Is there another general option (general in the sense of callers and callees that don't
know anything about each other)?
    Or is it that NOT_YET is used only between pairs of callers and callee that know enough
about each other to coordinate somehow so they can avoid spin waits and aribitrary delays?)

> Document RecordBatch.IterOutcome (enumerators and possible sequences)
> ---------------------------------------------------------------------
>                 Key: DRILL-3641
>                 URL: https://issues.apache.org/jira/browse/DRILL-3641
>             Project: Apache Drill
>          Issue Type: Bug
>            Reporter: Daniel Barclay (Drill)
>            Assignee: Daniel Barclay (Drill)

This message was sent by Atlassian JIRA

View raw message