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

Create full context for virtual asset #93

Open
cmgrote opened this issue Oct 17, 2019 · 1 comment
Open

Create full context for virtual asset #93

cmgrote opened this issue Oct 17, 2019 · 1 comment
Labels
enhancement New feature or request
Milestone
1.7

Comments

@cmgrote
Copy link
Member

cmgrote commented Oct 17, 2019 •
edited
Loading

For each virtual asset, create the "full context" including:

  • RelationalColumn
  • NestedSchemaAttribute
  • RelationalTable
  • AttributeForSchema
  • RelationalDBSchemaType
  • AssetSchemaType
  • DeployedDatabaseSchema
  • DataContentForDataSet
  • Database
  • ConnectionToAsset
  • Connection (generated to a placeholder used for all virtual assets, if necessary)
  • ConnectionConnectorType (generated to a placeholder used for all virtual assets, if necessary)
  • ConnectionEndpoint (generated to a placeholder used for all virtual assets, if necessary)
  • Endpoint (generated to a placeholder used for all virtual assets, if necessary)

Need to decide how best to do this: eg. via Data Platform OMAS, Data Engine OMAS, or elsewhere?
@cmgrote cmgrote self-assigned this Oct 17, 2019
@cmgrote cmgrote added the enhancement New feature or request label Oct 17, 2019
@cmgrote cmgrote mentioned this issue Oct 17, 2019
Closed
@cmgrote cmgrote added this to the 1.5 milestone Dec 5, 2019
@cmgrote cmgrote added the functionality-call To discuss and agree during weekly functionality call(s) label Mar 2, 2020
@cmgrote
Copy link
Member Author

cmgrote commented Mar 3, 2020

Agreed on 03/03 call that we should generate up to Database level (not necessary to go all the way up to Endpoint)

@cmgrote cmgrote removed the functionality-call To discuss and agree during weekly functionality call(s) label Mar 3, 2020
@cmgrote cmgrote modified the milestones: 1.6, 1.7 Apr 2, 2020
@cmgrote cmgrote removed their assignment Jun 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
1.7
Development

No branches or pull requests
1 participant
@cmgrote