Re: gremlin-driver ResultQueueTest.shouldDrainAsItemsArrive() delay

Timed tests generally stink - if you see a better way to represent the nature of that test, I'd be open to changes for sure. If you just want to bump the timeout, feel free to offer a pull request for review. On Mon, Jun 26, 2017 at 8:54 PM, Andy Davidoff wrote: > Running tests on a slow server

gremlin-driver ResultQueueTest.shouldDrainAsItemsArrive() delay

Running tests on a slow server demonstrated a false failure in gremlin-driver’s ResultQueueTest.shouldDrainAsItemsArrive() due to an insufficient delay of 3 seconds. In my case, I needed >10 seconds to execute the test successfully. If this test is going to fail, having it take even 30 seconds

Re: [DISCUSS] Gryo 3.0

Now that we have gremlin-io-test for 3.3.0 which tests different versions of gryo/graphson over different versions of tinkerpop (meaning the current version you build with ensure that it can still read/write the old formats) do we need to do this: https://issues.apache.org/jira/browse/TINKERPOP-13

[jira] [Commented] (TINKERPOP-1592) Add withDetachment() and specify the "detachment" model.

[ https://issues.apache.org/jira/browse/TINKERPOP-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063756#comment-16063756 ] Marko A. Rodriguez commented on TINKERPOP-1592: --- I have it right now whe

Re: [DISCUSS] Remaining Items for 3.3.0

Looking back at this thread, I think that since there were no objections to doing "pre-releases" of GLVs I think we can postpone the test suite changes. So, i'm fine with that being off the table. Looking at my list, I'm also surprised that I didn't include: https://issues.apache.org/jira/browse/

Re: [DISCUSS] GraphSON as the future of all serialization.

Hi, > Is that https://github.com/arangodb/velocypack ? Yea. There is a Java version: https://github.com/arangodb/java-velocypack I haven’t studied it, but the general idea of byteoffset lookups in order to nullify the need full obj

Re: [DISCUSS] GraphSON as the future of all serialization.

In retrospect, we really didn't have a good picture of what IO should have been for TinkerPop 3.x. The use cases made sense at the time but I don't think we foresaw GLVs terribly well. Now Gryo is a bit of a burden. Getting tired of hassling with three serialization formats. At least GraphML is pre

Re: [DISCUSS] GraphSON as the future of all serialization.

Is that https://github.com/arangodb/velocypack ? Robert Dale On Mon, Jun 26, 2017 at 10:56 AM, Marko Rodriguez wrote: > Hello, > > This is a “big idea” in that I don’t see it being helpful for TinkerPop3, > but something to consider for TinkerPop4. > > We currently support two “internal” seria

[DISCUSS] GraphSON as the future of all serialization.

Hello, This is a “big idea” in that I don’t see it being helpful for TinkerPop3, but something to consider for TinkerPop4. We currently support two “internal” serialization mechanisms — Gryo and GraphSON. We also support GraphML but this is primarily for data reading/writing (interoperability

[jira] [Commented] (TINKERPOP-1519) TinkerGraphComputer doesn't handle multiple MessageScopes in single iteration

[ https://issues.apache.org/jira/browse/TINKERPOP-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063186#comment-16063186 ] ASF GitHub Bot commented on TINKERPOP-1519: --- Github user okram commented on

[GitHub] tinkerpop issue #632: TINKERPOP-1519: tinker graph computer does not handle ...

Github user okram commented on the issue: https://github.com/apache/tinkerpop/pull/632 The problem is real, the fix works given the specific test case. VOTE +1. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If

Re: [DISCUSS] Gryo 3.0

Just wanted to note that Gryo 3.0 work is happening here in case anyone wants to follow along: https://issues.apache.org/jira/browse/TINKERPOP-1698 I have a branch setup. I think I'm going to clean up Gremlin Server configuration files for 3.3.0 and remove a bunch of the old serializers. The conf

[jira] [Commented] (TINKERPOP-1445) Large nested VertexProperties and Properties do not get printed well

[ https://issues.apache.org/jira/browse/TINKERPOP-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063154#comment-16063154 ] ASF GitHub Bot commented on TINKERPOP-1445: --- Github user asfgit closed the p

[jira] [Closed] (TINKERPOP-1445) Large nested VertexProperties and Properties do not get printed well

[ https://issues.apache.org/jira/browse/TINKERPOP-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stephen mallette closed TINKERPOP-1445. --- Resolution: Done Assignee: stephen mallette Fix Version/s: 3.3.0 >

[GitHub] tinkerpop pull request #631: TINKERPOP-1445 Add ellipses for long property v...

Github user asfgit closed the pull request at: https://github.com/apache/tinkerpop/pull/631 --- 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 is e

[jira] [Closed] (TINKERPOP-1004) Make Transaction.commit() failures consistent across implementations.

[ https://issues.apache.org/jira/browse/TINKERPOP-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stephen mallette closed TINKERPOP-1004. --- Resolution: Done Assignee: stephen mallette Fix Version/s: 3.3.0 >

[jira] [Commented] (TINKERPOP-1004) Make Transaction.commit() failures consistent across implementations.

[ https://issues.apache.org/jira/browse/TINKERPOP-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063150#comment-16063150 ] ASF GitHub Bot commented on TINKERPOP-1004: --- Github user asfgit closed the p

[GitHub] tinkerpop pull request #637: TINKERPOP-1004 Expand usage of TransactionExcep...

Github user asfgit closed the pull request at: https://github.com/apache/tinkerpop/pull/637 --- 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 is e

[jira] [Commented] (TINKERPOP-1551) Solidify and document Gremlin bytecode specification

[ https://issues.apache.org/jira/browse/TINKERPOP-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063084#comment-16063084 ] Marko A. Rodriguez commented on TINKERPOP-1551: --- I believe that this is

[jira] [Closed] (TINKERPOP-1240) Provide support g.script("V().map{closure}")

[ https://issues.apache.org/jira/browse/TINKERPOP-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marko A. Rodriguez closed TINKERPOP-1240. - Resolution: Won't Fix Assignee: Marko A. Rodriguez This is "fixed" using

[jira] [Closed] (TINKERPOP-1078) Do not include TraversalMetrics cap in profile results.

[ https://issues.apache.org/jira/browse/TINKERPOP-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marko A. Rodriguez closed TINKERPOP-1078. - Resolution: Fixed Fix Version/s: (was: 3.2.6) 3.2

[jira] [Closed] (TINKERPOP-974) Saving headless traversals for reuse (clone Iterator Fun)

[ https://issues.apache.org/jira/browse/TINKERPOP-974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marko A. Rodriguez closed TINKERPOP-974. Resolution: Won't Fix Fix Version/s: (was: 3.2.6) This is something th

Re: [DISCUSS] Bytecode bindings cache documentation

I didn't think we could cache traversals that way given: > So, while you can clone() a traversal and re-use it, you can't change its parameterization because its already been compiled and during compilation, many of those parameters were used to determine how it would be compiled. and we certainl

[jira] [Commented] (TINKERPOP-1669) EdgeVertexStep should be designed for extension

[ https://issues.apache.org/jira/browse/TINKERPOP-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16062861#comment-16062861 ] ASF GitHub Bot commented on TINKERPOP-1669: --- Github user spmallette commente

[GitHub] tinkerpop issue #639: TINKERPOP-1669: EdgeVertexStep should be designed for ...

Github user spmallette commented on the issue: https://github.com/apache/tinkerpop/pull/639 VOTE +1 --- 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 t

[jira] [Commented] (TINKERPOP-1552) C# Gremlin Language Variant

[ https://issues.apache.org/jira/browse/TINKERPOP-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16062858#comment-16062858 ] stephen mallette commented on TINKERPOP-1552: - > 2: You can save your api

[jira] [Commented] (TINKERPOP-1552) C# Gremlin Language Variant

[ https://issues.apache.org/jira/browse/TINKERPOP-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16062636#comment-16062636 ] Jorge Bay commented on TINKERPOP-1552: -- [Support for .NET Core projects on msbuil