Kamu

Changed
- Updates to support open-data-fabric/open-data-fabric63
- Metadata chain will complain about `AddData` or `ExecuteTransform` events if there is no `SetDataSchema` event
- Push ingest no longer piggy-backs on `SetPollingSource` - it requires `AddPushSource` event to be present
- `DatasetWriter` will now validate that schema of the new data block matches the schema in `SetDataSchema` to prevent schema drift
Added
- Name of the push source can optionally be specified in CLI command and REST API

Added
- New dataset permission for UI: `canSchedule`
- Added `kamu ui` feature flag to control availability of datasets scheduling

Added
- New `kamu ingest` command allows you to push data into a root dataset, examples:
- `kamu ingest my.dataset data-2023-*.json` - to push from files
- `echo '{"city": "Vancouver", "population": 675218}' | kamu ingest cities --stdin`
- New `/{dataset}/ingest` REST endpoint also allows you to push data via API, example:
- Run API server and get JWT token: `kamu ui --http-port 8080 --get-token`
- Push data: `echo '[{...}]' | curl -v -X POST http://localhost:8080/freezer/ingest -H 'Authorization: Bearer <token>'`
- The `kamu ui` command now supports `--get-token` flag to print out the access token upon server start that you can use to experiment with API
Changed
- Upgraded to `arrow v48`, `datafusion v33`, and latest AWS SDK

Fixed
- Jupyter image now correctly parses dataset aliases in multi-tenant repositories

Changed
- FlightSQL interface tweaks to simplify integration into `api-server`

Fixed
- `kamu ui` should run without specifying any auth secrets