Skip to content
This repository has been archived by the owner on Sep 2, 2024. It is now read-only.

Can we get back onto un-patched upstream? #47

Open
ash211 opened this issue Nov 18, 2022 · 0 comments
Open

Can we get back onto un-patched upstream? #47

ash211 opened this issue Nov 18, 2022 · 0 comments
Assignees

Comments

@ash211
Copy link

ash211 commented Nov 18, 2022

https://github.com/palantir/parquet-mr/blob/master/FORK.md shows that there's a difference in how we resolved PARQUET-686 vs upstream. Looking at history of FORK.md, there were other changes in the past but they've now been removed, so this is possibly the last remaining diff vs upstream.

Is there any way for us to resolve this diff and be able to use unpatched apache/parquet-mr across all our internal codebase? Or will we forever be on this patch due to having data created by the Palantir fork that cannot be read correctly in Apache upstream?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants