[
https://issues.apache.org/jira/browse/TINKERPOP-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840424#comment-15840424
]
ASF GitHub Bot commented on TINKERPOP-1566:
---
Github user vtslab commented on
Github user vtslab commented on the issue:
https://github.com/apache/tinkerpop/pull/534
Hi @mike-tr-adamson, I am glad you entered the discussion. I think your
main point is valid, namely that there are circumstances, pointed out by you,
when gremlin-driver should select the GSSAPI me
[
https://issues.apache.org/jira/browse/TINKERPOP-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840347#comment-15840347
]
ASF GitHub Bot commented on TINKERPOP-1617:
---
GitHub user okram opened a pull
GitHub user okram opened a pull request:
https://github.com/apache/tinkerpop/pull/549
TINKERPOP-1617: Create a SingleIterationStrategy which will do its best to
rewrite OLAP traversals to not message pass.
https://issues.apache.org/jira/browse/TINKERPOP-1617
There are vario
[
https://issues.apache.org/jira/browse/TINKERPOP-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette closed TINKERPOP-1433.
---
Resolution: Fixed
Fix Version/s: (was: 3.3.0)
just quickly re-opened to
[
https://issues.apache.org/jira/browse/TINKERPOP-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette reopened TINKERPOP-1433:
-
> Add steps to dev docs to help committers get their keys in order
> -
[
https://issues.apache.org/jira/browse/TINKERPOP-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Wilmes closed TINKERPOP-1433.
-
Resolution: Fixed
Fix Version/s: 3.2.4
3.3.0
> Add steps to dev docs
Marko A. Rodriguez created TINKERPOP-1617:
-
Summary: Create a SingleIterationStrategy which will do its best
to rewrite OLAP traversals to not message pass.
Key: TINKERPOP-1617
URL: https://issues.apache.o
[
https://issues.apache.org/jira/browse/TINKERPOP-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
pieter martin updated TINKERPOP-1616:
-
Summary: Strengthen semantics around lazy iteration and graph modifications
(was: Str
pieter martin created TINKERPOP-1616:
Summary: Strengthen semantics around lizy iteration and graph
modifications
Key: TINKERPOP-1616
URL: https://issues.apache.org/jira/browse/TINKERPOP-1616
Proj
I guess there is an inconsistency here that should be resolved.
Specifically, that means deciding on a behavior and then instituting
appropriate tests to enforce that behavior. I agree with Kuppitz that the
preferable way for this to work is to have that traversal be assert "2" as
that is the numbe
Ping!
Any ideas on this.
Thanks
Pieter
On 23/01/2017 19:00, pieter-gmail wrote:
> Hi,
>
> Ran some more tests, seems all is not well.
>
> So the previous example always works (on TinkerPop and Neo4j) because
> bothE is not seen as two queries but rather one and all is well.
>
> Running the same
OK, that's done, as you can no doubt see. Hoping this can make it into 3.2.4.
Thanks.
-Paul
-Original Message-
From: Stephen Mallette [mailto:spmalle...@gmail.com]
Sent: Wednesday, January 25, 2017 6:13 PM
To: dev@tinkerpop.apache.org
Subject: Re: [DISCUSS] Release 3.2.4 and 3.1.6
sure
[
https://issues.apache.org/jira/browse/TINKERPOP-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839856#comment-15839856
]
ASF GitHub Bot commented on TINKERPOP-1583:
---
Github user twilmes commented o
Github user twilmes commented on the issue:
https://github.com/apache/tinkerpop/pull/546
It looks like when I run this against tp32 without
`MatchPredicateStrategy`, the `a` and `b` keys are missing from the results. I
think I figured out what the issue is. Without `MatchPredicateSt
[
https://issues.apache.org/jira/browse/TINKERPOP-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839825#comment-15839825
]
ASF GitHub Bot commented on TINKERPOP-1589:
---
Github user pauljackson comment
Github user pauljackson commented on the issue:
https://github.com/apache/tinkerpop/pull/548
Hadoop build is failing for me, but this happens under normal conditions.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If you
[
https://issues.apache.org/jira/browse/TINKERPOP-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839812#comment-15839812
]
ASF GitHub Bot commented on TINKERPOP-1589:
---
GitHub user pauljackson opened
GitHub user pauljackson opened a pull request:
https://github.com/apache/tinkerpop/pull/548
TINKERPOP-1589 Re-introduced CloseableIterator
https://issues.apache.org/jira/browse/TINKERPOP-1589
Add support for the closing of `Iterators` returned from
`Vertex.vertices()` an
[
https://issues.apache.org/jira/browse/TINKERPOP-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839797#comment-15839797
]
ASF GitHub Bot commented on TINKERPOP-1589:
---
Github user pauljackson closed
[
https://issues.apache.org/jira/browse/TINKERPOP-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839796#comment-15839796
]
ASF GitHub Bot commented on TINKERPOP-1589:
---
Github user pauljackson comment
Github user pauljackson closed the pull request at:
https://github.com/apache/tinkerpop/pull/547
---
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
Github user pauljackson commented on the issue:
https://github.com/apache/tinkerpop/pull/547
Resubmitting this pull request.
---
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
enabl
[
https://issues.apache.org/jira/browse/TINKERPOP-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839791#comment-15839791
]
ASF GitHub Bot commented on TINKERPOP-1566:
---
Github user mike-tr-adamson com
Github user mike-tr-adamson commented on the issue:
https://github.com/apache/tinkerpop/pull/534
I'm concerned about changing the `getMechanism` logic based on the failing
tests. The tests can legitimately fail both ways. It would be valid to fix
those tests so that they can fail on e
I've only attempted running it from the docker build thus far. I'm
thinking it has
to be some odd local environment issue. I'll try again here in a bit and
see if I
can nail down the root cause.
On Thu, Jan 26, 2017 at 8:29 AM, Stephen Mallette
wrote:
> Thanks Ted. Does the GLV issue have some
Thanks Ted. Does the GLV issue have something to do with your python setup?
or is it a problem with the docs themselves?
On Thu, Jan 26, 2017 at 9:26 AM, Ted Wilmes wrote:
> Jason,
> I ctr'ed an update to docs adding instructions for getting keys setup. For
> some reason
> I'm getting consisten
Jason,
I ctr'ed an update to docs adding instructions for getting keys setup. For
some reason
I'm getting consistent failures in the GLV portion of the docs when I'm
generation them so I haven't
published updated snapshots yet. For the time being though, if you haven't
started the key process
yet
28 matches
Mail list logo