You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@parquet.apache.org by Edmon Begoli <eb...@gmail.com> on 2016/04/14 14:16:00 UTC
Portability limitations of Parquet
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?
Re: Portability limitations of Parquet
Posted by Julien Le Dem <ju...@dremio.com>.
what Nong said.
The format is independent of the OS.
https://github.com/apache/parquet-format/blob/master/README.md
On Thu, Apr 14, 2016 at 9:53 AM, Nong Li <no...@gmail.com> wrote:
> The files should be completely portable. Everything is specified in an
> platform/OS independent way.
>
> On Thu, Apr 14, 2016 at 5:16 AM, Edmon Begoli <eb...@gmail.com> 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?
> >
>
--
Julien
Re: Portability limitations of Parquet
Posted by Nong Li <no...@gmail.com>.
The files should be completely portable. Everything is specified in an
platform/OS independent way.
On Thu, Apr 14, 2016 at 5:16 AM, Edmon Begoli <eb...@gmail.com> 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?
>
Re: Portability limitations of Parquet
Posted by Antonios <An...@Landoop.com>.
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 <eb...@gmail.com> 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?
>