Allow flexible schema config definitions#3
Merged
Conversation
AMarinhoSN
approved these changes
Jul 29, 2025
| mapped_vals[mapped_valname] = val_v | ||
| mapped[k] = mapped_vals | ||
|
|
||
| print(f"{mapped = }") |
There was a problem hiding this comment.
Should this print be here?
If not, remove or replace with logger.debug or something
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Users can provide a config file (
.yaml) which specifies how column names and value vocabularies correspond between the reference and query tables. This update allows users to specify in the config only those column names or value maps that are different, and does not require the user to explicitly account for all columns as before.A "full" example of the config file is in the README, and additional examples are now added in the form of test input files.