[
https://issues.apache.org/jira/browse/TINKERPOP3-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15030946#comment-15030946
]
ASF GitHub Bot commented on TINKERPOP3-978:
-------------------------------------------
Github user PommeVerte commented on the pull request:
https://github.com/apache/incubator-tinkerpop/pull/147#issuecomment-160417491
ok, so I wanted to be thorough with this. Hence de delay.
- `mvn clean install` passes
- `mvn verify -DskipIntegrationTests=false -pl gremlin-server` passes
- wrote some driver side tests and they work properly. but shouldn't
`config: { useMapperFromGraph: graph }` be added to the default configuration
as well?
If there's some drawback to adding the above to the default
`gremlin-server.yaml` and the PR should stay as is then:
VOTE: +1
If there isn't any noticeable drawback I'd be tempted to squeeze that in
before merging.
> Native TinkerGraph Serializers for GraphSON
> -------------------------------------------
>
> Key: TINKERPOP3-978
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-978
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: io, tinkergraph
> Affects Versions: 3.0.2-incubating
> Reporter: stephen mallette
> Assignee: stephen mallette
> Priority: Minor
> Fix For: 3.1.1-incubating
>
>
> TinkerGraph supports native serialization to Gryo, meaning that you can pass
> a TinkerGraph directly to a Kryo object and have it serialize it - which
> means that it can be treated as a return object from Gremlin Server (which is
> nice for subgraphs).
> Add the same capability for GraphSON so that non-jvm languages can take
> advantage of that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
