[jira] [Assigned] (TINKERPOP-1925) Don't apply PathRetractionStrategy recursively

[ https://issues.apache.org/jira/browse/TINKERPOP-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Mallette reassigned TINKERPOP-1925: --- Assignee: Stephen Mallette (was: Ted Wilmes) > Don't apply PathRetracti

[jira] [Created] (TINKERPOP-2503) Implement look-ahead on PathRetractionStrategy

Stephen Mallette created TINKERPOP-2503: --- Summary: Implement look-ahead on PathRetractionStrategy Key: TINKERPOP-2503 URL: https://issues.apache.org/jira/browse/TINKERPOP-2503 Project: TinkerPop

[jira] [Updated] (TINKERPOP-2503) Implement look-ahead on PathRetractionStrategy

[ https://issues.apache.org/jira/browse/TINKERPOP-2503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Mallette updated TINKERPOP-2503: Description: With TINKERPOP-2499 we made traversal results from {{match()}} mor

[jira] [Commented] (TINKERPOP-2502) Consistent start API for anonymous and regular traversals

[ https://issues.apache.org/jira/browse/TINKERPOP-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17260515#comment-17260515 ] Stephen Mallette commented on TINKERPOP-2502: - I think I understand the p

[jira] [Commented] (TINKERPOP-2501) Websocket Connection handleError in javascript gremlin driver emits 'log' event instead of 'error'

[ https://issues.apache.org/jira/browse/TINKERPOP-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17260547#comment-17260547 ] Stephen Mallette commented on TINKERPOP-2501: - I'm not an expert on the J

Re: Make Gremlin Server Settings file more extensible

Could you be more specific about what you propose in your second idea? I guess i'd like to know how you would like to get the Constructor and how it would affect the API. Thanks On Wed, Jan 6, 2021 at 7:13 AM wrote: > Hi > > > We (JanusGraph) are already automatically settings overwriting defaul

[jira] [Updated] (TINKERPOP-2481) IdentityRemovalStrategy not installed

[ https://issues.apache.org/jira/browse/TINKERPOP-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Mallette updated TINKERPOP-2481: Labels: breaking (was: ) > IdentityRemovalStrategy not installed > ---

[jira] [Updated] (TINKERPOP-2499) PathRetractionStrategy returns inconsistent results when match() is not detected as the final step

[ https://issues.apache.org/jira/browse/TINKERPOP-2499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Mallette updated TINKERPOP-2499: Labels: breaking (was: ) > PathRetractionStrategy returns inconsistent results

[jira] [Commented] (TINKERPOP-2481) IdentityRemovalStrategy not installed

[ https://issues.apache.org/jira/browse/TINKERPOP-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17260730#comment-17260730 ] ASF GitHub Bot commented on TINKERPOP-2481: --- spmallette opened a new pull r

[jira] [Created] (TINKERPOP-2504) Failing ClientConnectionIntegrateTest

Stephen Mallette created TINKERPOP-2504: --- Summary: Failing ClientConnectionIntegrateTest Key: TINKERPOP-2504 URL: https://issues.apache.org/jira/browse/TINKERPOP-2504 Project: TinkerPop

Re: [DISCUSS] ANTLR and gremlin-script

First of all: I love this direction, for all of the reasons cited and the innovation I'm hoping that it opens up. Also, that Amazon Neptune has already done the work and would be willing to share it with the rest of the world is a remarkable gift. I'm just a user / admirer of the technology, but

[jira] [Commented] (TINKERPOP-2481) IdentityRemovalStrategy not installed

[ https://issues.apache.org/jira/browse/TINKERPOP-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17260900#comment-17260900 ] ASF GitHub Bot commented on TINKERPOP-2481: --- bechbd commented on pull reque

Re: [DISCUSS] ANTLR and gremlin-script

+1  I have often thought the language specification should be a project separate from the implementations, and done in a formal but plain English format similar to OMG or IETF specifications.  I suspect Sqlg's code base would have been fastly different if it had evolved from a grammer instead of