Timebased Fragmentation[DEPRECATED] with SNAPSHOT 2.0.0 #890

xdxxxdx · 2023-08-24T12:05:09Z

xdxxxdx
Aug 24, 2023
Maintainer

I am running the E2E test 004 https://github.com/Informatievlaanderen/VSDS-LDES-E2E-testing/tree/main/tests/004.server-time-fragment-ldes
With Sprint 33 snapshot:

With the configurations
as: https://github.com/Informatievlaanderen/VSDS-LDES-E2E-testing/blob/main/tests/004.server-time-fragment-ldes/config/mobility-hindrances.ttl for collections:

@prefix ldes:    <https://w3id.org/ldes#> .
@prefix tree:    <https://w3id.org/tree#>.
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix prov:    <http://www.w3.org/ns/prov#> .
@prefix sh:      <http://www.w3.org/ns/shacl#> .

</mobility-hindrances> a ldes:EventStream ;
	tree:shape [ a sh:NodeShape ; sh:targetClass <https://data.vlaanderen.be/ns/mobiliteit#Mobiliteitshinder> ] ;
	ldes:timestampPath prov:generatedAtTime ;
	ldes:versionOfPath dcterms:isVersionOf .

as: https://github.com/Informatievlaanderen/VSDS-LDES-E2E-testing/blob/main/tests/004.server-time-fragment-ldes/config/mobility-hindrances.by-time.ttl for view

@prefix tree: <https://w3id.org/tree#>.
@prefix xsd:    <http://www.w3.org/2001/XMLSchema#> .

</mobility-hindrances/by-time> a tree:Node ; 
  tree:viewDescription [ a tree:ViewDescription ;
    tree:fragmentationStrategy ([
		a tree:TimebasedFragmentation ;
		tree:memberLimit "300"^^xsd:integer ;
		tree:fragmentationPath <http://www.w3.org/ns/prov#generatedAtTime> ;
	]) ;
] .

I notice that

the previous time-based relation is abandoned. e.g. tree:LessThanRelation etc..
generic relation tree:Relation is employed.
we have a tree structure like:

I am wondering

tree:memberLimit "300"^^xsd:integer ; is not taken into account when doing the pagination. Then how to set it?
What is the exact useful meaning the layer between the pagination and the view URL?
In current case: http://localhost:8080/mobility-hindrances/by-time?generatedAtTime=2023-08-24T10:55:03.490Z .

from my perspective, this layer is not really extensible with the member ingesting or configuration. This URL will be fixed and there is only this one.
If this layer is removed, I don't see any difference with this deprecated time-based fragmentation and pagination.

Btw as we have the new implemented Hierarchical Timebased Fragmentation, it might be useful adapting the E2E test for it.