afs commented on issue #2076:
URL: https://github.com/apache/jena/issues/2076#issuecomment-1794325269
> This test below fails with Jena 4.9.0 and 4.10.0 (and probably earlier
versions as well)
This could be quite sensitive to the environment (e.g. version of Java JDK)
- would it be possible to run this in some earlier versions? `GraphMem` did
change (clean up) in 4.9.0 although I don't think any behaviour will have
changed.
Does it need to involve the async parser or does
`RDFParser.source("").parse(graph)` also exhibit the problem?
> Also, GraphMem is no longer the instance returned by
GraphFactory.createDefaultGraph().
Correct - in Jena 5.0.0, there is a completely new in-memory graph
implementation, `GraphMem2` which is also available in Jena4.9.0. It is a
term-equality graph.
> Furthermore, the default graph's iterator in Jena 5.0.0 no longer supports
remove() - so I wonder whether use of remove() on a Graph's iterator is
generally considered discouraged.
Not all implementations can provide `remove()` - either it is fundamentally
incompatible with an implementation or a lot for work, including some amount of
slow down, for little use.
And of course, the Java world is moving to towards streams and flows.
We're moving to common semantics across different graph/datasets - we won't
ever complete get there, sometimes the differences are for positive reasons.
Term-equality and no support for iterator.remove is part of that.
Feedback on the wider issues welcome - ideally on dev@jena.
--
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]
