dwcc v2.11 Improved the Dremio collector’s handling of data sources nested within multiple layers of folders, and fixed a minor issue with the Dremio collector’s harvesting of lineage metadata from the Dremio graph API.
dwcc v2.10 Added a collector for Domo and JDBC database collectors can now catalog all schemas in the database at once (default remains to catalog only user's default schema).
dwcc v2.9 Added Tableau Server collector and extended the OpenAPI collector to include a few additional schema property metadata properties.
dwcc v2.8 Added Infor ION data lake collector Optimized collection of JDBC metadata (performance improvement).
dwcc v2.7 Added a collector for PowerBI.
dwcc v2.6 Added the Manta collector.
dwcc v2.5 Upgraded Java runtime.
dwcc v2.4 Extended handling of OpenAPI collector parameters and responses.
dwcc v2.3 Added support for OpenAPI (fka Swagger) collector.
dwcc v2.2 A refactoring release.
dwcc v2.1 Fixed an issue with the Denodo cataloger jdbc url port.
With dwcc v2.0 we now use v2 URIs as the official locator IDs for metadata resources. This is a breaking change (for structural, intentional reasons) which is not backwards compatible with v1 URIs. For more information see the article on dwcc v2.X.
dwcc v 1.20 addresses some memory issues and open-cursor leaks.
With dwcc v.1.19 we write statements to the catalog graph indicating that the catalog was generated by dwcc (with a version). We also added the ability to write database schema objects to the catalog graph.
As of dwcc v1.18, you can specify alternate organization permissions and upload locations when performing an automatic upload of the metadata.
dwcc v.1.16 and dwcc v.1.17 address issues with the SQL Server cataloger.
In dwcc v.1.15 we add Dremio support with optional Catalog API lineage fetching.
As of dwcc v1.14, you can change the amount of memory that gets allocated to a DWCC docker process. See our article on allocating additional memory to Docker for more information.
In dwcc v.1.13 we add support for Microsoft SQL Server, and we enable JVM to use available memory in the container (useful for creating large catalogs). Additionnally we Improve data type recognition in AWS Glue cataloger.
As of dwcc v1.12 we can support not only Glue ETL jobs, but also Glue Data Catalog tables and columns.
With dwcc v.1.11 you can:
Upload generated catalogs via the --upload / -U command-line parameters
Upload the dwcc log when uploading generated catalogs with --upload
Fetch an organization's current catalog with the fetch-catalog command
In dwcc v1.10 we added support for AWS Glue and AWS Athena including cataloging ETL jobs associated with an AWS account. There is no need to mount in a jdbc drivers directory as the Glue cataloger uses the Glue API, not JDBC.
dwc v.1.9 is a bug cleanup release.
It is now possible with dwccv.1.8 to use jdbc drivers on classpath as well as those found in user-specified JDBC Driver Directory (drivers in directory have higher precendence than classpath drivers).
dwcc v.1.7 is a bug-fix release
dwcc v.1.6 adds the support for arbitrary jdbc data sources and the ability to build one-off docker images for testing, demos, etc.,
With dwcc v.1.5 we add support for Oracle.
In dwccv.1.4 we add support for Google BigQuery.
dwcc v.1.3 brings much new functionality including:
Support for Denodo and Snowflake
Compatibility of JDBC catalogs with tables imported through data.world integrations
Ability to differentiate source information for databases cataloged from localhost
Cataloging of
REMARKSfields into dct:descriptio
With dwcc v.1.2 we support Redshift databases.
dwcc v.1.1 contains documentation clarification and expansion for the documents to streamline tags on customer docker hosts.
The initial release of dwcc v.1.0 provides support for metadata catalog extraction for DB2, Hive, MySQL, Postgres.