Hi, As discussed on the mailing list [1] I would like to add a feature enum to enhance our ability to evolve Arrow in a forward compatible manner and allow clients and servers to negotiate which features are supported before finalizing the features used.
The PR adds a new enum and a field on schema.fbs [2]. We may make modifications to the language in comments but this vote is whether to accept the addition of this enum and field. Details for how this will be used in flight, are not part of this change. For clarity, this change is non-breaking and fully backwards compatible. The field ensures that current libraries will be able to determine if a future library version used features that it doesn't support (by checking for out of range enum values). It will require libraries to both populate the field on writing and check values when reading. The vote will be open for at least 72 hours. [ ] +1 Accept addition of Feature enum flatbuffers field [ ] +0 [ ] -1 Do not accept addition because... [1]: https://mail-archives.apache.org/mod_mbox/arrow-dev/202006.mbox/%3CCAK7Z5T-mUB1ipO7YGqwW%3DtcW7eA8_aYvrjWAzLmHw7ZtS09naQ%40mail.gmail.com%3E [2]: https://github.com/apache/arrow/pull/7502
