Repository navigation
fix(sigma): record dropped keys when a relationship's column arrays have unequal length #406
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
Merged
jbonofre
merged 3 commits into
apache:main
from
AmirF194:fix/sigma-relationship-arity-mismatch
Sep 27, 2026
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
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.
Now
core-spec/spec.md(Relationship) states: "Both arrays must have the same number of columns". It's not something we should warn and proceed, it's a "real" issue.The PR here handles the identical condition by recording a
ConverterIssueand then converting viazip(), which silently truncates to the shorter array. That's inconsistent with the spec statement, and it means a document that skipsvalidate.pygets corrupted output from the converter instead of being rejected.We already have what we need:
converter_issues.pydefinesConverterError, raised when the input cannot converted at all, as opposed to partial, lossy conversion that aConverterIssuean describe. This file already uses it for structurally invalid input (emptysemantic_model).An arity mismatch is a spec-invalid input, not a legal-but-lossy translation gap like
EXPRESSION_NOT_TRANSLATABLE.I suggest raising
ConverterErrorhere instead of appending aConverterIssueand continuing.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.
@khush-bhatia FYI, see my request change here (about
ConverterError).