Github user vtslab commented on the issue:
https://github.com/apache/tinkerpop/pull/721
Please do not merge yet, I just noticed two wrong links. I will correct
this later in the week together with the tp33/master branch.
Marc
---
[
https://issues.apache.org/jira/browse/TINKERPOP-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16207186#comment-16207186
]
ASF GitHub Bot commented on TINKERPOP-1786:
---
Github user vtslab commented on
Artem Aliev created TINKERPOP-1801:
--
Summary: OLAP profile() step return incorrect timing
Key: TINKERPOP-1801
URL: https://issues.apache.org/jira/browse/TINKERPOP-1801
Project: TinkerPop
Is
GitHub user artem-aliev opened a pull request:
https://github.com/apache/tinkerpop/pull/733
TINKERPOP-1801: fix profile() timing in OLAP by adding worker iteratiâ¦
â¦on timings to step metrics
this is a simple fix that do not change any API
You can merge this pull request
[
https://issues.apache.org/jira/browse/TINKERPOP-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16208050#comment-16208050
]
ASF GitHub Bot commented on TINKERPOP-1801:
---
GitHub user artem-aliev opened
[
https://issues.apache.org/jira/browse/TINKERPOP-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16208065#comment-16208065
]
Artem Aliev commented on TINKERPOP-1801:
That is simple way to fix it, without
GitHub user artem-aliev opened a pull request:
https://github.com/apache/tinkerpop/pull/734
TINKERPOP-1801: fix profile() timing in OLAP by adding worker iteratiâ¦
â¦on timings to step metrics
this is a simple fix that do not change any API
You can merge this pull request
[
https://issues.apache.org/jira/browse/TINKERPOP-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16208074#comment-16208074
]
ASF GitHub Bot commented on TINKERPOP-1801:
---
GitHub user artem-aliev opened
Github user artem-aliev commented on the issue:
https://github.com/apache/tinkerpop/pull/733
that should be against tp32 branch
---
Github user artem-aliev closed the pull request at:
https://github.com/apache/tinkerpop/pull/733
---
Github user artem-aliev commented on the issue:
https://github.com/apache/tinkerpop/pull/733
See #734
---
[
https://issues.apache.org/jira/browse/TINKERPOP-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16208075#comment-16208075
]
ASF GitHub Bot commented on TINKERPOP-1801:
---
Github user artem-aliev comment
[
https://issues.apache.org/jira/browse/TINKERPOP-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16208077#comment-16208077
]
ASF GitHub Bot commented on TINKERPOP-1801:
---
Github user artem-aliev comment
[
https://issues.apache.org/jira/browse/TINKERPOP-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16208076#comment-16208076
]
ASF GitHub Bot commented on TINKERPOP-1801:
---
Github user artem-aliev closed
> So if I understand correctly the map is only needed for bulking so quite
often is not needed.
afaik, it is only used for bulking though it's hard to characterize how
often it is used - i suppose it all depends on the types of traversals you
write and the nature of the data being traversed.
> A
…do your vertices implement hashCode() and equals() “correctly” ?
Marko.
> On Oct 17, 2017, at 2:40 PM, Stephen Mallette wrote:
>
>> So if I understand correctly the map is only needed for bulking so quite
> often is not needed.
>
> afaik, it is only used for bulking though it's hard to char
Currently Sqlg's optimization strategies removes bulking as it does not
work with Sqlg's way of accessing the database. Sqlg fetches many
VertexSteps in one go and bulking needs it to be on a one by one basis.
Bulking is still possible but only by removing Sqlg's strategies from
the traversal.
Yes the hasCode() and equals() is correct. It is however a slightly
heavier operation than TinkerGraph as Sqlg's Element's id is a more
complex object holding the label and its id.
I should have mentioned that in Sqlg the traverser is always a
B_LP_O_P_S_SE_SL_Traverser. As Sqlg returns multip
18 matches
Mail list logo
