IFrameWriter's state transitions are not guaranteed within SuperActivity nodes

[GoogleCodeExporter]

Via ASTERIX: A search query is aborted by the lock manager due to timing out. 
When this happens, the IndexSearchOperatorNodePushable should have its close 
method called on it (at some point).

The steps to reproduce using ASTERIX are:
use dataverse demo;

create type TweetType as closed {
 id: string,
 username : string,
 location : string,
 text : string,
 timestamp : string
}       

create feed dataset Tweets(TweetType)
using pull_twitter (("query"="Lakers"),("interval"="10"))
primary key id;

//------

use dataverse demo;

begin feed Tweets;

//------
// after some data is let through by the feed ...

use dataverse demo;

let $c := count(for $x in dataset Tweets return $x)
return $c

Original issue reported on code.google.com by zheilb...@gmail.com on 27 Apr 2013 at 2:46

[GoogleCodeExporter]

Update: This can happen only within a SuperActivity node. If an operator inside 
the SA throws an exception in nextFrame(), the its close() method is not 
guaranteed to be called. My guess is that the fail() methods will not be called 
either, but that's not verified.

Original comment by zheilb...@gmail.com on 30 Apr 2013 at 4:34

• Changed title: IFrameWriter's state transitions are not guaranteed within SuperActivity nodes

[GoogleCodeExporter]

Original comment by zheilb...@gmail.com on 11 May 2013 at 7:58

• Added labels: Priority-Critical
• Removed labels: Priority-Medium