This shouldn't be a problem Edmon. Think of parquet files as a file format - like ZIP files Similarly to how you can generate .ZIP files in one OS and unzip them into another OS - parquet should be transparent
The only limitation i can think of, is in the object model. If you are using Avro to describe your objects - and you are using an Avro feature introduced in specifications 1.8.0 you could be having issues when trying to read them from a platform that has 1.7.6 Avro spec/libraries in the classpath On Thu, Apr 14, 2016 at 3:16 PM, Edmon Begoli <[email protected]> wrote: > What are the portability limitations of Parquet generated data files? > > I.e. what determines if the parquet data file generated on one OS can or > cannot be moved to another? >
