GitHub user sjudeng opened a pull request:
https://github.com/apache/tinkerpop/pull/458
Message scope initialization in PeerPressureVertexProgram
These updates resolve issues observed running tinkerpop-3.2.2 tests against
Titan. Sorry if this should have been submitted through JIRA.
### Message scope initialization in PeerPressureTest
Failing test was
`g_V_peerPressure_byXclusterX_byXoutEXknowsXX_pageRankX1X_byXrankX_byXoutEXknowsXX_timesX2X_group_byXclusterX_byXrank_sumX`
During test execution it was observed at the failing (vote) step that the
message scope was `VertexStep(OUT,[knows],edge)`, but this didn't match the
message scope, `VertexStep(OUT,edge)`, in the statically initialized set,
`VOTE_SCOPE`, returned by `PeerPressureVertexProgram#getMessageScopes`. This
caused an error in the custom memory implementation that is resolved by moving
the initialization as shown in this PR.
### Vertex id checks in BulkDumperVertexProgramTest
Vertex id checks fail when implementation does not support user-specified
ids
### Transaction rollback in TransactionTest
Implementation fails to rollback a transaction that is already closed
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ngageoint/tinkerpop tp32-tests
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tinkerpop/pull/458.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #458
----
commit 531e62c3302fec092fa7e10d5c87b96e8eb4f4a6
Author: sjudeng <[email protected]>
Date: 2016-10-18T00:02:46Z
Lazy message scope initialization in PeerPressureVertexProgram. Remove
vertex id checks in BulkDumperVertexProgramTest. Don't rollback transaction if
already closed in TransactionTest.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
