[
https://issues.apache.org/jira/browse/ATLAS-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16943096#comment-16943096
]
Ashutosh Mestry commented on ATLAS-3434:
----------------------------------------
[~sarath] Thanks for the patch.
I ran few tests with migration import and noticed that the locking exceptions
have disappeared. (It is likely that the occurrence have reduced.)
My tests yielded +ve results: +1 for the patch.
> Update janusgraph-hbase storage manager PREFERRED_TIMESTAMPS from MILLI to
> MICRO
> --------------------------------------------------------------------------------
>
> Key: ATLAS-3434
> URL: https://issues.apache.org/jira/browse/ATLAS-3434
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
> Affects Versions: 2.0.0
> Reporter: Sarath Subramanian
> Assignee: Sarath Subramanian
> Priority: Major
> Fix For: 2.1.0
>
> Attachments: ATLAS-3434.001.patch, precommit-atlas-3434
>
>
> {{The default timestamp resolution property - graph.timestamps in Janusgraph
> is MICRO.}}
> GraphDatabaseConfiguration.TIMESTAMP_PROVIDER = MICRO
>
> But, HBaseStoreManager class in Atlas the default property is different
> HBaseStoreManager.PREFERRED_TIMESTAMPS = MILLI
>
> This Jira is about updating the default
> HBaseStoreManager.PREFERRED_TIMESTAMPS to MICRO to be in alignment with the
> janusgraph default property (GraphDatabaseConfiguration.TIMESTAMP_PROVIDER =
> MICRO)
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
