[jira] [Commented] (TINKERPOP-1752) Gremlin.Net: Generate completely type-safe methods

[ https://issues.apache.org/jira/browse/TINKERPOP-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16220101#comment-16220101 ] ASF GitHub Bot commented on TINKERPOP-1752: --- Github user jorgebay commented on the issue:

[GitHub] tinkerpop issue #712: TINKERPOP-1752: Gremlin.Net: Generate completely type-...

Github user jorgebay commented on the issue: https://github.com/apache/tinkerpop/pull/712 VOTE +1 ---

[jira] [Created] (TINKERPOP-1811) Improve error reporting for serialization errors between gremlin-python and gremlin-server

Hugo Arts created TINKERPOP-1811: Summary: Improve error reporting for serialization errors between gremlin-python and gremlin-server Key: TINKERPOP-1811 URL: https://issues.apache.org/jira/browse/TINKERPOP-1811

[GitHub] tinkerpop pull request #736: TINKERPOP-1791 Added GremlinDsl.AnonymousMethod...

Github user asfgit closed the pull request at: https://github.com/apache/tinkerpop/pull/736 ---

[jira] [Commented] (TINKERPOP-1791) GremlinDsl custom step with generic end type produces invalid code in __.java

[ https://issues.apache.org/jira/browse/TINKERPOP-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16220295#comment-16220295 ] ASF GitHub Bot commented on TINKERPOP-1791: --- Github user asfgit closed the pull request at:

[jira] [Closed] (TINKERPOP-1791) GremlinDsl custom step with generic end type produces invalid code in __.java

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

[jira] [Closed] (TINKERPOP-1798) MutationListener.vertexPropertyChanged oldValue should be a VertexProperty

[ https://issues.apache.org/jira/browse/TINKERPOP-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stephen mallette closed TINKERPOP-1798. --- Resolution: Fixed Fix Version/s: 3.3.1 3.2.7 >

[jira] [Commented] (TINKERPOP-1798) MutationListener.vertexPropertyChanged oldValue should be a VertexProperty

[ https://issues.apache.org/jira/browse/TINKERPOP-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16220297#comment-16220297 ] ASF GitHub Bot commented on TINKERPOP-1798: --- Github user asfgit closed the pull request at:

[GitHub] tinkerpop pull request #737: TINKERPOP-1798 Fix signature of MutationListene...

Github user asfgit closed the pull request at: https://github.com/apache/tinkerpop/pull/737 ---

[jira] [Comment Edited] (TINKERPOP-1816) Consider improvements to the .NET documentation

[ https://issues.apache.org/jira/browse/TINKERPOP-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16220393#comment-16220393 ] Bill Woo edited comment on TINKERPOP-1816 at 10/26/17 1:01 PM: --- Without

[jira] [Commented] (TINKERPOP-1816) Consider improvements to the .NET documentation

[ https://issues.apache.org/jira/browse/TINKERPOP-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16220435#comment-16220435 ] Jorge Bay commented on TINKERPOP-1816: -- Can you specify which areas are not covered in the docs:

[jira] [Updated] (TINKERPOP-1816) Consider improvements to the .NET documentation

[ https://issues.apache.org/jira/browse/TINKERPOP-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stephen mallette updated TINKERPOP-1816: Summary: Consider improvements to the .NET documentation (was: the .NET port

[jira] [Commented] (TINKERPOP-1816) Consider improvements to the .NET documentation

[ https://issues.apache.org/jira/browse/TINKERPOP-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16220393#comment-16220393 ] Bill Woo commented on TINKERPOP-1816: - Without a certain minimal level of documentation, there is

[jira] [Created] (TINKERPOP-1812) ProfileTest assumes that graph implementations will not add their own steps

Bryn Cooke created TINKERPOP-1812: - Summary: ProfileTest assumes that graph implementations will not add their own steps Key: TINKERPOP-1812 URL: https://issues.apache.org/jira/browse/TINKERPOP-1812

[jira] [Updated] (TINKERPOP-1806) Consistently use Gremlin.Net instead of Gremlin-DotNet

[ https://issues.apache.org/jira/browse/TINKERPOP-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stephen mallette updated TINKERPOP-1806: Issue Type: Improvement (was: Task) > Consistently use Gremlin.Net instead of

[jira] [Commented] (TINKERPOP-1816) Consider improvements to the .NET documentation

[ https://issues.apache.org/jira/browse/TINKERPOP-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16220424#comment-16220424 ] stephen mallette commented on TINKERPOP-1816: - > Without a certain minimal level of

[jira] [Created] (TINKERPOP-1813) Subgraph strategy requires the graph API

Bryn Cooke created TINKERPOP-1813: - Summary: Subgraph strategy requires the graph API Key: TINKERPOP-1813 URL: https://issues.apache.org/jira/browse/TINKERPOP-1813 Project: TinkerPop Issue

Re: [DISCUSS] GLV Test Suite

I can't help thinking that perhaps non-JVM languages need to leverage bytecode to make traversal building easier. We already have an established pattern for converting bytecode into Traversals and while it is different for each language, it's generally governed by the Translator interface. Note

[jira] [Updated] (TINKERPOP-1816) the .NET port has no useful documentation

[ https://issues.apache.org/jira/browse/TINKERPOP-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stephen mallette updated TINKERPOP-1816: Affects Version/s: 3.2.6 > the .NET port has no useful documentation >

[jira] [Updated] (TINKERPOP-1816) the .NET port has no useful documentation

[ https://issues.apache.org/jira/browse/TINKERPOP-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stephen mallette updated TINKERPOP-1816: Issue Type: Improvement (was: Bug) > the .NET port has no useful documentation

Re: [DISCUSS] bothE() on self-reference

Maybe outE() and inE() should only return non-self-referencing edges. Then there should be a new step called selfE(). And every time it's called, it posts a picture of Gremlin holding that edge to Facebook. :-) Hmm.. it seems like you made the engineering case. What's the user perspective? I

[jira] [Created] (TINKERPOP-1816) the .NET port has no useful documentation

Bill Woo created TINKERPOP-1816: --- Summary: the .NET port has no useful documentation Key: TINKERPOP-1816 URL: https://issues.apache.org/jira/browse/TINKERPOP-1816 Project: TinkerPop Issue

[jira] [Updated] (TINKERPOP-1816) the .NET port has no useful documentation

[ https://issues.apache.org/jira/browse/TINKERPOP-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Woo updated TINKERPOP-1816: Description: Without at least one complete code sample, you are wasting potential users; time.

[jira] [Created] (TINKERPOP-1814) Some process tests require the graph API

Bryn Cooke created TINKERPOP-1814: - Summary: Some process tests require the graph API Key: TINKERPOP-1814 URL: https://issues.apache.org/jira/browse/TINKERPOP-1814 Project: TinkerPop Issue

[jira] [Updated] (TINKERPOP-1814) Some process tests require the graph API

[ https://issues.apache.org/jira/browse/TINKERPOP-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stephen mallette updated TINKERPOP-1814: Issue Type: Improvement (was: Test) > Some process tests require the graph API

Re: remove step

Is there some difference between what you are proposing and: http://tinkerpop.apache.org/docs/current/reference/#drop-step On Thu, Oct 26, 2017 at 2:18 PM, pieter gmail wrote: > Hi, > > I was wondering if we can add a remove step. Currently to remove elements > I

Re: [jira] [Created] (TINKERPOP-1812) ProfileTest assumes that graph implementations will not add their own steps

I racked my brain on it a bit a while back without any good fixit's really a TinkerGraph test. I probably should just migrate them over there and stop pressing them down on other providers. On Thu, Oct 26, 2017 at 2:31 PM, pieter gmail wrote: > In Sqlg many profile

remove step

Hi, I was wondering if we can add a remove step. Currently to remove elements I iterate the traversal and call remove on each element. Adding a remove step will make it possible to optimize removals. Its probably less useful for Neo4j and TinkerGraph, not sure about Janus but for Sqlg,

[jira] [Updated] (TINKERPOP-1812) ProfileTest assumes that graph implementations will not add their own steps

[ https://issues.apache.org/jira/browse/TINKERPOP-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stephen mallette updated TINKERPOP-1812: Issue Type: Improvement (was: Test) > ProfileTest assumes that graph

Re: remove step

Ha, there it is already. Sorry did not know about that one. A rtfm moment. Thanks Pieter On 26/10/2017 20:21, Stephen Mallette wrote: Is there some difference between what you are proposing and: http://tinkerpop.apache.org/docs/current/reference/#drop-step On Thu, Oct 26, 2017 at 2:18 PM,

Re: [jira] [Created] (TINKERPOP-1812) ProfileTest assumes that graph implementations will not add their own steps

Yes. We should have only a primitive ProfileTest that ensures that a TraversalMetrics object is returned and that is it. Marko. > On Oct 26, 2017, at 12:35 PM, Stephen Mallette wrote: > > I racked my brain on it a bit a while back without any good fixit's > really

Re: [jira] [Created] (TINKERPOP-1812) ProfileTest assumes that graph implementations will not add their own steps

In Sqlg many profile tests are ignored because of this. Including steps being removed. Back in the day no-one including myself had any interest in fixing it. Its not trivial by all accounts. Cheers Pieter On 26/10/2017 13:21, Bryn Cooke (JIRA) wrote: Bryn Cooke created TINKERPOP-1812:

[jira] [Commented] (TINKERPOP-1816) Consider improvements to the .NET documentation

[ https://issues.apache.org/jira/browse/TINKERPOP-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16220590#comment-16220590 ] Bill Woo commented on TINKERPOP-1816: - With the same time and energy you just spent constructing a

[jira] [Created] (TINKERPOP-1815) Graph io requires the graph API

Bryn Cooke created TINKERPOP-1815: - Summary: Graph io requires the graph API Key: TINKERPOP-1815 URL: https://issues.apache.org/jira/browse/TINKERPOP-1815 Project: TinkerPop Issue Type:

Re: [DISCUSS] GLV Test Suite

I see that for most languages using bytecode to native language translator would be the easiest solution. In the case of the JavaScript GLV, it would be fairly straightforward to implement (and I plan to do so!). In the case of C#, being more strict regarding typing than java, it would be an