Re: Unicorn supports their own version of Gremlin.

Sorry for the delay here, been away for a while... Thanks for clarifying things. That makes sense... it's a bit different from the MySQL storage engine model, where one simply implements the API for a new storage engine, plugs it in, and the "top-half" doesn't change (e.g. the query planner /

Re: [DISCUSS] Returning Side Effects

Yes, I expected to return results first and then stream the side-effects. On Fri, Jul 22, 2016 at 5:05 PM, Dylan Millikin wrote: > > Perhaps nicer than doing all that trickery with transactions would be to > self-detach the vertex ahead of time > > This was the

Re: [DISCUSS] Returning Side Effects

> Perhaps nicer than doing all that trickery with transactions would be to self-detach the vertex ahead of time This was the original idea, I never dove too deep into it as the sideEffects were applied mid traversal and extra filtering/SEs still had to occur. I wasn't sure it was actually

Re: [DISCUSS] Download Page

Stephen, I think what Sebb might be getting at is that some things should be spelled out even if they are obvious to some. I agree with this. 3.2.1 (latest, stable) 3.1.3 (bug fixes only) I think the dates should be in ISO8601 format. -MM-DD Otherwise, I think it looks very good. --

Re: [DISCUSS] Returning Side Effects

Yeah sorry I left out an important part. This is especially an issue when you're dealing with an ORM layer that's expecting results of a specific type (for example vertices). You can take the case of a group count as a really simple example. Your result set could be : [{count:5, vertex:v[1]},

Re: [DISCUSS] Download Page

+1 looks great. Link to the documentation, maybe next to the release notes link, would be useful too. -- Jason On Fri, Jul 22, 2016 at 2:07 PM, Stephen Mallette wrote: > I think it might be a good idea to include a "Download Page" on our web > site. It would let us

Re: [DISCUSS] Returning Side Effects

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 wrote: > I'm going to confirm that this is actually a common issue. > One thing to keep in mind is that often times the sideEffects

[DISCUSS] Download Page

I think it might be a good idea to include a "Download Page" on our web site. It would let us better list the versions we have out there and would get us better in line with Apache Infrastructure - for example: https://issues.apache.org/jira/browse/TINKERPOP-1255 I'm also seeing that we yet have

Re: [DISCUSS] interrupt

"It's not clear to me if the problem exists in HSQLDB, the test, or tail step" This had nothing to do with the TailStep bug. That one is resolved for the most part. For the rest, where the problem is, is itself part of the problem. Thread.interrupt() has rather weak semantics having many

Re: [DISCUSS] Returning Side Effects

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

[jira] [Updated] (TINKERPOP-1385) Refactor Profiling test cases

[ https://issues.apache.org/jira/browse/TINKERPOP-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stephen mallette updated TINKERPOP-1385: Affects Version/s: 3.2.1 Priority: Minor (was: Major)

[jira] [Updated] (TINKERPOP-1385) Refactor Profiling test cases

[ https://issues.apache.org/jira/browse/TINKERPOP-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Broecheler updated TINKERPOP-1385: --- Description: The following test cases make assumptions about the number

[jira] [Updated] (TINKERPOP-1385) Refactor Profiling test cases

[ https://issues.apache.org/jira/browse/TINKERPOP-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Broecheler updated TINKERPOP-1385: --- Description: The following test cases make assumptions about the number

[jira] [Created] (TINKERPOP-1385) Refactor Profiling test cases

Matthias Broecheler created TINKERPOP-1385: -- Summary: Refactor Profiling test cases Key: TINKERPOP-1385 URL: https://issues.apache.org/jira/browse/TINKERPOP-1385 Project: TinkerPop

Re: Code Freeze 3.1.3/3.2.1

I'm finishing up all the release work now that the votes are all closed. Announcement of the releases will happen as soon as the Apache mirrors synch up (as late as tomorrow i guess). At this point, the tp31 branch has been re-opened. It has been bumped to 3.1.4-SNAPSHOT and those artifacts have

[RESULT][VOTE] TinkerPop 3.2.1 Release

This vote is now closed with a total of 6 +1s, no +0s and no -1s. The results are: BINDING VOTES: +1 (Stephen Mallette, Dylan Millikin, Daniel Kuppitz, Hadrian Zbarcea, Ted Wilmes) 0 (0) -1 (0) NON-BINDING VOTES: +1 (Pieter Martin) 0 (0) -1 (0) Thank you very much, Stephen On Thu, Jul

Re: [GitHub] tinkerpop pull request #363: TINKERPOP-1379 remove excess bulk in tail buffe...

More info -- on vacation from ipad s -- dont make anew graph as you have. Use modern or Grateful. this way olap will test too. order on age or something like that to get the bulking. name you method like all other test methods. in short yoy are doing too much and making your test too