-
Notifications
You must be signed in to change notification settings - Fork 58
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
feat: open source the event generator gradle plugin #64
Conversation
...b/src/main/java/com/linkedin/metadata/annotations/DefaultGmaEntitiesAnnotationAllowList.java
Outdated
Show resolved
Hide resolved
|
||
## What are "v5" Metadata Events? | ||
|
||
In brief, we've split the monolithic MCE/MAE/FMCE events into smaller events. One event per aspect-entity combination. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
use the order of entity-aspect?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any particular reason why?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
because we break down the event in the order of form? namespace com.linkedin.mxe.corpUser.corpUserInfo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The text here isn't meant to indicate order, just the pairing. If you feel it is important to be consistent we can change it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the work!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This plugin exists internally and I am now open sourcing it.
I've added two commits to this PR to make reviewing easier. The second is new documentation that should be thoroughly reviewed; while the code changes could perhaps be more skimmed over since they already exist internally.
Checklist