Hi, Actually there is a repo at https://github.com/apache/parquet-testing that may be used for making sure that the Java, C++ and other implementations are interoperable. But in the context of a parquet-format release I don't think we need tests for the interoperability of implementations, because parquet-format is only about the specification which is independent of language binding.
Br, Zoltan On Thu, Jun 20, 2019 at 5:49 PM Jim Apple <[email protected]> wrote: > > Regarding your question, I don't have an opinion on 1, but I think 2 is > > very important. In the end, the parquet format is nothing more than a > > couple of Thrift definitions. I would suggest writing good unit tests to > > ensure that the bloom filters behave in the same manner. > > I agree, it is important. The Bloom filter tests can be run cross-language > now, but the running is manual. IIRC we were stuck on not having a repo for > the binaries to live in. I think such a repo would be valuable for the > format in general, not just for the Bloom filters, and the magnitude of > that is part of what makes me suggest a release even though that repo (and > accompanying tests) doesn't exist yet. > > > The release process can be done by a committer, but also requires the > > involvement of at least 3 PMC's [1] to get the binding votes to get the > > release signed off. > > Yes, indeed. A committer must be involved even before the "[VOTE]" thread. >
