Problem
The current io-ingest optional extra pins ingestr>=0.13.61,<0.15. Every version of ingestr in that range hard-pins sqlalchemy-cratedb==0.41.0 or ==0.42.0.dev2, which creates an unsatisfiable conflict any time cratedb-toolkit itself requires a newer sqlalchemy-cratedb. This broke CI and will block every future sqlalchemy-cratedb upgrade.
Beyond the dependency conflict, the <0.15 is effectively EOL.
Why this is important
- cratedb-toolkit pipeline is broken because of this conflict, We should upgrade ingestr to continue the support.
- Dependency simplification. The old io-ingest extra required five packages to make ingestr work with CrateDB.
- it blocks sqlalchemy >2 update in future
License note
ingestr 1.0.x changed its license from MIT/Apache 2.0 to the Functional Source License 1.1. FSL is not an open-source license. it prohibits use for "competing commercial purposes" for two years after each release, after which it automatically converts to Apache 2.0. For current use, the practical exposure looks low.
We can keep track of dropping support or migration to another package for ingestr in other issue. Wdyt? @kneth @florinutz
Problem
The current io-ingest optional extra pins
ingestr>=0.13.61,<0.15. Every version of ingestr in that range hard-pinssqlalchemy-cratedb==0.41.0or==0.42.0.dev2, which creates an unsatisfiable conflict any time cratedb-toolkit itself requires a newer sqlalchemy-cratedb. This broke CI and will block every future sqlalchemy-cratedb upgrade.Beyond the dependency conflict, the
<0.15is effectively EOL.Why this is important
License note
ingestr 1.0.xchanged its license from MIT/Apache 2.0 to the Functional Source License 1.1. FSL is not an open-source license. it prohibits use for "competing commercial purposes" for two years after each release, after which it automatically converts to Apache 2.0. For current use, the practical exposure looks low.We can keep track of dropping support or migration to another package for ingestr in other issue. Wdyt? @kneth @florinutz