Been following this since I would eventually like to get gremlinbin back on
its feet. Vote +1
On Thu 18 Feb 2021 at 06:58, wrote:
> VOTE +1
>
> -Ursprüngliche Nachricht-
> Von: Divij Vaidya
> Gesendet: Donnerstag, 18. Februar 2021 05:52
> An: dev@tinkerpop.apache.org
> Betreff: Re:
Tests with the php driver all pass here as well.
VOTE +1
On Thu, May 10, 2018 at 11:43 AM, Stephen Mallette
wrote:
> bah...hate when stuff like that happens. i can update that manually i
> guess, but the zip artifacts are just going to have ship with that typo.
>
Tests with the php driver all pass. No regressions or anything noticeable.
VOTE +1
On Thu, May 10, 2018 at 10:48 AM, Daniel Kuppitz wrote:
> VOTE: +1
>
> On Wed, May 9, 2018 at 10:15 AM, Ted Wilmes wrote:
>
> > Docs and validate looked good +1
> >
> >
er a thing (i.e. the toString() of a complex object)
> because GraphSON 3.0 allows complex keys. That "1" was a hack in prior
> versions of GraphSON to get around that problem. We shouldn't be trying to
> carry that forward. Does that make sense?
>
> On Mon, Apr 16, 2018 at 4:17
But still a little lopsided.
BTW if you're wondering, the "1" key from GRAPHSON 1.0 is a string
representation of the *element id*. So I really wouldn't be surprised if
people were using that information currently.
On Mon, Apr 16, 2018 at 4:04 PM, Dylan Millikin <dyl
t;:1},
"label":"vertex",
"properties":{"name": ...
I like the new way better to be honest. And it's probably more consistent
with gryo, but this is a breaking change and inconsistent across
serializing methods ATM. At the very l
n Server just understands it that way.
>
>
>
> On Mon, Apr 16, 2018 at 1:51 AM, Dylan Millikin <dm...@apache.org> wrote:
>
> > Hey guys,
> >
> > Just been working on implementing GRAPHSON 3.0 into the php world.
> (testing
> > against gremlin-server 3.3.2
Hey guys,
Just been working on implementing GRAPHSON 3.0 into the php world. (testing
against gremlin-server 3.3.2)
I noticed that the following request message fails:
{
"@type":"g:Map",
"@value":[
"requestId","f990037e-3b55-49a4-a108-2f0e8c162715",
"processor","",
Ran all tests from the php end. Everything passes. Actually added a couple
more and those also pass.
VOTE: +1
On Fri, Apr 6, 2018 at 9:29 AM, Jason Plurad wrote:
> Validated the binaries, did several manual tests with the Gremlin Server +
> Gremlin Console, looked over the
Hey guys,
Sorry I've been so absent over the past year I've been having a lot of
personal issues. But I've been keeping a bit of an eye on things regardless
and plan on making a proper comeback to bring everything up to speed.
I noticed JB had a few docker images going so I might use those to
I ran the php driver tests against this locally and everything is good.
VOTE +1 from me!!
Cheers.
On Mon, Feb 6, 2017 at 7:48 AM, Stephen Mallette
wrote:
> I can't remember the error I got, but I think it makes sense to test
> validate-distribution.sh from the branch
With multiple branches set up as they are here, wouldn't it help to move to
a more classical workflow, that is to push to master and then
backport/cherry pick downwards? This comes with it's own set of
implications but thought I would ask.
On Thu, Nov 3, 2016 at 9:19 PM, Stephen Mallette
Yeah looking great!
On Tue, Oct 4, 2016 at 10:39 AM, Marko Rodriguez
wrote:
> Diamn — that is one solid report.
>
> Marko.
>
> http://markorodriguez.com
>
>
>
> > On Oct 4, 2016, at 8:36 AM, Stephen Mallette
> wrote:
> >
> > A lot of stuff seems
I would wait for 3.3.0. I'm a little confused about the versions at the
moment as I thought our minor version 3.2.x should not be breaking (but
that doesn't seem to be the case since 3.2.2 was breaking compared to
3.2.0, though maybe that was a mishap).
Other than that the PR is a really nice
[
https://issues.apache.org/jira/browse/TINKERPOP-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15537949#comment-15537949
]
Dylan Millikin commented on TINKERPOP-1474:
---
I'm less torn about this now that GLVs
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
+1 I find this to be way more explicit. Kinda got tripped by this a while
back.
On Tue, Sep 20, 2016 at 3:38 PM, Daniel Kuppitz wrote:
> +1
>
> On Tue, Sep 20, 2016 at 3:35 PM, Marko Rodriguez
> wrote:
>
> > Hi,
> >
> > I was thinking that store() and
Yeah. This should be a client side feature.
I think discussing scenarios where retry is useful to clients and bubbling
up proper errors would be the correct solution to this problem. A good
example would be locks, currently clients have no clean way of detecting
locks and retrying appropriately.
[
https://issues.apache.org/jira/browse/TINKERPOP-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15466882#comment-15466882
]
Dylan Millikin commented on TINKERPOP-1427:
---
I hear you, trust me. I'm just pointing out
over Jython, if Jython is not
> up to date and, perhaps more importantly, not the environment users will
> run their code in. Doesn't seem to have much value in that case. Perhaps
> for 3.2.2 we don't have to try to tackle this testing issue completely.
>
> On Tue, Aug 16, 2016 at 9
[
https://issues.apache.org/jira/browse/TINKERPOP-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15422724#comment-15422724
]
Dylan Millikin commented on TINKERPOP-1407:
---
+1 on this
> Default serializers for Grem
d, and then look at how to apply that elsewhere. If we can
> attain that same high bar, then we include a GLV. If we can't, then we wait
> until we can figure out how to. At least that's how I think about it.
>
> I'm not sure if any of that changes your position, but I believe the
+1 sounds good
On Fri, Jul 29, 2016 at 5:25 AM, Stephen Mallette
wrote:
> I just created this issue:
>
> https://issues.apache.org/jira/browse/TINKERPOP-1391
>
> As part of TINKERPOP-1278, I'd went ahead with deprecating the old method
> of sending a Traversal to the
ot; rather than the more narrow view of just "remoting
> traversals". If we go wider, we might come up with some good ideas to
> really broaden access to TinkerPop and graphs in a very big way.
>
> We already have a really big improvement with "remoting" as compared to
t; hi dylan, could you please provide a more concrete example of the problem
> you're facing?
>
> On Fri, Jul 22, 2016 at 1:24 PM, Dylan Millikin <dylan.milli...@gmail.com>
> wrote:
>
> > I'm going to confirm that this is actually a common issue.
> > One th
I'm going to confirm that this is actually a common issue.
One thing to keep in mind is that often times the sideEffects are directly
linked to returned elements on a 1 --> n basis which neither of the above
really help with. That is to say that if you're streaming your results
you'll need the
Ran all the driver tests again neo4j and tinkerpop and everything works as
expected.
VOTE: +1
On Tue, Jul 19, 2016 at 9:20 AM, Stephen Mallette
wrote:
> Hello,
>
> We are happy to announce that TinkerPop 3.2.1 is ready for release - note
> the lack of "-incubating"
Quick question which is probably handled automatically but is this working
with multiple cardinalities on properties?
On Tue, Jul 19, 2016 at 12:05 PM, gallardo.kev...@gmail.com <
gallardo.kev...@gmail.com> wrote:
>
>
> On 2016-07-15 16:25 (+0100), "gallardo.kev...@gmail.com"<
>
+1 from me as well. Sounds good.
On Thu, Jul 14, 2016 at 2:14 PM, Ted Wilmes wrote:
> It does for me too, +1.
>
> --Ted
>
> On Wed, Jul 13, 2016 at 3:44 PM, Hadrian Zbarcea
> wrote:
>
> > +1. It does to me.
> > Hadrian
> >
> >
> > On 07/13/2016 04:29 PM,
Maybe working on referencing these pages via perhaps a blog post from
someone would be cool. Something along the lines of "Creating a graph db
with Tinkerpop" or some other variation that may get good hit results in a
google search.
On Wed, May 25, 2016 at 10:06 AM, Stephen Mallette
Grats guys. I'm genuinely excited about this.
Thanks to everyone who worked so hard to make this happen.
On Mon, May 23, 2016 at 10:49 AM, Marko Rodriguez
wrote:
> Congratulations everyone --- and thank you Stephen for being the Chair of
> the project. You are perfect for
31 matches
Mail list logo