f the context ClassLoader."
He goes on to show this working in action. Hope this helps somewhat.
> Serialising lambdas for RemoteGraph
> ---
>
> Key: TINKERPOP-1230
> URL: https://issues.apache.org/jira/browse/TIN
f the context ClassLoader."
He goes on to show this working in action. Hope this helps somewhat.
> Serialising lambdas for RemoteGraph
> ---
>
> Key: TINKERPOP-1230
> URL: https://issues.apache.org/jira/browse/TIN
e code to and that will be used
when we deserialize the Closure. Now we can add this [GroovyClosureClassLoader]
to our derserialize method and make our DefaultSerializer use this ClassLoader
instead of the context ClassLoader."
He goes on to show this working in action. Hope this helps som
t I'd like to understand. If other peeps worked on this it would be good to
hear what they found out.
> Serialising lambdas for RemoteGraph
> ---
>
> Key: TINKERPOP-1230
> URL: https://issues.apache.org/jira
this in the past. The problem was that on the same machine it
works, but then you move it to a different machine and it doesn't deserialize
correctly. ... I forget the specifics but I think that was the problem with
this "simple serialization" technique.
> Serialising l
e
Display stack trace? [yN]
{code}
> Serialising lambdas for RemoteGraph
> ---
>
> Key: TINKERPOP-1230
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1230
> Project: TinkerPop
&
https://github.com/mpollmeier/jvm-lambda-serialisation
> Serialising lambdas for RemoteGraph
> ---
>
> Key: TINKERPOP-1230
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1230
> Project: TinkerPop
>
https://github.com/mpollmeier/jvm-lambda-serialisation
> Serialising lambdas for RemoteGraph
> ---
>
> Key: TINKERPOP-1230
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1230
> Project: TinkerPop
>
n compile exec:java -Dexec.mainClass="LambdaDeserialisation"
https://github.com/mpollmeier/jvm-lambda-serialisation
> Serialising lambdas for RemoteGraph
> ---
>
> Key: TINKERPOP-1230
> URL: https://
com/mpollmeier/jvm-lambda-serialisation
> Serialising lambdas for RemoteGraph
> ---
>
> Key: TINKERPOP-1230
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1230
> Project: TinkerPop
>
/commit/dc3620bda420c4549a22261657164f64e4a32f78
after the fix for TINKERPOP-1239 was merged to master.
> Re-use Client instances in RemoteGraph tests
>
>
> Key: TINKERPOP-1238
> URL: https://issues.apache.
stephen mallette created TINKERPOP-1238:
---
Summary: Re-use Client instances in RemoteGraph tests
Key: TINKERPOP-1238
URL: https://issues.apache.org/jira/browse/TINKERPOP-1238
Project: TinkerPop
[
https://issues.apache.org/jira/browse/TINKERPOP-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marko A. Rodriguez closed TINKERPOP-1231.
-
Resolution: Implemented
> Get RemoteGraph to work with GraphCompu
the pull request at:
https://github.com/apache/incubator-tinkerpop/pull/275
> Get RemoteGraph to work with GraphComputer traversals (OLAP).
> -
>
> Key: TINKERPOP-1231
> URL: https://iss
ette commented on the pull request:
https://github.com/apache/incubator-tinkerpop/pull/275#issuecomment-200900333
Paired with marko on this yesterday - good stuff: VOTE +1
> Get RemoteGraph to work with GraphComputer traversal
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-tinkerpop/pull/275
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the fe
Github user spmallette commented on the pull request:
https://github.com/apache/incubator-tinkerpop/pull/275#issuecomment-200900333
Paired with marko on this yesterday - good stuff: VOTE +1
---
If your project is set up for it, you can reply to this email and have your
reply appear o
Github user okram commented on the pull request:
https://github.com/apache/incubator-tinkerpop/pull/275#issuecomment-200876559
```
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache TinkerPop ...
INFO]
[INFO] Total time: 3:22:25.665s
[INFO] Finished at: Wed Mar 23 22:11:36 MDT 2016
[INFO] Final Memory: 97M/814M
[INFO]
```
> Get RemoteGraph to work with GraphC
Github user okram commented on the pull request:
https://github.com/apache/incubator-tinkerpop/pull/275#issuecomment-200568210
VOTE +1. Docs build and published as well.
http://tinkerpop.apache.org/docs/3.2.0-SNAPSHOT/reference/
---
If your project is set up for it, you can reply to
d on the pull request:
https://github.com/apache/incubator-tinkerpop/pull/275#issuecomment-200568210
VOTE +1. Docs build and published as well.
http://tinkerpop.apache.org/docs/3.2.0-SNAPSHOT/reference/
> Get RemoteGraph to work with GraphComputer traversal
Github user spmallette commented on the pull request:
https://github.com/apache/incubator-tinkerpop/pull/275#issuecomment-200295615
This is cool - I will have to think about how to serialize back specific
exceptions. There's room in the protocol for that if I recall correctly. The
t
d be only able to send back standard Java exceptions i guess as
sending back others might put the client in a position where it can't
deserialize the exception if the exception class is only on the server but not
the client.
> Get RemoteGraph to work with GraphCom
"code" - it serializes data in objects and
that isn't enough to allow you to deserialize on the server for all cases.
It would be amazing if you could figure out how this would work, but it sounds
like you've reached the same roadblocks that everyone else has.
> Seriali
Github user okram commented on the pull request:
https://github.com/apache/incubator-tinkerpop/pull/275#issuecomment-200045429
@twilmes --- While we can merge at this time, there is some things I would
like @spmallette to look at. He will most likely add a commit.
---
If your projec
d on the pull request:
https://github.com/apache/incubator-tinkerpop/pull/275#issuecomment-200045429
@twilmes --- While we can merge at this time, there is some things I would
like @spmallette to look at. He will most likely add a commit.
> Get RemoteGraph to work with GraphC
nted on the pull request:
https://github.com/apache/incubator-tinkerpop/pull/275#issuecomment-200038337
Nice addition to the remote graph functionality. Code looks good.
VOTE +1
> Get RemoteGraph to work with GraphComputer traversal
Github user twilmes commented on the pull request:
https://github.com/apache/incubator-tinkerpop/pull/275#issuecomment-200038337
Nice addition to the remote graph functionality. Code looks good.
VOTE +1
---
If your project is set up for it, you can reply to this email and
ed a pull request:
https://github.com/apache/incubator-tinkerpop/pull/275
TINKERPOP-1231: Get RemoteGraph to work with GraphComputer traversals
(OLAP).
https://issues.apache.org/jira/browse/TINKERPOP-1231
I got `RemoteGraph` to work with `GraphComputer` OLAP traversals. I ha
GitHub user okram opened a pull request:
https://github.com/apache/incubator-tinkerpop/pull/275
TINKERPOP-1231: Get RemoteGraph to work with GraphComputer traversals
(OLAP).
https://issues.apache.org/jira/browse/TINKERPOP-1231
I got `RemoteGraph` to work with
Marko A. Rodriguez created TINKERPOP-1231:
-
Summary: Get RemoteGraph to work with GraphComputer traversals
(OLAP).
Key: TINKERPOP-1231
URL: https://issues.apache.org/jira/browse/TINKERPOP-1231
the RemoteGraph.
I didn't quite get there, but wanted to share my findings:
* it's possible to serialise lambdas on the jvm by just extending
`Serializable`:
http://stackoverflow.com/questions/22807912/how-to-serialize-a-lambda/22808112#22808112
* sending a normal predicate doesn'
the RemoteGraph.
I didn't quite get there, but wanted to share my findings:
* it's possible to serialise lambdas on the jvm by just extending
`Serializable`:
http://stackoverflow.com/questions/22807912/how-to-serialize-a-lambda/22808112#22808112
* sending a normal predicate doesn'
the RemoteGraph.
I didn't quite get there, but wanted to share my findings:
* it's possible to serialise lambdas on the jvm by just extending
`Serializable`:
http://stackoverflow.com/questions/22807912/how-to-serialize-a-lambda/22808112#22808112
* sending a normal predicate doesn'
Michael Pollmeier created TINKERPOP-1230:
Summary: Serialising lambdas for RemoteGraph
Key: TINKERPOP-1230
URL: https://issues.apache.org/jira/browse/TINKERPOP-1230
Project: TinkerPop
the pull request at:
https://github.com/apache/incubator-tinkerpop/pull/269
> Implement RemoteGraph
> -
>
> Key: TINKERPOP-575
> URL: https://issues.apache.org/jira/browse/TINKERPOP-575
> Project: TinkerPop
d on the pull request:
https://github.com/apache/incubator-tinkerpop/pull/269#issuecomment-198126388
The insane PR. VOTE +1.
> Implement RemoteGraph
> -
>
> Key: TINKERPOP-575
> URL: https://issues.apache.org/jira/b
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-tinkerpop/pull/269
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the fe
d on the pull request:
https://github.com/apache/incubator-tinkerpop/pull/269#issuecomment-198125740
Wonderful!
VOTE: +1
> Implement RemoteGraph
> -
>
> Key: TINKERPOP-575
> URL: https://issues.apache.org/ji
ities
plugin activated: tinkerpop.tinkergraph
gremlin> graph = RemoteGraph.open('conf/remote-graph.properties')
==>remotegraph[DriverServerConnection-localhost/127.0.0.1:8182
[graph='graph]]
gremlin> g = graph.traversal()
==>graphtraversalsource[re
[
https://issues.apache.org/jira/browse/TINKERPOP-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette closed TINKERPOP-575.
--
Resolution: Implemented
> Implement RemoteGr
activated: tinkerpop.tinkergraph
gremlin> graph = RemoteGraph.open('conf/remote-graph.properties')
==>remotegraph[DriverServerConnection-localhost/127.0.0.1:8182
[graph='graph]]
gremlin> g = graph.traversal()
==>graphtraversalsource[remotegraph[DriverServerConnection-loc
GitHub user spmallette opened a pull request:
https://github.com/apache/incubator-tinkerpop/pull/269
TINKERPOP-575 RemoteGraph
https://issues.apache.org/jira/browse/TINKERPOP-575
This is a brute of a PR that introduces `RemoteGraph`. The tests execute as
part of gremlin
Github user dkuppitz commented on the pull request:
https://github.com/apache/incubator-tinkerpop/pull/269#issuecomment-198125740
Wonderful!
VOTE: +1
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your proje
Github user spmallette commented on the pull request:
https://github.com/apache/incubator-tinkerpop/pull/269#issuecomment-198311155
@mpollmeier that was a nice bug find. i never unpackaged the zip and my
assembly files had a bug in them. the `scripts` directory wasn't being included
ed a pull request:
https://github.com/apache/incubator-tinkerpop/pull/269
TINKERPOP-575 RemoteGraph
https://issues.apache.org/jira/browse/TINKERPOP-575
This is a brute of a PR that introduces `RemoteGraph`. The tests execute as
part of gremlin-server with regular old `mvn c
support binary traversal
submissions by simply implementing RemoteConnection.
http://tinkerpop.apache.org/docs/3.2.0-SNAPSHOT/dev/provider/#remoteconnection-implementations
This idea came from Matthias Bröcheler. His point was that RemoteGraph is a
great idea, but forcing vendors to pac
Github user okram commented on the pull request:
https://github.com/apache/incubator-tinkerpop/pull/269#issuecomment-198126388
The insane PR. VOTE +1.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Check out this new RemoteGraph business for 3.2.0...
gremlin> graph = RemoteGraph.open('conf/remote-graph.properties')
==>remotegraph[DriverServerConnection-localhost/127.0.0.1:8182
[graph=graph]]
gremlin> g = graph.traversal()
==>graphtraversalsource[remotegraph[DriverServ
nted on the pull request:
https://github.com/apache/incubator-tinkerpop/pull/269#issuecomment-198622155
works fine now, thanks!
> Implement RemoteGraph
> -
>
> Key: TINKERPOP-575
> URL: https://issues.apache.org/jira/b
ldn't get initialized with data which so you were executing
your remotes against an empty graph and getting no results. Should work for
you now if you try again. Reviewing the distributions now to be sure nothing
else is amiss.
> Implement RemoteGraph
> -
>
>
Github user mpollmeier commented on the pull request:
https://github.com/apache/incubator-tinkerpop/pull/269#issuecomment-198622155
works fine now, thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
[
https://issues.apache.org/jira/browse/TINKERPOP-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette updated TINKERPOP-575:
---
Summary: Implement RemoteGraph (was: Implement withServer())
> Implem
o be implemented when TINKERPOP-971 is merged. Should be fun.
> Consider implementing a RemoteGraph
> ---
>
> Key: TINKERPOP-575
> URL: https://issues.apache.org/jira/browse/TINKERPOP-575
> Project: TinkerPop
ttps://issues.apache.org/jira/browse/TINKERPOP3-971 what
{{GremlinServerStrategy}} does and how it solves this ticket.
> Consider implementing a RemoteGraph
> ---
>
> Key: TINKERPOP3-575
> URL: https://issues.apache.org/jir
into this, we need an easy way to create {{TraversalEngines}}.
This is related: https://issues.apache.org/jira/browse/TINKERPOP3-971
> Consider implementing a RemoteGraph
> ---
>
> Key: TINKERPOP3-575
> URL: https://iss
hink that your specific example would work because the
value of "name" would be stored in the step and serialized with the
{{Traversal}} to be sent to the server.
> Consider implementing a RemoteGraph
> ---
>
> Key: TINKERPOP3
ocal executor context be available in a
traversal? i.e, would this work
{{def name = "bob"; remoteGraphTraversal.V().has("name", name")}}
> Consider implementing a RemoteGraph
> ---
>
> Key: TINKERPOP3-575
>
[
https://issues.apache.org/jira/browse/TINKERPOP3-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14744342#comment-14744342
]
Matthias Broecheler commented on TINKERPOP3-575:
----
RemoteGraph woul
compliant {{RemoteGraph}} would need to be with the test
suite, but there would potentially need to be some changes to error handling in
the Gremlin Server protocol to get {{RemoteGraph}} fully compliant with it.
Gremlin Server doesn't send back java exceptions - it generalizes errors so
60 matches
Mail list logo
