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

Wolfgang Fahl commented on TINKERPOP-2294:
------------------------------------------

The separation of concerns GLV - Graph is something I'd appreciate if there was 
some kind of API to make sure you can influnence the base graph. This involves:
 * choosing the Provider
 * choosing the underlying graph

A "simple" API for this would be just great. My use case is that I'd like to 
load two graphs using Python and to a diff on theses. I might want to then 
persist the graphs using some kind of provider. Currently the GLV approach 
seems to make this all very very unintuitive. Especially since small details 
like the url in the remoteConnection play a critiical role in whether you end 
up in a non-working situation with fully unreleated errorc codes (tornado 
-timeout 599 ...). The api should be there to give a clear exception handling 
if the provider e.g. is not configured correctly.

> Gremlin-Python usability and tutorial
> -------------------------------------
>
>                 Key: TINKERPOP-2294
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2294
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: python
>    Affects Versions: 3.4.3
>            Reporter: Wolfgang Fahl
>            Priority: Major
>
> The Gremlin-Python environment is not useable "out of the box" at this time 
> and hard to configure. It needs a specially configured gremlin-server for 
> each use case.
> The handling of the server configuration and startup could be simplified if 
> it would be done by some kind of API instead of the YAML file. Especially it 
> is important to make graph io available to be able to create python specific 
> tutorials that are based on typical databases.  The handling of typical 
> backend database configurations should be simplified.
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to