A recent issue with the JDBC adapter [1] made me realize we aren't doing enough to communicate to consumers the maturity of various modules within arrow. From the issue, it also seems like it is surprising that everything is based off of off-heap data access.
To help with this I added a description to each module in a new PR [2] with a preliminary annotation experimental/contrib [3] modules. The annotations match my understanding of the current state of the world, but please correct them if I got something wrong. If anyone knows how tags on mvnrepository [4] are generated, I think it would also be good to populate tags for experimental, contrib and off-heap/nio code. Is there anything else we could be doing? Thanks, Micah [1] https://issues.apache.org/jira/browse/ARROW-6206 [2] https://github.com/apache/arrow/pull/5151 [3] My rough definitions for each annotation are: 1. Contrib - Limited users, not well tested in production environments. Not necesserily optimized. 2. Experimental - Not finalized (very likely to be breaking API changes). Better definitions are welcome :) [4] https://mvnrepository.com/artifact/org.apache.arrow/arrow-vector
