[GitHub] [jena] sszuev commented on issue #1992: [question] unexpected ConcurrentModificationException while working with GraphMem

["sszuev (via GitHub)" <gi...@apache.org>]

sszuev commented on issue #1992:
URL: https://github.com/apache/jena/issues/1992#issuecomment-1681941522

   Sure, that's standard for non-concurrent collection. No doubt. 
   But thank you for detailed explanation.
   
   I know about isolation and `close`, but thank you anyway.
   
   But I think user may not know that GraphMem behaves just like JDK.
   Also, it is strange that behavior differs in these two scenarios. 
   
   It would be nice to have some words in javadoc that states that inappropriate `find` use MAY lead to `ConcurrentModificationException` (or may not).
   


-- 
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: issues-unsubscribe@jena.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@jena.apache.org
For additional commands, e-mail: issues-help@jena.apache.org