You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Parquet relies heavily on a few Hadoop classes, such as its Configuration class, which is used throughout Parquet's reading and writing logic. If we include our own interface for this, this could potentially allow users to use Parquet's readers and writers without the Hadoop dependency later on.
In order to preserve backward compatibility and avoid breaking downstream projects, the constructors and methods using Hadoop's constructor should be preserved for the time being, though I would favour deprecation in the near future.
Parquet relies heavily on a few Hadoop classes, such as its Configuration class, which is used throughout Parquet's reading and writing logic. If we include our own interface for this, this could potentially allow users to use Parquet's readers and writers without the Hadoop dependency later on.
In order to preserve backward compatibility and avoid breaking downstream projects, the constructors and methods using Hadoop's constructor should be preserved for the time being, though I would favour deprecation in the near future.
This is part of an effort that has been discussed on the dev mailing list.
Reporter: Atour Mousavi Gourabi / @amousavigourabi
Assignee: Atour Mousavi Gourabi / @amousavigourabi
Related issues:
PRs and other links:
Note: This issue was originally created as PARQUET-2347. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: