[ 
https://issues.apache.org/jira/browse/TINKERPOP3-886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15019054#comment-15019054
 ] 

ASF GitHub Bot commented on TINKERPOP3-886:
-------------------------------------------

Github user kushal256 commented on the pull request:

    
https://github.com/apache/incubator-tinkerpop/pull/141#issuecomment-158556607
  
    Awesome!  Apologies for the import with a wildcard, my Intellij did that
    for me, I can clean that up, let me know if there are any additional
    cleanup items, want to ensure everything meets the project's standards.
    
    
    On Fri, Nov 20, 2015 at 1:43 PM, Daniel Kuppitz <[email protected]>
    wrote:
    
    > I've been almost happy with the first version and now that something has
    > been added to the docs:
    >
    > VOTE: +1
    >
    > —
    > Reply to this email directly or view it on GitHub
    > 
<https://github.com/apache/incubator-tinkerpop/pull/141#issuecomment-158532860>
    > .
    >



> Allow any GraphReader/Writer to be persistence engine for TinkerGraph 
> ----------------------------------------------------------------------
>
>                 Key: TINKERPOP3-886
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-886
>             Project: TinkerPop 3
>          Issue Type: Improvement
>          Components: tinkergraph
>    Affects Versions: 3.0.2-incubating
>            Reporter: stephen mallette
>            Assignee: stephen mallette
>            Priority: Trivial
>
> TinkerGraph currently works with gryo, graphml and graphson - all internal 
> formats to TinkerPop.  This could easily be extended to work with any format 
> implementing the appropriate interfaces (i.e. also external third-party 
> formats) by allowing for the `gremlin.tinkergraph.graphFormat` setting for 
> TinkerGraph to be set to the existing three settings, but also allow for it 
> to be the fully qualified class name for a {{Io.Builder<I extends Io>}} 
> interface.  TinkerGraph could then dynamically instantiate this class (which 
> we can expect to have a zero-arg constructor) and use it to load/save data.  
> This might actually also clean up some of the existing code around load/save.



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

Reply via email to