Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Nit fixes to URL-encoding of partition field names #1499
Nit fixes to URL-encoding of partition field names #1499
Changes from 4 commits
8ba2c2f
d303e13
a4bb503
312b442
0aa6442
c75d637
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes in this file address #1457 (comment)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we can either do this and run
make_compatible_name
for every test caseor we can set
make_compatible_name
as optional and only run for the specific use casewhich one do you prefer?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, not sure I understand. If it's always going to be
pyiceberg.schema.make_compatible_name
, doesn't it make more sense to be enabled by a boolean argument that we only set toTrue
for the special field test case? I'm probably misunderstanding here againThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(Aside: it's not easy to have default value for a
pytest.mark.parametrize
arg I think which is why I specifiedNone
each time before - and probably why there was no e.g.spark_create_table_sql_for_justification: str = None
before that too)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh i didn't know that! My comment was based on the fact that we can set a default
None
value.yea thats also the point i want to make. make it clear that only certain test cases requires
make_compatible_name
but also, this is a nit comment, we dont necessary have to do this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah not sure. I marginally prefer leaving it as it is now - it reads more nicely, prevents
None
s/False
s mostly everywhere, sanitisation is fast so I don't think it'll causes a cumulative slowdown even when done for several test cases.