[
https://issues.apache.org/jira/browse/TINKERPOP-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16932777#comment-16932777
]
stephen mallette commented on TINKERPOP-2294:
---------------------------------------------
> Why is this all so horribly complicated. I find this totally frustrating
> since the need behind all this is simple and the solution is way complicated.
There's not much point into my going into the history of the evolution of
TinkerPop over the last 5 years to get us where we are now. Choices were made,
dark deals were struck, epiphanies were plenty and now we set an adoring and
simultaneously loathing gaze upon the granite city of The TinkerPop.
> See
> https://stackoverflow.com/questions/53708193/how-do-i-upload-tinkergraph-into-python-gremlin
> for what people expect.
Well, that implies building TinkerGraph in python and javascript and .NET and
whatever other languages we go to support. It perhaps further implies the
notion of a local graph system which would involve building a native TinkerPop
graph processing engine in each host language. That's not what Gremlin Language
Variants (GLVs) are meant to be about. They simply expose the Gremlin language
in a way that allows you to traverse a remote graph in your native programming
language. In this way you avoid embedding Gremlin strings in your
python/javascript/etc code. That's it. That's why we've recently gotten rid of
the use of {{Graph}} all together in the language variants and simply started
the construction of "g" with {{traversal()}} so that it was more clear that
GLVs are about remote Gremlin execution.
Are GLVs lightweight? yes. Do GLVs come with limitations? you bet, they are not
a 1:1 mapping to the Gremlin Java. They do however provide a layer of
convenience which some people seem to appreciate.
to be honest, i'm not sure where to go from here on this one. part of me thinks
that we might fold some of these ideas under TINKERPOP-2063 which would have to
introduce TinkerGraph (or something like it) into GLVs. Once we came to grips
with that then it could open the door for some other major steps to be taken
perhaps.
> 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)
