> > Let's take an example: > > * Dremio can execute SQL and uses Arrow as its native runtime format > * Apache Spark can execute SQL and offers UDF support with Arrow > format, i.e. so using Arrow for IO > > Both of these projects can say that they "use Apache Arrow", but the > extent to which Arrow is a key ingredient may not be obvious to the > average onlooker. To have more "Arrow-native" systems seems like one > of the missions of the project. >
I'm not following you here. Are you suggesting that these systems are Arrow-native or not Arrow-native? Or that one is and the other is not? What does Arrow-native mean to you? Do you think there is enough problems around this right now that we need to do something? It seems like you're concerned about people claiming they are using Arrow when they aren't quite. Right now, it seems like the community mostly benefits from people saying they are using Arrow. Have you seen situations where users/consumers were frustrated because something was Arrow but not really Arrow?
