0.8.2

Deprecation warning ⚠️

Two methods have been deprecated and will be removed in a future release.

• train_transforms_models is deprecated in favor of train_transforms
• train is deprecated in favor of train_synthetics

More on these below.

New features 🚀

JSON support

Gretel Relational can now handle columns with nested JSON. No changes to existing code are required. Depending on shape, nested JSON may lead to additional models being trained under the hood.

Single transforms config for all tables

The new train_transforms method (replacing the now-deprecated train_transforms_models) accepts a single Transforms model config and applies it to all tables. The set of tables being transformed can be controlled via the optional only (inclusive) and ignore (exclusive) parameters.

Tables can be excluded from synthetics

The new train_synthetics method (replacing the now-deprecated train) supports omitting tables from synthetics training. This is useful if you have a table with static reference data that should never be synthesized. As above, the scope of tables is controlled by the optional only and ignore parameters.

Optional schema parameter for Connector

The Connector#extract method takes an optional schema parameter that gets forwarded to SQLAlchemy and Pandas. Note: this parameter is dialect-specific and not supported by all databases.

---

All PRs

• Support for JSON by @mikeknep in #107
• Single transforms config by @mikeknep in #109
• Kill off all the old style types in Relational code by @mikeknep in #110
• Reduce unnecessary JSON parsing by @mikeknep in #112
• Preserve tables before training by @mikeknep in #111
• Fix bug related to empty normalized tables by @mikeknep in #113
• Add optional schema param to connectors by @mikeknep in #116
• Adjust JSON log locations by @mikeknep in #115
• Notebook update by @mikeknep in #114

Full Changelog: v0.8.1...v0.8.2