Question: RecordBatchReader.close() behavior

[amachanic]

When working with the arrow_reader() function on a cursor object, the returned type is a RecordBatchReader. I was hoping that I could call close() on this object partway through iteration and have it cancel any server-side work and clean up the underlying resources, but instead this appears to be a no-op. (Or at least, I don't see any effect on this end.)

So: What is close() supposed to do today, if anything? And would it possible for it to do what I'm asking for?

[github-actions]

Hi @amachanic, thank you for opening this issue!

Our team will review it shortly. We aim to triage all new issues within 24-48 hours and get back to you.

If you have additional information to share, please feel free to update the issue.

Thank you for your patience!

[subrata-ms]

Hi @amachanic , Thanks for raising the bug.

Effectively, [reader.close()] today is a client-side, pyarrow-internal no-op with respect to mssql_python and the database. The only paths that actually free anything are:

1. Iterating the reader to completion (the generator returns, [arrow_batch] returns 0 rows).
2. Calling [cursor.close()] or letting the [Cursor] be garbage-collected.
3. Closing the connection.

However, this looks like a valid scenario, and we are evaluating the design and potential fix.