Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Made ParquetConversions and its methods publicly accessible(#2148) #2149

Closed
wants to merge 1 commit into from

Conversation

saurabhagas
Copy link

No description provided.

@rdblue
Copy link
Contributor

rdblue commented Jan 26, 2021

@saurabhagas, why does this need to be public? This is an internal utility class and I don't think that we need to add it to the API.

@rdblue rdblue closed this Feb 6, 2021
@rdblue
Copy link
Contributor

rdblue commented Feb 6, 2021

I'm closing this since there was no reply. Feel free to reopen if you have time to pick it back up.

@saurabhagas
Copy link
Author

saurabhagas commented Feb 17, 2021

I'm closing this since there was no reply. Feel free to reopen if you have time to pick it back up.

@rdblue, sorry, this issue fell out of my radar. I had given the reasoning behind this change in the tracking issue: #2148 (I've edited the description slightly to help the reader). If you're convinced, please reopen the PR and accept the change. Note that, I'm only interest in the class and its ParquetConversions::fromParquetPrimitive method, not all the methods in the class.

@saurabhagas
Copy link
Author

@rdblue, can you check this PR and give your final verdict please? If the change isn't acceptable, I'll close the tracking issue as well. Thanks!

@rdblue
Copy link
Contributor

rdblue commented Feb 24, 2021

@saurabhagas, I'm not sure there's enough information in the issue to understand why a different method can't be used, or if it is a good idea to expose this. It sounds like you're constructing different schemas and using stats differently, so how much similarity is there? The Parquet values produced by this are specific to Iceberg's object model. If you're building something different from Iceberg then I would say that it makes the most sense for you to have similar code for your use case.

@saurabhagas
Copy link
Author

Thanks for the reply. Closing the issue.

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

Successfully merging this pull request may close these issues.

2 participants