This change came back in March. Looking back at the original ticket: https://issues.apache.org/jira/browse/TINKERPOP3-603
and mailing list discussion: http://bit.ly/1F9pCBT It doesn't appear that the choice was made within any specific technical reason to do it one way or another. I guess my question would be why does titan have trouble with this? Titan is already iterating the arguments to convert to ids testing arguments classes as it goes. Seems like there is just an extra step required to throw an exception if that argument list isn't uniform. Unless someone feels really strongly about it, I'd prefer not to change the rules around this for GA because it touches two areas I'd like to see stabilizing: gremlin-test and tinkergraph. We can always open an issue and change the semantics later, especially since this is a feature that expands capability rather than limit it. On Fri, May 8, 2015 at 3:31 AM, Matthias Broecheler <[email protected]> wrote: > Hi guys, > > TP3 recently started to impose the requirement that graph.vertices() and > graph.edges() should not accept mixed argument lists. > > That's causing trouble for Titan because it converts all arguments to ids > right away before retrieving elements by id. > Why does this need to be enforced? > > Best, > Matthias >
