While doing some Flatbuffers work, I noticed that recent compiler versions now warn about non-snake-case field names:
https://github.com/google/flatbuffers/pull/6005 It seems that the intent is for the compiler to generate "language-friendly" code (e.g. camelCase for Java) from snake_case schemas. It looks like Arrow won't be disrupted by this warning, but I am wondering if this is something that we might be able to fix at some point. Because the field names do not impact the binary format of the Flatbuffers, this would be backward and forward compatible, but it would require some code changes in various bindings (e.g. C++, but probably not Java).
