[
https://issues.apache.org/jira/browse/TINKERPOP-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18017014#comment-18017014
]
ASF GitHub Bot commented on TINKERPOP-3182:
-------------------------------------------
spmallette opened a new pull request, #3194:
URL: https://github.com/apache/tinkerpop/pull/3194
https://issues.apache.org/jira/browse/TINKERPOP-3182
`Path` objects were being forcibly detached by reference in GraphSON v1/v2
which put it at odds with v1 untyped. Inclusion or removal of properties should
be controlled via `materializeProperties` only.
There's still a bit of weirdness here for Javascript particularly if you
note the assertions in our tests. That should be resolved separately with a
breaking change:
[TINKERPOP-3186](https://issues.apache.org/jira/browse/TINKERPOP-3186).
VOTE +1
> Consistent serialization of Path for untyped GraphSON
> -----------------------------------------------------
>
> Key: TINKERPOP-3182
> URL: https://issues.apache.org/jira/browse/TINKERPOP-3182
> Project: TinkerPop
> Issue Type: Bug
> Components: io
> Affects Versions: 3.7.4
> Reporter: Stephen Mallette
> Assignee: Stephen Mallette
> Priority: Major
>
> {{Path}} objects are being detached to reference by the GraphSON v2/3
> serializers which puts the output at odds with v1 untyped. This is not a
> documented difference that was expected to exist. Users should control
> property inclusion on elements via the {{materializeProperties}} option.
> Should not be a breaking change and mitigation for performance issues can be
> disabled {{materializeProperties}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
