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
DM-32229: Update faro TExTasks to take parquet table as input #114
Conversation
…able column names
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.
Looks good, I left a few very minor comments to address.
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.
Thanks for all the work on this PR, including the validation tests / comparisons between the FITS and parquet input versions. Suggest to move forward to merge this ticket so that we have a concrete example of a measurement task that uses the parquet table inputs while we continue to develop the strategy to implement selectors and specify columns to load from the parquet tables across various metrics and analysis contexts.
second jenkins job after requested pr changes -> https://ci.lsst.codes/blue/organizations/jenkins/stack-os-matrix/detail/stack-os-matrix/35623/pipeline |
Jenkins job -> https://ci.lsst.codes/blue/organizations/jenkins/stack-os-matrix/detail/stack-os-matrix/35491/pipeline
This also resulted in a few minor changes to tex.py and some of its dependencies, see notes in JIRA ticket (https://jira.lsstcorp.org/browse/DM-32229)