tinkerpop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TINKERPOP-2033) Maintain order of profile() annotations
Date Fri, 14 Sep 2018 07:06:00 GMT

    [ https://issues.apache.org/jira/browse/TINKERPOP-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16614461#comment-16614461

ASF GitHub Bot commented on TINKERPOP-2033:

Github user nastra commented on the issue:


> Maintain order of profile() annotations
> ---------------------------------------
>                 Key: TINKERPOP-2033
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2033
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: process
>    Affects Versions: 3.4.0
>            Reporter: stephen mallette
>            Assignee: stephen mallette
>            Priority: Minor
>             Fix For: 3.4.0
> The {{annotations}} of {{ImmutableMetrics}} uses a {{ConcurrentHashMap}} but that of
course loses the insertion order. Convert to a {{synchronizedMap}} that takes a {{LinkedHashMap}}
to maintain that order as well as the ability to support concurrent access which is an issue
for some graphs. 
> There was some question as to whether or not this change was breaking to the Gryo format
or not ,but it appears that it is not. Gryo 1.0 and 3.0 remain as intact as they were on previous
releases, though it is worth noting that Gryo 1.0 broke on release on 3.3.0 when it comes
to "metrics" serialization so that break is still intact. Therefore you can't use Gryo 1.0
between 3.2.x and 3.3.x/3.4.x. Not sure how that happened exactly.

This message was sent by Atlassian JIRA

View raw message