You could also use labels in JIRA to mark issues that introduce API changes
On Mon, Jul 22, 2019 at 4:42 AM Fan Liya <liya.fa...@gmail.com> wrote: > > @Uwe L. Korn > > Thanks a lot for the good suggestion. > I will create a new file to track the changes. > > Best, > Liya Fan > > On Mon, Jul 22, 2019 at 5:03 PM Uwe L. Korn <uw...@xhochy.com> wrote: > > > Hallo Liya, > > > > what about having this as part of the repository, e.g. > > java/api-changes.md? We have an auto-generated changelog that is quite > > verbose but having such documentation for consumers of the Java library > > would be really helpful as it is gives a denser packed information on > > upgrading versions. > > > > Cheers > > Uwe > > > > On Mon, Jul 22, 2019, at 4:54 AM, Fan Liya wrote: > > > Hi all, > > > > > > Let's track the API behavior changes in this email thread, so as not > > forget > > > about them for the next release. > > > > > > ARROW-5842 <https://issues.apache.org/jira/browse/ARROW-5842>: the > > > semantics of lastSet in ListVector changes. In the past, it refers to the > > > next index that will be set; now it points to the last index that is > > > actually set. > > > > > > ARROW-5973 <https://issues.apache.org/jira/browse/ARROW-5973>: The > > > semantics of the get methods for VarCharVector, VarBinaryVector, and > > > FixedSizeBinaryVector changes. If the past, if the validity bit is clear, > > > the methods throw throws an IllegalStateException when > > > NULL_CHECKING_ENABLED is set, or returns an empty object when the flag is > > > not set. Now, the get methods returns a null if the validity bit is > > clear. > > > > > > Best, > > > Liya Fan > > > > >
