drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dsbos <...@git.apache.org>
Subject [GitHub] drill pull request: DRILL-3641: Doc. RecordBatch.IterOutcome (enum...
Date Mon, 17 Aug 2015 04:10:11 GMT
Github user dsbos commented on the pull request:

    https://github.com/apache/drill/pull/113#issuecomment-131674681
  
    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
possible.
    
    A timed wait would involve a (probably) arbitrary time, so presumably we avoid that if
possible.
    
    (Delegating to the next-level caller by returning NOT_YET just devolves back to this same
question.)
    
    
    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?)
    



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message