I think that bothE() == union(outE(),inE()) and outE().count() +
inE().count() == bothE().count(). If you don't want the self-referencing
edge to be returned twice, then either make it a unidirected edge (if
supported) so that it would still satisfy the two previous condition or
dedup(). In either
[
https://issues.apache.org/jira/browse/TINKERPOP-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16219795#comment-16219795
]
ASF GitHub Bot commented on TINKERPOP-1798:
---
Github user robertdale commente
Github user robertdale commented on the issue:
https://github.com/apache/tinkerpop/pull/737
VOTE +1
---
[
https://issues.apache.org/jira/browse/TINKERPOP-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16219764#comment-16219764
]
ASF GitHub Bot commented on TINKERPOP-1791:
---
Github user robertdale commente
Github user robertdale commented on the issue:
https://github.com/apache/tinkerpop/pull/736
VOTE +1
---
Ted Wilmes created TINKERPOP-1810:
-
Summary: Add Lambda.binaryOperator and Lambda.unaryOperator
Key: TINKERPOP-1810
URL: https://issues.apache.org/jira/browse/TINKERPOP-1810
Project: TinkerPop
[
https://issues.apache.org/jira/browse/TINKERPOP-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16219605#comment-16219605
]
ASF GitHub Bot commented on TINKERPOP-1791:
---
Github user dkuppitz commented
Github user dkuppitz commented on the issue:
https://github.com/apache/tinkerpop/pull/736
VOTE: +1
---
[
https://issues.apache.org/jira/browse/TINKERPOP-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16219554#comment-16219554
]
ASF GitHub Bot commented on TINKERPOP-1798:
---
Github user dkuppitz commented
Github user dkuppitz commented on the issue:
https://github.com/apache/tinkerpop/pull/737
VOTE: +1
---
+1 definitely helps me out
On Wed, Oct 25, 2017 at 1:12 PM, Stephen Mallette wrote:
> I'd like to propose that we do release candidates of gremlinpython from
> both master and tp32. We're not quite ready for a full official release as
> of yet (personally, I'd like to see .NET ready to go before
I'd like to propose that we do release candidates of gremlinpython from
both master and tp32. We're not quite ready for a full official release as
of yet (personally, I'd like to see .NET ready to go before we do that),
but we did just fix some bugs in gremlinpython around serialization and
depende
Hello TinkerPop,
I've just published another blog post on DSLs that you might find
interesting:
https://academy.datastax.com/content/gremlin-dsls-python-dse-graph
It focuses on what I think are guidelines that I believe are useful in
designing your Gremlin DSLs, so it is a bit different than my
stephen mallette created TINKERPOP-1809:
---
Summary: Process tests shouldn't modify toy data
Key: TINKERPOP-1809
URL: https://issues.apache.org/jira/browse/TINKERPOP-1809
Project: TinkerPop
I've been looking over the current test scenarios on the TINKERPOP-1784
branch, with the C# GLV test suite in mind, and oh man that's an impressive
amount of scenarios!
So far, I have a suggestion.
Instead of
Scenario: g_V_fold_countXlocalX
Given the modern graph
And the traversal of
IMO it should return the edge only once.
Cheers,
Daniel
On Wed, Oct 25, 2017 at 5:47 AM, Stephen Mallette
wrote:
> The test suite doesn't seem to enforce behavior related to self-relating
> edges. TinkerGraph does this:
>
> gremlin> g = TinkerGraph.open().traversal()
> ==>graphtraversalsource[
The test suite doesn't seem to enforce behavior related to self-relating
edges. TinkerGraph does this:
gremlin> g = TinkerGraph.open().traversal()
==>graphtraversalsource[tinkergraph[vertices:0 edges:0], standard]
gremlin> g.addV().as('a').addE('self').to('a')
==>e[1][0-self->0]
gremlin> g.E()
==>
I think there are inherent benefits into creating our own serialization
format, which can be based on existing conventions (like big endian format
for any numeric) but has the advantages of being minimally descriptive. For
complex composite types, we don't have to specify the meta properties that
a
Thanks,
Pieter
On 25/10/2017 14:26, Stephen Mallette wrote:
As there were no objections to making the change, I went ahead and
published - it may take a few minutes for the changes to propogate. Thanks
On Sun, Oct 22, 2017 at 12:35 PM, pieter gmail
wrote:
Hi,
Can I request Sqlg's descriptio
As there were no objections to making the change, I went ahead and
published - it may take a few minutes for the changes to propogate. Thanks
On Sun, Oct 22, 2017 at 12:35 PM, pieter gmail
wrote:
> Hi,
>
> Can I request Sqlg's description on the homepage <
> https://tinkerpop.apache.org/> to be
We might want to use TinkerPop 3.x to experiment with the "perfect"
serialization format for some distant future TinkerPop 4.x. We haven't
quite gotten it completely right with anything that we have thus far, but
on the other hand I don't think we'd conceived of the manner in which we
use IO today
[
https://issues.apache.org/jira/browse/TINKERPOP-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette closed TINKERPOP-1808.
---
Resolution: Done
Assignee: stephen mallette
Fix Version/s: 3.3.1
[
https://issues.apache.org/jira/browse/TINKERPOP-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette updated TINKERPOP-1808:
Affects Version/s: 3.2.6
> Add ability to get the consumer in LambdaSideEffectSt
[
https://issues.apache.org/jira/browse/TINKERPOP-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryn Cooke updated TINKERPOP-1808:
--
Description:
When lambda steps are used in a traversal it would be helpful to allow access
Bryn Cooke created TINKERPOP-1808:
-
Summary: Add ability to get the consumer in LambdaSideEffectStep
Key: TINKERPOP-1808
URL: https://issues.apache.org/jira/browse/TINKERPOP-1808
Project: TinkerPop
25 matches
Mail list logo
