* feat(dashboard): Dashboard models update
* Keep chartId/dashboardId fields in the URN definitions and add fields for chartURL/dashboardURL into info aspects
* Rebase and address some comments
* feat(field-level-lineage): adding models for field level lineage
adding models for field level lineage. Introduce DatasetFieldUrn as a unique identifier for dataset field
* added intial version of Business Glossary RFC
* slight updates to Business Glossary RFC
* slight updates to Business Glossary RFC
* updated the sample business glossary table
* updated the sample business glossary content
* updated the sample business glossary content
* Update README.md
updated the attribute of Business Term
* incorporated feedback around DatasetFieldUrn and relationships
* Update README.md
updated the alternatives section
* Update README.md
incorporated the feedback provided by Nagarjuna
* Update README.md
Incorporated feedback
a) removal of redundant uri attribute from BusinessTerm definition
b) rolled back changes to SchemaField (as per feedback) and will continue to use fieldPath is unique identified for a field in a given Dataset
* Incrporated the review comments and Discussion Feedck
* Fix teh RFC link
* Fix teh RFC link
* refactor(gms): use BaseLocalDAO as the interface in factories & rest.li resources
Fixes#1974
* Revert yarn.lock change
Co-authored-by: Mars Lan <mars@trayminder.com>
* refactor search index builder to store urn parts efficiently (#1937)
Co-authored-by: Jyoti Wadhwani <jywadhwa@linkedin.com>
* set urn for all documents
* rebase, fix merge conflicts and modify tests
Co-authored-by: Jyoti Wadhwani <jywadhwa@linkedin.com>
Move code to linkedin/datahub-gma.
"GMA" (Generalized Metadata Architecture) is the backend of DataHub, and has been moved to its own repository.
This deletes the code that was moved and uses jars that GMA publishes to bintray to load it.
Note that not all of GMA was moved, but most of it. We may still move more things to the other repository in the future.
* fix(login): Fix login error when corp user editable information is not present
Check if the aspects are present before extracting the values
* More stronger checks for presence of aspects in model
* feat(Azkaban entities): RFC for Azkaban Flows and Jobs
* Update to pivot to data job and flow as an entity and address comments
* Update urn definitions and address comments
* address minor comments
