You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are releasing 1.0.0 version of dlt. In the last 2 years we've got quite stable (in term of our API, internal migrations and major bugs being rare) and feature complete. There so many production deployments that even with our obsessive approach to testing (you can always write more test cases!) we are pretty confident dlt is now "stable" and ready for production.
What is coming if full release
We move sql databasefilesystem/buckets and rest api sources to the core library to make them easily available, stabilize the APIs and run tons of additional tests.
Our documentation gets a big update: additional tutorials on syncing the databases, working with buckets and file readers and using rest api toolkit to declare pipelines loading data from REST APIs
On top of that we will plan a few quick follow-up features:
To use iceberg table format on Athena destination, set the table_format to iceberg on all your resources instead of force_iceberg flag in destination configuration. This flag is deprecated but will be still observed for backward compatibility.
A few column hints (foregin_key and index) that were not documented and have no real use, will be removed.
if primary key was used in nested table, linking was not created in relational.py. now linking is skipped when nested row is fitted into table that is not nested (does not have a parent). a rare case of someone that does not want dlt linking
removes generate_dlt_id from json relational normalizer config
deprecates skip_complex_types in dlt Pydantic config, asks to use skip_nested_types
dlt schema engine migration
If you run this version against existing dataset in a destination, schema in _dlt_version will be migrated to engine v10. Same applies to local pipeline working dir. You can restore the old schema by deleting the migrated version from the version table.
New Versioning Scheme
We'll follow classical major.minor.patch scheme. Where
major means breaking changes and removed deprecations
minor new features, sometimes automatic migrations
patch bug fixes
Version rollout plan
0.5.x will be still supported: docs will be available and major bugs fixed
We plan an alpha release with sources merged in the core and docs updates early next week.
We plan 1.0.0 release in the second / third week of September
Each next week we'll release one of follow-up features
This pre-release brings sql, filesystem and rest_api sources to the core and introduces 95% of the breaking changes and the deprecations. New documentation is not yet available. ⚠️ do not deploy in production ⚠️ will migrate existing schemas - try on fresh datasets
try
To use iceberg table format on Athena destination, set the table_format to iceberg on all your resources instead of force_iceberg flag in destination configuration. This flag is deprecated but will be still observed for backward compatibility.
Will migrate schemas to engine v. 10. this is irreversible
Internal or obscure features:
A few column hints (foregin_key and index) that were not documented and have no real use, will be removed.
if primary key was used in nested table, linking was not created in relational.py. now linking is skipped when nested row is fitted into table that is not nested (does not have a parent). a rare case of someone that does not want dlt linking
removes generate_dlt_id from json relational normalizer config
deprecates skip_complex_types in dlt Pydantic config, asks to use skip_nested_types
Why
1.0
?We are releasing
1.0.0
version ofdlt
. In the last 2 years we've got quite stable (in term of our API, internal migrations and major bugs being rare) and feature complete. There so many production deployments that even with our obsessive approach to testing (you can always write more test cases!) we are pretty confidentdlt
is now "stable" and ready for production.What is coming if full release
On top of that we will plan a few quick follow-up features:
Deprecations and Breaking Changes
iceberg
table format on Athena destination, set thetable_format
toiceberg
on all your resources instead offorce_iceberg
flag in destination configuration. This flag is deprecated but will be still observed for backward compatibility.complex
type is deprecated and superseded byjson
Rename "complex" data type to "json" #1673Internal or obscure changes:
foregin_key
andindex
) that were not documented and have no real use, will be removed.dlt
linkingskip_complex_types
indlt
Pydantic config, asks to useskip_nested_types
dlt pipeline -v <pipeline> trace
source password not redacted #1687dlt schema engine migration
If you run this version against existing dataset in a destination, schema in
_dlt_version
will be migrated to engine v10. Same applies to local pipeline working dir. You can restore the old schema by deleting the migrated version from the version table.New Versioning Scheme
We'll follow classical
major.minor.patch
scheme. Wheremajor
means breaking changes and removed deprecationsminor
new features, sometimes automatic migrationspatch
bug fixesVersion rollout plan
0.5.x
will be still supported: docs will be available and major bugs fixed1.0.0
release in the second / third week of September0.9.9a1 pre-release available
This pre-release brings sql, filesystem and rest_api sources to the core and introduces 95% of the breaking changes and the deprecations. New documentation is not yet available.⚠️ do not deploy in production ⚠️ will migrate existing schemas - try on fresh datasets
try
or
to start a new project
breaking changes and warnings
Deprecations and Breaking Changes
iceberg
table format on Athena destination, set thetable_format
toiceberg
on all your resources instead offorce_iceberg
flag in destination configuration. This flag is deprecated but will be still observed for backward compatibility.Internal or obscure features:
foregin_key
andindex
) that were not documented and have no real use, will be removed.dlt
linkingskip_complex_types
indlt
Pydantic config, asks to useskip_nested_types
run
method, those will be evaluated in a single ad-hoc source. previously each resource was evaluated separately (serialized). creates a single source in extract for all resource instances passed as list #1535Other features
cursor_path
missing or None value by @willi-mueller in Fix/1571 Incremental: Optionally load or ignore records with cursor_path missing or None value #1576The text was updated successfully, but these errors were encountered: