I also recall Daniel mentioning in a post that .store() in OLAP works like
.aggregate() in OLTP so this change could help users distinguish between
both worlds and BFS/DFS.
On Wednesday, 21 September 2016, Dylan Millikin
wrote:
> yeah I like the barrier().store() best
yeah I like the barrier().store() best as well.
On Wed, Sep 21, 2016 at 11:46 AM, Jean-Baptiste Musso
wrote:
> I think barrier().store() for .aggregate() is very appropriate and fully
> tells what is going on.
>
> I like both, +1 for one or the other.
>
> People also tend to
I was thinking about how to test our GLVs (existing and more importantly
future ones to come) and how to best leverage our existing test
infrastructure. We have about 600 "process" suite tests (i.e. test methods
that contain assertions for a particular traversal). Those tests are
re-used in a
I like the idea of deprecating aggregate and combining barrier with store
to get the same behavior, but the flipped version makes more sense to me
"store().barrier()" when running in OLTP mode.
gremlin> g.V().out().aggregate('x').limit(1).cap('x')
==>[v[3],v[3],v[3],v[2],v[4],v[5]]
gremlin>
I imagine that .store('x').barrier() and .barrier().store('x') would have
the same end result while taking slightly different paths at least with how
I read the definitions as they are today in OLTP.
.store('x').barrier() would lazily fill 'x' up to the barrier.
.barrier().store('x') would
GitHub user robertdale opened a pull request:
https://github.com/apache/tinkerpop/pull/430
Fix store step documentation
Query produces 2 results since 3.0.0
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/robertdale/tinkerpop
[
https://issues.apache.org/jira/browse/TINKERPOP-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette closed TINKERPOP-1459.
---
Resolution: Invalid
Assignee: stephen mallette
Ok - thanks
> When
Xian Yi Teng created TINKERPOP-1459:
---
Summary: When executing lines from a file and encountering error,
Gremlin console should disable stack trace prompt
Key: TINKERPOP-1459
URL:
[
https://issues.apache.org/jira/browse/TINKERPOP-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15510750#comment-15510750
]
stephen mallette commented on TINKERPOP-1459:
-
You can run from a file with `-e`:
{code}
[
https://issues.apache.org/jira/browse/TINKERPOP-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette updated TINKERPOP-1459:
Component/s: console
> When executing lines from a file and encountering error,
[
https://issues.apache.org/jira/browse/TINKERPOP-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15511124#comment-15511124
]
ASF GitHub Bot commented on TINKERPOP-1115:
---
GitHub user dkuppitz opened a pull request:
Github user okram commented on the issue:
https://github.com/apache/tinkerpop/pull/431
VOTE +1. Thanks.
---
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
[
https://issues.apache.org/jira/browse/TINKERPOP-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15511221#comment-15511221
]
ASF GitHub Bot commented on TINKERPOP-1115:
---
Github user asfgit closed the pull request at:
[
https://issues.apache.org/jira/browse/TINKERPOP-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15511209#comment-15511209
]
ASF GitHub Bot commented on TINKERPOP-1115:
---
Github user okram commented on the issue:
14 matches
Mail list logo