[GitHub] [arrow] pitrou commented on pull request #8229: ARROW-9579: [C++] Provide the plugin API to support customized compression codec for parquet

pitrou commented on pull request #8229: URL: https://github.com/apache/arrow/pull/8229#issuecomment-887311848 Link to ML discussion: https://lists.apache.org/thread.html/r88c56e47cdd69eda23477c67c8e4ad5e66a3ccb144087082d427ffbf%40%3Cdev.arrow.apache.org%3E -- This is an automated

[GitHub] [arrow] pitrou commented on pull request #8229: ARROW-9579: [C++] Provide the plugin API to support customized compression codec for parquet

pitrou commented on pull request #8229: URL: https://github.com/apache/arrow/pull/8229#issuecomment-887311279 I'm going to close this PR as stale, and because the approach here is too heavy-weight as already discussed. -- This is an automated message from the Apache Git Service. To

[GitHub] [arrow] pitrou commented on pull request #8229: ARROW-9579: [C++] Provide the plugin API to support customized compression codec for parquet

pitrou commented on pull request #8229: URL: https://github.com/apache/arrow/pull/8229#issuecomment-696176912 Hmm, reading the mailing-list discussion again, I don't think we had agreed on a design. The first question for me is what the end-user API should be. * should the user calling

[GitHub] [arrow] pitrou commented on pull request #8229: ARROW-9579: [C++] Provide the plugin API to support customized compression codec for parquet

pitrou commented on pull request #8229: URL: https://github.com/apache/arrow/pull/8229#issuecomment-696176912 Hmm, reading the mailing-list discussion again, I don't think we had agreed on a design. The first question for me is what the end-user API should be. * should the user calling