drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jacques Nadeau <jacq...@apache.org>
Subject Re: what is the correct behavior when an upstream operator returns STOP
Date Mon, 04 May 2015 17:11:10 GMT
In general, an operator should release its resources as soon as it can.  I
believe Steven is working on a patch to make all resource intensive
operators do just this.

On Mon, May 4, 2015 at 9:47 AM, Abdel Hakim Deneche <adeneche@maprtech.com>
wrote:

> What is the correct behavior for an operator when it receives an
> IterOutcome.STOP from upstream:
> 1. should it just stop right away and return STOP downstream ?, or
> 2. should it cleanup it's resources before returning STOP downstream ?
>
> Some operators follow 1 and others (like OrderedPartitionRecordBatch)
> follow 2.
>
> --
>
> Abdelhakim Deneche
>
> Software Engineer
>
>   <http://www.mapr.com/>
>
>
> Now Available - Free Hadoop On-Demand Training
> <
> http://www.mapr.com/training?utm_source=Email&utm_medium=Signature&utm_campaign=Free%20available
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message