[
https://issues.apache.org/jira/browse/JENA-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13055097#comment-13055097
]
Thorsten Möller commented on JENA-76:
-------------------------------------
Shouldn't this be a feature request (rather than a bug) having the subject "TDB
should implement Iterator.remove()"? What is the reason for not considering
this an option? Is it conceptually related that TDB cannot implement
Iterator.remove()? The solution described above seems to introduce additional
work (search repeatedly as long as something relevant is found versus search
once only).
> 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
