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.

Sign up for GitHub

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

Jump to bottom

should we have computed columns for each table? #134

Open
tardunge opened this issue Aug 1, 2023 · 0 comments
Open

should we have computed columns for each table? #134

tardunge opened this issue Aug 1, 2023 · 0 comments
Labels
question Further information is requested

Comments

@tardunge
Copy link
Collaborator

tardunge commented Aug 1, 2023

right now the computed columns are defined on a global scope. If any table has the column specified in its schema definition, it is computed and furnished. We might have a slight advantage when we scope this at a table definition level and avoid un-necessary computations on a multi-table ingestion scenario.
@tardunge tardunge added the question Further information is requested label Aug 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tardunge