I think behavior of most the methods in the class should be "write fully" from a user's perspective. However, I see dilemmas in the API design: 1. If `write(ByteBuffer buffer)` is "not write fully" but other methods (e.g., `write(ArrowBuf buffer)` ) are "write fully", then naming can be confusing (some write* methods will be "write fully" and some won't) . 2. If we add "Fully" in all methods that have "write fully" behavior, then the methods name becomes long and some of them won't make sense, e.g., `writeIntLittleEndianFully`
3. Don't follow WriteByteChannel semantics and have `write(ByteBuffer buffer)` to be "write fully". This makes methods in this class consistent but doesn't follow WriteByteChannel semantics... None of these is ideal unfortunately.. [ Full content available at: https://github.com/apache/arrow/pull/2594 ] This message was relayed via gitbox.apache.org for [email protected]
