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

Data Stage connector capability to process virtual assets #599

Open
lpalashevski opened this issue Sep 16, 2021 · 0 comments
Open

Data Stage connector capability to process virtual assets #599

lpalashevski opened this issue Sep 16, 2021 · 0 comments

Comments

@lpalashevski
Copy link
Contributor

Following requirements were discussed on the virtual Egeria workshop:

  • If the option "includeVirtualAssets" is set to true, the connector will send the virtual assets information through (via new DataEngine api calls);
  • In case of mode=JOB_LEVEL, it includes: database schema (deployed database schema as asset in egeria), relational tables;
  • Data files are still under discussion because of the way they are used in IGC (file patterns and not file instances). We need to decide what will be the correct type used in Egeria (DataFolder?);
  • Connection level metadata is not useful and we are not going to create Egeria representation;
  • Data Engine can then do lineage mappings using the assets created from virtual IGC assets.
@lpalashevski lpalashevski changed the title DataStage connector capability to process virtual assets Data Stage connector capability to process virtual assets Sep 16, 2021
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

No branches or pull requests

1 participant