fix dataSpace Analytics with Association #1003
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MauricioUyaguari
requested review from
pierredebelen,
davidharte-gs,
aormerod-gs,
gs-ssh16,
epsstan,
kevin-m-knight-gs,
rafaelbey,
aziemchawdhary-gs and
elopezcastro
as code owners
akphi
approved these changes
Oct 3, 2022
MauricioUyaguari
force-pushed
the
dsMinor
branch
from
c61cf53
to
b62278d
Compare
pierredebelen
approved these changes
Oct 4, 2022
hausea
pushed a commit
to hausea/legend-engine
that referenced
this pull request
Feb 8, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
bug fix
What does this PR do / why is it needed ?
in conjunction with fetching dataSpace Analytics result from depot. There are some issues with the PMCD generators. Most were fix with #966
but association was missed
Which issue(s) this PR fixes:
Fixes #
Other notes for reviewers:
Does this PR introduce a user-facing change?