An allegedly Serializable object with non-transient, non-serializable data members could cause program crashes. Method toURL() of URL class is depreceted.
These tests verify that, given an index settings and mappings, data can be written to the index, and read from it with a query_all query. These are very simple sanity tests.
We can, and should, write more complex tests that specific to each index in the future.
The environment was not set correctly, so it could not fire kafka events. It (mce-cli) always worked when running outside of docker.
I also added a dev ingestion docker image / script which may be much faster if you've already built locally.
Tested:
1. Cleaned docker volumes and started datahub. Verified it is empty.
2. Built with gradle.
3. Ran ./docker/ingestion/ingestion-dev.sh. Verified data shows in DataHub.
4. Ran step 1 again.
5. Ran ./docker/ingestion/ingestion.sh. Verified data shows in DataHub.
Add DataFlow and DataJob urn and aspect models.
The aspects include metadata associated with Data processing flow and job entities,
associated inputs and outputs of a job.
* Init new and improved in repo documentation for open source and github
{COMMIT-SYNC:dca335ff397c3e9c1283d845cef56fdb42f7853b}
* [META-13251] Initial implementation for button to integrate with wintermute
{COMMIT-SYNC:491b2bf5bc91137a2919370e81936033be15b13a}
* Quickfix for UMP Datasets not showing the correct owner link
{COMMIT-SYNC:26eb64cca78f96ed383994b7e67dd4fc8a99d985}
* Updates history of datahub documentation
{COMMIT-SYNC:306b2c72f3a81e699c8b414a8aaf4dcbfdf1ed31}
Co-authored-by: Ignacio Bona <ibonapiedrabuena@linkedin.com>
Involves fixing some types. Bright side is that ModelValidation actually checks aspects now (it did not before because aspects are not records but unions!).
* 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
