[
https://issues.apache.org/jira/browse/JENA-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13055120#comment-13055120
]
Thorsten Möller commented on JENA-76:
-------------------------------------
I see (seems similar to the notorious view update problem). Still, the approach
is not quite convincing since it creates behavior that one might want/need to
optimize at a later point. If I understand the proposal correctly, then it is
necessary to temporarily keep the blocks in main memory (i.e., it is not a
streaming like approach). Hence, under main memory constraints one might want
to keep the blocks rather small, ergo more repetitions. Conversely, under
performance constraints one might want to make the blocks large in order to
reduce repetitions.
> Resourceutils.renameResource uses Iterator.remove() to make changes - not all
> iterators support .remove.
> --------------------------------------------------------------------------------------------------------
>
> Key: JENA-76
> URL: https://issues.apache.org/jira/browse/JENA-76
> Project: Jena
> Issue Type: Bug
> Components: Jena
> Reporter: Andy Seaborne
>
> Resourceutils.renameResource uses Iterator.remove() to make changes. TDB does
> not support Iterator.remove
> Instead, renameResource could grab a block (say, 1000) items, rename them and
> loop on blocks of 1000. This way, the iterator is terminated before updates
> are done. The nature of the rename operation means that the find iterator is
> executed until no resources are found so this batching mechanism does not
> need to need to track what has and has not been found - just repeat until
> less than 1000 items found.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
