Skip to content

v3.1.0 alpha

Pre-release
Pre-release
Compare
Choose a tag to compare
@Yalz Yalz released this 19 Jun 08:51
· 114 commits to main since this release
v3.1.0-alpha
f839814
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

What's Changed

Liquibase introduction

From the 3.1.0 release on, the LDES server contains a migration path between each release.
No extra configuration is needed, all needed tables and migrations will be done on the fly.

Fragmentation rework (batching)

The fragmentation got a big rework to focus towards a more performant LDES Server.
The 2 processes (bucketisation and pagination) are now split up:

  • Bucketisation: Based on the configured fragmentation strategy and a given LDES member, the member can be assinged to a number of buckets. This will be reflected in the relations in the LDES fragments.
  • Pagination: For each of the assigned buckets, the members will be paginated. This happens based on the configured memberCount per page.

These processes will now work with a time interval to process more members at the same time.

Geospatial fragmentation update

Previously, there was an issue in the geospatial fragmentation where only the tiles that contains the points of a shape were taken.
In the below example, A3 and D3 were taken as tiles of a geospatial fragmentation, but the others were ignored.
From now on, also tiles B3, C2 and C3 are taken.
image

Closing of an LDES

If, as a dataowner, you know no more data will be ingested in an Event Stream, there is now the ability to close the stream (turns the latest page immutable).
This gives the advantage that the LDES Client can stop following the LDES without needlessly polling for updates that will never come.
To close an LDES, please visit the swagger endpoint.

Change notes

Full Changelog: v3.0.0-alpha...v3.1.0-alpha

Contributors

Yalz, ferre-vaes, and 2 other contributors
Assets 2
Loading