Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FRG-30] enhance ITERATOR calling convention to allow Java iterators to receive a notification on cursor close #840

Open
dynamobi-build opened this issue Dec 30, 2011 · 3 comments

Comments

@dynamobi-build
Copy link

[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.

@dynamobi-build
Copy link
Author

[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.

@dynamobi-build
Copy link
Author

[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.

@dynamobi-build
Copy link
Author

[author="jvs", created="Sat, 17 May 2008 21:41:32 -0500 (GMT-05:00)"]
See also FRG-320.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant