zeroshade commented on pull request #11310: URL: https://github.com/apache/arrow/pull/11310#issuecomment-941642847
I was able to narrow this down to being related to the application metadata. Unlike the C++ flight integration client, the Java one does not validate the metadata in the response to the DoGet, only in the DoPut, if I modify the Go flight integration server to *not* send the app metadata field with the DoGet responses, then it succeeds without issue. But when it does send the metadata, it fails claiming a memory leak of the exact number of bytes that were sent via app metadata (1 byte per message). I don't know why it doesn't have this memory leak when consuming from the C++ flight integration server which appears to be sending the metadata in the same way unless i'm missing something. I'm not particularly well versed with java or the java implementation so any assistance at all in tracking down what's going on and whether it's a Go bug or a Java bug would be extremely helpful. Thanks much! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
