as we have moved the Arrow<->Parquet C++ integration into parquet-cpp,
we still have to decide on how we are going to proceed with the
Arrow<->Parquet Python integration. For the moment, it seems that the
best way to go ahead is to pull the pyarrow.parquet module out into a
separate Python package. From an organisational point, I'm unclear how I
should proceed here. Should we put this in a separate repo? If so, as
part of the Apache organisation?
- Python Parquet package Uwe Korn