Hi,
I was assuming that the original iterator is "static" with its values and thus,
if you add values while you iterate, you will only be iterating over those
edges you had prior to the iteration.
Unfortunately, it seems the OrientDB has a "dynamic" iterator that can grow
during iteration…
Either OrientDB forces a "static" iteration or perhaps we add a new Feature:
Graph.Features.supportsStaticVertexIteration
Graph.Features.supportsStaticEdgeIteration
Vertex.Features.supportsStaticVertexIteration
Vertex.Features.supportsStaticEdgeIteration
…I'm sorta scared of "yet more Features."
Thoughts?,
Marko.
http://markorodriguez.com
On Nov 27, 2015, at 5:23 AM, Stephen Mallette <[email protected]> wrote:
> I don't remember exactly what we wanted to enforce there - Marko looks like
> you added that one around TinkeGraph, can you comment?
>
> On Thu, Nov 26, 2015 at 2:10 PM, Marvin Froeder <[email protected]> wrote:
>
>> Hey,
>>
>> I was looking the EdgeTest, and it can cause infinite loops...
>>
>>
>> https://github.com/apache/incubator-tinkerpop/commit/4b5d67aed4c69a0383d0e887501a8bba68a0e973#commitcomment-14537644
>>
>> For each edge the test removes, 2 more are added.
>>
>> For OrientDB drive we stream the edges live, from the DB, so this test
>> enter in an infinite loop.
>>
>>
>> Any suggestions how can I circumvent it?
>>
