vtermanis commented on PR #1344:
URL: https://github.com/apache/jena/pull/1344#issuecomment-1153617081
(sorry, one more Q @LorenzBuehmann )
> we have to live with the Quadtree for read-write Datasets.
What would it mean for persistence? (From my understanding the current
`STRtree` index is serialised to disk in full.)
For the case where a write-heavy dataset is only used sparingly for
GeoSPARQL queries, is it still useful to offer the "no index" option also, i.e.:
1. `STRtree` index pre-generated either to file or into memory (current mode)
2. `QuadTree` index updated during writes (in memory and/or disk?)
1. Can update geometries in data & continue to perform spatial queries
2. If have existing large dataset, have to pre-generate initial index on
startup
3. Spatial index disabled
1. No write & startup perf impact (if (2) persisted)
2. GeoSPARQL queries slow(er), choose option 1 or 2 if this matters
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
