SNOW-980272: Direct memory not freed / deallocated when using ARROW result format and streaming

[koszta5]

Please answer these questions before submitting your issue.
In order to accurately debug the issue this information is required. Thanks!

1. What version of JDBC driver are you using?
   3.14.3

2. What operating system and processor architecture are you using?
   RedHat Linux 7.9. , x86_64

3. What version of Java are you using?
   JDK 11 - Temurin-11.0.19+7

4. What did you do?
   Use JDBC driver to execute select * from MY_TABLE

• table has 20+ mil of rows
• we are using JDBC template in a streaming fashion ( List query(String sql, RowMapper rowMapper, @nullable Object... args) throws DataAccessException)

5. What did you expect to see?
   As are we streaming the data (steam batch from Snowflake, insert into target, clear batch) there should be no limit for overall data processed (GC takes care of cleaning up object no longer needed)

   What should have happened and what happened instead?

• internally JDBC uses Apache Arrow and direct memory allocation which is only freed after whole statement execution is finished
• this is a really bad approach as we consume the data on the fly and stream them to target
• No size of direct memory would be enough to handle such a large dataset (at 1 go)
• we always ran out of direct memory

6. Can you set logging to DEBUG and collect the logs?

• yes but this is a design issue
• why is direct memory not being freed up as rs.next() is getting called --> this would be a simple fix

7. Workaround

• Workaround is to force JSON query result set format prior to statement execution (alter session set JDBC_QUERY_RESULT_FORMAT='JSON')
• This does not allocate direct memory and therefore uses GC after rs.next() is called

The current behaviour is not in sync with common JDBC drivers of other DB systems