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

Custom parsers / null literals should use pre-legalized names (issue #190) #223

Merged
merged 1 commit into from
Nov 13, 2024

Conversation

kosak
Copy link
Contributor

@kosak kosak commented Nov 9, 2024

Fixes #190

Not that #190 misidentifies the root cause as having to do with reserved keywords. This is not correct because the library doesn't care whether a column header is a reserved keyword. The actual root cause is an interaction between the user-supplied "legalizer" and user-specified parsers or null literals that are specified by column names. Specifically the question is whether column names mentioned in CsvSpecs.Builder.putParserForName and CsvSpecs.Builder.putNullValueLiteralsForName should refer to the name that the column had before it was transformed by the legalizer, or after. The expected behavior is "before", but prior to this fix the library was doing the "after" behavior.

@kosak kosak force-pushed the kosak_legalizer-names branch 2 times, most recently from 8c1dc43 to 89bff04 Compare November 9, 2024 01:00
@kosak kosak self-assigned this Nov 9, 2024
@kosak kosak merged commit 4c104f0 into deephaven:main Nov 13, 2024
3 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Nov 13, 2024
@kosak kosak deleted the kosak_legalizer-names branch November 13, 2024 20:11
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Reserved keyword column names don't use user-specified parser
2 participants