You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[reporter="jvs", created="Fri, 27 Jan 2006 19:59:39 -0500 (GMT-05:00)"]
This would be similar to the way we already added the RestartableIterator extension. Without this, iterators like FarragoJavaUdxIterator have to go through contortions in order to avoid becoming resource leaks.
The text was updated successfully, but these errors were encountered:
[author="jvs", created="Sat, 11 Feb 2006 15:31:23 -0500 (GMT-05:00)"]
Also support propagation of special "YIELD_ROW" objects which would allow Java iterators to be properly scheduled as ExecStreams.
[author="jvs", created="Fri, 2 Feb 2007 02:08:34 -0500 (GMT-05:00)"]
Stephan already took care of the yield part, but the close part still remains to be fixed. In particular, currently when a UDX is closed without the client draining all of its results, it sees an abort and posts an exception, which is confusing.
[reporter="jvs", created="Fri, 27 Jan 2006 19:59:39 -0500 (GMT-05:00)"]
This would be similar to the way we already added the RestartableIterator extension. Without this, iterators like FarragoJavaUdxIterator have to go through contortions in order to avoid becoming resource leaks.
The text was updated successfully, but these errors were encountered: