-
Notifications
You must be signed in to change notification settings - Fork 132
Using signals schema instead of columns to calculate dataset schema #1404
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
base: main
Are you sure you want to change the base?
Using signals schema instead of columns to calculate dataset schema #1404
Conversation
Reviewer's guide (collapsed on small PRs)Reviewer's GuideThis PR refactors how the dataset schema is computed by deriving a flat schema from the unified signals schema (including system signals) rather than reconstructing it from column definitions. It adds a clone_with_sys_signals helper to merge system columns, generates flat_schema in DataChain.save, and propagates flat_schema through query/dataset.save and catalog.create_dataset, replacing the previous inline column-based schema logic. File-Level Changes
Possibly linked issues
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
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.
Deploying datachain-documentation with
|
| Latest commit: |
42f2b0b
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://6dd3bbe1.datachain-documentation.pages.dev |
| Branch Preview URL: | https://ilongin-1403-use-signal-sche.datachain-documentation.pages.dev |
|
@ilongin ping |
WIP
Summary by Sourcery
Use the signals schema to compute and pass both hierarchical and flat dataset schemas across save and dataset creation APIs, eliminating manual column-based schema logic
New Features:
Enhancements: