It is better to put the filter operator in the same container as the Avro operator.
Setting emitBatchSize will not help, it just limits the number of tuples emitted per *emitTuples* call and the *emitTuples* is called multiples, negating the effect of reducing the batch size. On Tue, May 30, 2017 at 10:33 AM AJAY GUPTA <ajaygit...@gmail.com> wrote: > You can set the property "emitBatchSize". This limits the number of tuples > emitted per window. Default value is 1000. > > > > Ajay > > On Tue, May 30, 2017 at 10:51 PM, Vivek Bhide <bhide.vi...@gmail.com> > wrote: > >> Thank you.. I understand that partitioning is one of the options but is >> there >> a way to decrease the emit rate? Reason I am interested in this option in >> the upstream operator is fileReader operator and down stream operator is >> filter operator. I tries partitioning the filter operator but still I see >> this warning sooner or later so to avoid the application getting clogged >> is >> there a way I can limit the emit rate of filereader operator? >> >> Regards >> Vivek >> >> >> >> -- >> View this message in context: >> http://apache-apex-users-list.78494.x6.nabble.com/Exceeded-allowed-memory-block-for-AvroFileInputOperator-tp1651p1655.html >> Sent from the Apache Apex Users list mailing list archive at Nabble.com. >> > >
