github dlt-hub/dlt 0.5.1

latest releases: 1.3.0, 1.2.0, 1.1.0...
4 months ago

This is a major release (0.4 -> 0.5) in our versioning scheme so please review the breaking changes below. Most of them are relevant only for platform builders that use dlt internals. Some of the long-deprecated components were removed as well

Breaking Changes

Breaking Changes (internals)

  • if dlt.source or dlt.resource decorated function is passed a None in a default argument during a function call, it will be handled exactly like in regular Python function call. Previously such None would request argument injection from configuration. Please read more here: (#1430)
  • dlt.config.value and dlt.secrets.value were evaluating to None at runtime. Now they will evaluate to a sentinel value. All the existing code should be backward compatible. (#1430)
  • full_refresh flag of dlt.pipeline will be deprecated and replaced with dev_mode. (#1063) and (https://dlthub.com/devel/general-usage/pipeline#do-experiments-with-dev-mode)
  • the default resource extraction sequence has changed to round_robin from fifo as a default setting. You can switch back to the previous behavior and learn more about what this means here: (https://dlthub.com/docs/reference/performance#resources-extraction-fifo-vs-round-robin)
  • if you create an instance of a SPEC (ie. SnowflakeCredentials) it will not be marked as resolved even if all required fields are provided. previously some were resolving and some were not. #1489
  • parse_native_representation never marks config as resolved. previously some were resolving and some were not. #1489

Core Library

Docs

Verified Sources

We worked intensively on rest_api and sql_database:

New Contributors

Full Changelog: 0.4.12...0.5.1

Don't miss a new dlt release

NewReleases is sending notifications on new releases.