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

Flows: physical to logical datatype rippler should use a dedicated provenance #7111

Open
davidwatkins73 opened this issue Jul 12, 2024 · 0 comments
Open

Flows: physical to logical datatype rippler should use a dedicated provenance #7111

davidwatkins73 opened this issue Jul 12, 2024 · 0 comments
Milestone
next : 1.66

Comments

@davidwatkins73
Copy link
Member

Description

Currently it is hard to tell at a glance if the data type on a logical was rippled up from a physical. This is because the PhysicalSpecDecoratorDao::rippleDataTypesToLogicalFlows method has the hard coded values waltz for provenance and admin for the user id.

Suggest we change the to be more explicit (data-type-rippler / automated-job) ?

Resourcing

We intend to contribute this feature
@davidwatkins73 davidwatkins73 added this to the todo : 1.61.1 milestone Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
next : 1.66
Development

No branches or pull requests
1 participant
@davidwatkins73