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

Ensure the wrong number of parameters in a call to deephaven.ParquetTools.writeTable generates an error. #1652

Merged
merged 2 commits into from
Dec 7, 2021

Conversation

jcferretti
Copy link
Member

As it is right now, and due to a mistake in an earlier change on that file, a call to deephaven.ParquetTools.writeTable with the wrong number of parameters (eg, 1, like just the filename or just the table name), silently does nothing instead of alerting the user
that something is wrong; this was not intentional and is misleading, eg, a user can mistake the (wrongful) no output for success.
I noticed this recently after having fell myself to that trap in some debugging session: I forgot one argument and for a while couldn't understand what was going on when the file was not showing up.

jmao-denver
jmao-denver previously approved these changes Dec 7, 2021
Copy link
Contributor

@jmao-denver jmao-denver left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because writeTable() is generated, I understand the need for adding such 'unpythonic' check. It will not be necessary if we hand-wrap the class.

@jmao-denver jmao-denver merged commit a9091be into deephaven:main Dec 7, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Dec 7, 2021
@jcferretti jcferretti deleted the cfs-parquettools-write-0 branch December 9, 2021 04:29
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants