Releases: kamu-data/kamu-cli
Releases · kamu-data/kamu-cli
Release v0.219.1
[0.219.1] - 2029-01-18
Fixed
- Reverted unstable AWS API dependencies
Release v0.219.0
[0.219.0] - 2029-01-17
Changed
- Massive crates restructuring around Open Data Fabric code:
src/odf
concentrates large number of related crates now, preparing for future separation in different Git repo- old
opendatafabric
crate becamseodf-metadata
- low-level repository implementations became
odf-storage[-...]
crates - specific storage technologies are gated via features (
lfs
,s3
,http
) DatasetFactory
,Dataset
,DatasetSummary
,DatasetLayout
,BlockRef
,
MetadataChain
and visiting logic now are residents ofodf-dataset
kamu-data-utils
becameodf-data-utils
- multiple utility libraries introduced, shared both via ODF and main Kamu code
(async-utils
,file-utils
,s3-utils
,test-utils
) DatasetRepository
still stays in Kamu core, renamed toDatasetStorageUnit
to better match it's current purpose- import statements pointing at ODF code have been cleaned all over the code base (use
odf
meta-crate only outsidesrc/odf
)
Release v0.218.0
[0.218.0] - 2029-01-17
Changed
- Private Datasets:
- OSO: using user actors / dateset resources that come from the database
- Thus, any access check relies on real entities
- GQL, added
Dataset.visibility()
to get the current visibility value - GQL, added
DatasetMut.setVisibility()
to be able to change the dataset visibility after it has been created - Deletion of previously created (and unused) ReBAC-properties and reindexing
- OSO: updating the schema to use identifiers instead of names
- OSO: added resource storage for access speed
- E2E: Using the correct account in multi-tenant mode
- And also the possibility of set it up
DatasetOwnershipService
: moved to thekamu-dataset
crate area & implemented viaDatasetEntryServiceImpl
- GQL,
DatasetMetadata.currentUpstreamDependencies
: indication if datasets not found/not accessed - GQL,
DatasetMetadata.currentDownstreamDependencies
: exclude datasets that cannot be accessed - E2E: added the ability to create an account using CLI
- OSO: using user actors / dateset resources that come from the database
Release v0.217.3
[0.217.3] - 2025-01-14
Fixed
- Fix crash on resolving dataset by non existing account
- Minor improvements in event sourcing aggregation
Release v0.217.2
[0.217.2] - 2025-01-10
Changed
- Updated to latest
datafusion
andalloy
dependencies - Performance improvements with batch loading of event sourcing aggregates
Release v0.217.1
[0.217.1] - 2025-01-09
Changed
- Extended database config options with next fields:
maxConnections
,maxLifeTimeSecs
andacquireTimeoutSecs
Release v0.217.0
Release v0.217.0 + minor deps
Release v0.216.0
[0.216.0] - 2024-12-30
Changed
- Flight SQL protocol now supports anonymous and bearer token authentication
- The
kamu notebook
command now defaults toDataFusion
engine for speed, but you can switch to Spark with--engine spark
argument - The
kamu notebook
command uses new image based on latest Jupyter and newkamu-client-python
library - The
kamu sql server
command now defaults toDataFusion
engine with interface changed to use--engine datafusion/spark
, removing the--flight-sql
flag - Examples in
examples/flightsql/python
were updated to new auth and showcasingkamu
Python library - Most notebooks in
examples/
directory are usingkamu
Python library withDataFusion
engine, with Spark still in use for GIS extensions
Release v0.215.1
[0.215.1] - 2024-12-30
Fixed
- GraphQL: in a multi-tenant workspace,
datasets.createEmpty
anddatasets.createFromSnapshot
mutations now return dataset aliases prefixed with account name. - Fix DB transaction error in
/verify
REST endpoint (cherry-picked from0.214.1
)
Release v0.214.1
[0.214.1] - 2024-12-28
Fixed
- Transaction error on
/verify
REST endpoint