You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2017/08/22 11:35:02 UTC
[jira] [Updated] (TINKERPOP-1344) ReferenceYYYXXX for better
message passing
[ https://issues.apache.org/jira/browse/TINKERPOP-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stephen mallette updated TINKERPOP-1344:
----------------------------------------
Fix Version/s: (was: 3.3.0)
3.3.1
> ReferenceYYYXXX for better message passing
> ------------------------------------------
>
> Key: TINKERPOP-1344
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1344
> Project: TinkerPop
> Issue Type: Improvement
> Components: process
> Affects Versions: 3.2.0-incubating, 3.1.2-incubating
> Reporter: Marko A. Rodriguez
> Fix For: 3.3.1
>
>
> In https://issues.apache.org/jira/browse/TINKERPOP-1343, I was saying that it would be nice to have the element id type be known so we can do {{writeObject()}} as opposed to {{writeObjectAndClass()}}. I think we could do some good with a hiearchy of classes like:
> {code}
> ReferenceIntVertex
> ReferenceLongVertex
> ReferenceVertex (Object -- what we have now)
> ReferenceUUIDVertex
> ...
> {code}
> ...likewise for Edge, VertexProperty...
> This will save us an extra 32-bits (4 byte int) on the serialization of messages during OLAP message pass as that is all {{ReferenceXXX}} based.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)