[ 
https://issues.apache.org/jira/browse/TINKERPOP-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stephen mallette updated TINKERPOP-1124:
----------------------------------------
    Fix Version/s:     (was: 3.2.4)

I'm not sure that we would do this, but it definitely wouldn't happen on 3.2.x 
at this point - [~velobr] if you want to see this change you would probably 
need to create consensus for it on the dev list.

> Make tinkerpop interfaces expandable
> ------------------------------------
>
>                 Key: TINKERPOP-1124
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1124
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: structure
>    Affects Versions: 3.1.1-incubating
>            Reporter: Marvin Froeder
>
> Make the return methods generic so we can specialize them.
> For instance, instead of
> {code:java}
> public interface Graph {
>  public Iterator<Vertex> vertices(final Object... vertexIds);
> }
> {code}
> move to
> {code:java}
> public interface Graph<V extends Vertex> {
>  public Iterator<V> vertices(final Object... vertexIds);
> }
> {code}
> That way, orientdb-gremlin (or any other drivers) can expose custom 
> operations on graphs, vertex or edges and even enforce types for things like 
> Element.id() and many other creative stuff.
> That is the way querydsl (http://www.querydsl.com/) found to have a 
> consistent api that can be extended and used in so many different modules.
> This would allow orient-gremlin expose orient specific operations w/o having 
> to expose the implementation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to