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.

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

Allow using key columns as input to derivations #921

Open
wants to merge 11 commits into
base: main
Choose a base branch
from

Conversation

xiaohui-sun
Copy link
Collaborator

@xiaohui-sun xiaohui-sun commented Feb 10, 2025

Summary

Add support for using key columns as input to derivations.

Why / Goal

Test Plan

  • Added Unit Tests
  • Covered by existing CI
  • Integration tested

Checklist

  • Documentation update

Reviewers

@hzding621
@yuli-han

@xiaohui-sun xiaohui-sun changed the title [WIP]Allow using key columns as input to derivations Allow using key columns as input to derivations Feb 12, 2025
@xiaohui-sun xiaohui-sun marked this pull request as ready for review February 12, 2025 05:43
Copy link
Collaborator

@yuli-han yuli-han left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you try to test the fetcher behavior on a gateway? Usually the step is:

  1. update an existing testing join derivation with derivation on key in the zipline_test folder
  2. run metadata-upload to upload the new join schema to k-v store metadata store
  3. upload the local jar to a remote gateway with the new change.
  4. run fetcher cli to validate the change
    This is the procedure I am running when changing the fetcher, cc @hzding621 @pengyu-hou could you pls share if you know any simpler way to test or if there are existing doc for the testing procedure? Also pls lemme know if you need the command to run the steps.

@hzding621
Copy link
Collaborator

+1 to fetchercli testing as to what @yuli-han said

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants