Re: [DISCUSS] C++ code sharing amongst Apache {Arrow, Kudu, Impala, Parquet}

I also support the idea of creating an "apache commons modern c++" style library, maybe tailored toward the needs of columnar data processing tools. I think APR is the wrong project but I think that *style* of project is the right direction to aim. I agree this adds test and release process compl

Re: [DISCUSS] C++ code sharing amongst Apache {Arrow, Kudu, Impala, Parquet}

Hey folks, As Henry mentioned, Impala is starting to share more code with Kudu (most notably our RPC system, but that pulls in a fair bit of utility code as well), so we've been chatting periodically offline about the best way to do this. Having more projects potentially interested in collaboratin

Re: [DISCUSS] C++ code sharing amongst Apache {Arrow, Kudu, Impala, Parquet}

hi Miki, No, I don't think so. APR is a portable C library. The code we are talking about would be intended for use in C++11/14 projects like Impala and Kudu (and Arrow and Parquet). Wes On Sun, Feb 26, 2017 at 1:58 PM, Miki Tebeka wrote: > Can't some (most) of it be added to APR

Re: [DISCUSS] C++ code sharing amongst Apache {Arrow, Kudu, Impala, Parquet}

Can't some (most) of it be added to APR ? On Sun, Feb 26, 2017 at 8:12 PM, Wes McKinney wrote: > hi Henry, > > Thank you for these comments. > > I think having a kind of "Apache Commons for [Modern] C++" would be an > ideal (though perhaps initially more labor intensive)

Re: [DISCUSS] C++ code sharing amongst Apache {Arrow, Kudu, Impala, Parquet}

hi Henry, Thank you for these comments. I think having a kind of "Apache Commons for [Modern] C++" would be an ideal (though perhaps initially more labor intensive) solution. There's code in Arrow that I would move into this project if it existed. I am happy to help make this happen if there is i