wjones127 commented on issue #15280: URL: https://github.com/apache/arrow/issues/15280#issuecomment-1379489392
I spent some time looking at the necessary changes, and it occured to me with have a bit of a mess with namespaces as well. We introduced a library called `libarrow_substrait` and that contains the namespace `arrow::engine`. Nothing else uses that namespace. Acero (i.e. the code in `src/arrow/compute/exec` all lives in the `arrow::compute` namespace. Although I'd like to have this issue somewhat limited in scope, it would be nice to know where we are trying to go with the library structure. I created a document outlining the current structure, an a couple ideas of a slightly more sane structure: https://docs.google.com/document/d/1IcQfqFlvMgM3GreNbAvax0_2XKFHRdmcs9nqTPQlhOs/edit?usp=sharing I welcome any comments or alternative suggestions. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
