Changelog
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
[1.3.2] - 2024-09-20
Added
Targets
mongodb
target. Models will be stored on a dedicated collection with the following target configuration:{
// ...
"target": {
"type": "mongodb",
"url": "mongodb://test:27017/?replicaSet=rs", // 👈 mongodb connection string: the database must be a replica set
"database": "test_database", // 👈 if defined, it will be used as default database to store the models
}
}The record will be stored in a collection named
open-lineage-datasets
.NOTE:
To use MongoDB as a target, the database must be configured as a replica set.
Updated
- Data Catalog Agent bumped to version
0.6.4
[1.3.1] - 2024-07-31
Updated
- Data Catalog Agent bumped to version
0.6.3
Fixed
- bug introduced by previous release which prevented MySQL queries to return records.
[1.3.0] - 2024-07-12
Updated
- Data Catalog Agent bumped to version
0.6.2
- rolling out of support for Oracle
11c
- Crud Service http connection now has an additional parameter,
healthcheck
, which contains the path used to retrieve the version of the service.
Added
settings
field to connection configuration object;options
optional field for oracle odbc configurations: this field defines the tables that will be used for retrieve the metadata. If not specified,user
option will be used as default;
Changed
version
field in theoracle
odbc configuration has been moved outside of theparams
object, so it can be used along with odbc connection string.{example.json}{
"type": "odbc",
"configuration": {
"vendor": "oracle",
"version": "11",
"params": {/** ... */}
}
}
[1.2.0] - 2024-05-07
Added
- Support for
salesforce_objects
- Data Catalog Agent bumped to version
0.5.1
[1.1.0] 2024-02-08
- Add Mia CRUD Service support to the data-catalog agent
[1.0.0] 2024-01-31
- First release