[jira] [Commented] (TINKERPOP-2076) Build with Java 11
[
https://issues.apache.org/jira/browse/TINKERPOP-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16974158#comment-16974158
]
Robert Dale commented on TINKERPOP-2076:
{{docker/build.sh -i -t -n SUCCESS}}
> Build with Java 11
> --
>
> Key: TINKERPOP-2076
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2076
> Project: TinkerPop
> Issue Type: Improvement
> Components: build-release
>Affects Versions: 3.3.4
> Environment: $ java --version
> java 11 2018-09-25
> Java(TM) SE Runtime Environment 18.9 (build 11+28)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11+28, mixed mode)
>Reporter: Steve Strassmann
>Assignee: Stephen Mallette
>Priority: Major
> Fix For: 3.5.0
>
>
> I cannot build TinkerPop with a current (v11) Java version.
> On the gremlin-users Google group, Robert Dale suggests using Java 8, but
> that is deprecated. Recommended: support current Java versions. Stephen
> Mallette says "we need to start worrying about such things."
> Oracle [says Java 8 is
> deprecated|https://www.oracle.com/technetwork/java/javase/overview/index.html]:
> {quote}{color:#d04437}[End of Public Updates for Oracle JDK
> 8|https://www.oracle.com/technetwork/java/javase/eol-135779.html]{color}
> Oracle will not post further updates of Java SE 8 to its public download
> sites for commercial use after January 2019.
> {quote}
>
> See issue posted in Gremlin-users Google Group:
>
> [https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/gremlin-users/Kgnq4BkrZXQ]
> {{unable to build Tinkerpop from master with mvn clean install. }}
>
> The error appears to be
> An API incompatibility was encountered while executing
> org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce:
> java.lang.ExceptionInInitializerError: null
> {code:java}
> $ git clone https://github.com/apache/tinkerpop.git
> $ git checkout master
> $ mvn --version
> Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
> 2018-06-17T14:33:14-04:00)
> Maven home: /opt/maven
> Java version: 11, vendor: Oracle Corporation, runtime:
> /Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.13.6", arch: "x86_64", family: "mac"
> {code}
>
>
> {code:java}
> $ mvn clean install
> [INFO] Scanning for projects...
> [WARNING] The project org.apache.tinkerpop:tinkerpop:pom:3.4.0-SNAPSHOT uses
> prerequisites which is only intended for maven-plugin projects but not for
> non maven-plugin projects. For such purposes you should use the
> maven-enforcer-plugin. See
> https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] Apache TinkerPop
> [pom]
> [INFO] Apache TinkerPop :: Gremlin Shaded
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Core
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Test
> [jar]
> [INFO] Apache TinkerPop :: TinkerGraph Gremlin
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Groovy
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Driver
> [jar]
> [INFO] Apache TinkerPop :: Neo4j Gremlin
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Server
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Javascript
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Python
> [jar]
> [INFO] Apache TinkerPop :: Gremlin.Net
> [pom]
> [INFO] Apache TinkerPop :: Gremlin.Net - Source
> [pom]
> [INFO] Apache TinkerPop :: Gremlin.Net - Tests
> [pom]
> [INFO] Apache TinkerPop :: Hadoop Gremlin
> [jar]
> [INFO] Apache TinkerPop :: Spark Gremlin
> [jar]
> [INFO] Apache TinkerPop :: SPARQL Gremlin
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Console
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Archetype
> [pom]
> [INFO] Apache TinkerPop :: Archetype - TinkerGraph
> [jar]
> [INFO] Apache TinkerPop :: Archetype - Server
> [jar]
> [INFO] Apache TinkerPop :: Archetype - DSL
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Tools
> [pom]
> [INFO] A
[jira] [Commented] (TINKERPOP-2076) Build with Java 11
[
https://issues.apache.org/jira/browse/TINKERPOP-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16973898#comment-16973898
]
Robert Dale commented on TINKERPOP-2076:
re: 4. images can co-exist for multiple versions through tags. currently what
we see are three images:
{noformat}
tinkerpop:hadoop-2.7.7
tinkerpop:base
ubuntu:xenial
{noformat}
{{ubuntu:xenial}} is obviously the ubuntu base image
{{base}} is the big heavy-weight. it builds on ubuntu and adds updates,
language compilers, and many other things. This is the thing you really don't
want to have to rebuild. Looks like {{dotnet}} is the largest consumer of
space.
{{hadoop-2.7.7}} is much smaller, containing only the hadoop install. Trivial
to rebuild with a newer hadoop version.
So, all we need to do is come up with some new tags for images we need to
co-exist. We could add TinkerPop versioning or divide it by jdk version
(similar to hadoop version).
TinkerPop Versioning:
{noformat}
tinkerpop:base-3.3
tinkerpop:base-3.5
{noformat}
such that {{base-3.3}} is compat with 3.3, 3.4. {{base-3.5}} is compat with
3.5+ (and until some high version exists).
JDK Versioning:
{noformat}
tinkerpop:base-jdk11
tinkerpop:base-jdk8
{noformat}
Self-explanatory. Technically, we don't have to make a {{base-jdk8}}. we can
leave the existing {{base}} alone or just retag it if we really want to migrate
existing images to the new naming scheme.
The only thing that's less clear is how do we want to handle the hadoop image.
{{hadoop-2.7.7_jdk11}}? Do we even still need this? Does the version change
enough to warrant it? Or do we want to move more, potentially changing version
things into it and give it a more general name?
Anyway, lots of options on how to reorganize dependencies, version, and tag
them.
> Build with Java 11
> --
>
> Key: TINKERPOP-2076
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2076
> Project: TinkerPop
> Issue Type: Improvement
> Components: build-release
>Affects Versions: 3.3.4
> Environment: $ java --version
> java 11 2018-09-25
> Java(TM) SE Runtime Environment 18.9 (build 11+28)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11+28, mixed mode)
>Reporter: Steve Strassmann
>Assignee: Stephen Mallette
>Priority: Major
> Fix For: 3.5.0
>
>
> I cannot build TinkerPop with a current (v11) Java version.
> On the gremlin-users Google group, Robert Dale suggests using Java 8, but
> that is deprecated. Recommended: support current Java versions. Stephen
> Mallette says "we need to start worrying about such things."
> Oracle [says Java 8 is
> deprecated|https://www.oracle.com/technetwork/java/javase/overview/index.html]:
> {quote}{color:#d04437}[End of Public Updates for Oracle JDK
> 8|https://www.oracle.com/technetwork/java/javase/eol-135779.html]{color}
> Oracle will not post further updates of Java SE 8 to its public download
> sites for commercial use after January 2019.
> {quote}
>
> See issue posted in Gremlin-users Google Group:
>
> [https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/gremlin-users/Kgnq4BkrZXQ]
> {{unable to build Tinkerpop from master with mvn clean install. }}
>
> The error appears to be
> An API incompatibility was encountered while executing
> org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce:
> java.lang.ExceptionInInitializerError: null
> {code:java}
> $ git clone https://github.com/apache/tinkerpop.git
> $ git checkout master
> $ mvn --version
> Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
> 2018-06-17T14:33:14-04:00)
> Maven home: /opt/maven
> Java version: 11, vendor: Oracle Corporation, runtime:
> /Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.13.6", arch: "x86_64", family: "mac"
> {code}
>
>
> {code:java}
> $ mvn clean install
> [INFO] Scanning for projects...
> [WARNING] The project org.apache.tinkerpop:tinkerpop:pom:3.4.0-SNAPSHOT uses
> prerequisites which is only intended for maven-plugin projects but not for
> non maven-plugin projects. For such purposes you should use the
> maven-enforcer-plugin. See
> https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] Apache TinkerPop
> [pom]
> [INFO] Apache TinkerPop :: Gremlin Shaded
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Core
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Test
> [jar]
> [INFO] Apache TinkerPop :: Tinke
[jira] [Commented] (TINKERPOP-2076) Build with Java 11
[
https://issues.apache.org/jira/browse/TINKERPOP-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16973852#comment-16973852
]
Robert Dale commented on TINKERPOP-2076:
consistency for when things go awry ;)
> Build with Java 11
> --
>
> Key: TINKERPOP-2076
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2076
> Project: TinkerPop
> Issue Type: Improvement
> Components: build-release
>Affects Versions: 3.3.4
> Environment: $ java --version
> java 11 2018-09-25
> Java(TM) SE Runtime Environment 18.9 (build 11+28)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11+28, mixed mode)
>Reporter: Steve Strassmann
>Assignee: Stephen Mallette
>Priority: Major
> Fix For: 3.5.0
>
>
> I cannot build TinkerPop with a current (v11) Java version.
> On the gremlin-users Google group, Robert Dale suggests using Java 8, but
> that is deprecated. Recommended: support current Java versions. Stephen
> Mallette says "we need to start worrying about such things."
> Oracle [says Java 8 is
> deprecated|https://www.oracle.com/technetwork/java/javase/overview/index.html]:
> {quote}{color:#d04437}[End of Public Updates for Oracle JDK
> 8|https://www.oracle.com/technetwork/java/javase/eol-135779.html]{color}
> Oracle will not post further updates of Java SE 8 to its public download
> sites for commercial use after January 2019.
> {quote}
>
> See issue posted in Gremlin-users Google Group:
>
> [https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/gremlin-users/Kgnq4BkrZXQ]
> {{unable to build Tinkerpop from master with mvn clean install. }}
>
> The error appears to be
> An API incompatibility was encountered while executing
> org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce:
> java.lang.ExceptionInInitializerError: null
> {code:java}
> $ git clone https://github.com/apache/tinkerpop.git
> $ git checkout master
> $ mvn --version
> Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
> 2018-06-17T14:33:14-04:00)
> Maven home: /opt/maven
> Java version: 11, vendor: Oracle Corporation, runtime:
> /Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.13.6", arch: "x86_64", family: "mac"
> {code}
>
>
> {code:java}
> $ mvn clean install
> [INFO] Scanning for projects...
> [WARNING] The project org.apache.tinkerpop:tinkerpop:pom:3.4.0-SNAPSHOT uses
> prerequisites which is only intended for maven-plugin projects but not for
> non maven-plugin projects. For such purposes you should use the
> maven-enforcer-plugin. See
> https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] Apache TinkerPop
> [pom]
> [INFO] Apache TinkerPop :: Gremlin Shaded
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Core
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Test
> [jar]
> [INFO] Apache TinkerPop :: TinkerGraph Gremlin
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Groovy
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Driver
> [jar]
> [INFO] Apache TinkerPop :: Neo4j Gremlin
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Server
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Javascript
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Python
> [jar]
> [INFO] Apache TinkerPop :: Gremlin.Net
> [pom]
> [INFO] Apache TinkerPop :: Gremlin.Net - Source
> [pom]
> [INFO] Apache TinkerPop :: Gremlin.Net - Tests
> [pom]
> [INFO] Apache TinkerPop :: Hadoop Gremlin
> [jar]
> [INFO] Apache TinkerPop :: Spark Gremlin
> [jar]
> [INFO] Apache TinkerPop :: SPARQL Gremlin
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Console
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Archetype
> [pom]
> [INFO] Apache TinkerPop :: Archetype - TinkerGraph
> [jar]
> [INFO] Apache TinkerPop :: Archetype - Server
> [jar]
> [INFO] Apache TinkerPop :: Archetype - DSL
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Tools
> [pom]
> [INFO]
[jira] [Commented] (TINKERPOP-2076) Build with Java 11
[
https://issues.apache.org/jira/browse/TINKERPOP-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16973846#comment-16973846
]
Robert Dale commented on TINKERPOP-2076:
re: 4. Noticed that docker/Dockerfile is from xenial but travis is using
bionic. Shouldn't these things match?
> Build with Java 11
> --
>
> Key: TINKERPOP-2076
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2076
> Project: TinkerPop
> Issue Type: Improvement
> Components: build-release
>Affects Versions: 3.3.4
> Environment: $ java --version
> java 11 2018-09-25
> Java(TM) SE Runtime Environment 18.9 (build 11+28)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11+28, mixed mode)
>Reporter: Steve Strassmann
>Assignee: Stephen Mallette
>Priority: Major
> Fix For: 3.5.0
>
>
> I cannot build TinkerPop with a current (v11) Java version.
> On the gremlin-users Google group, Robert Dale suggests using Java 8, but
> that is deprecated. Recommended: support current Java versions. Stephen
> Mallette says "we need to start worrying about such things."
> Oracle [says Java 8 is
> deprecated|https://www.oracle.com/technetwork/java/javase/overview/index.html]:
> {quote}{color:#d04437}[End of Public Updates for Oracle JDK
> 8|https://www.oracle.com/technetwork/java/javase/eol-135779.html]{color}
> Oracle will not post further updates of Java SE 8 to its public download
> sites for commercial use after January 2019.
> {quote}
>
> See issue posted in Gremlin-users Google Group:
>
> [https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/gremlin-users/Kgnq4BkrZXQ]
> {{unable to build Tinkerpop from master with mvn clean install. }}
>
> The error appears to be
> An API incompatibility was encountered while executing
> org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce:
> java.lang.ExceptionInInitializerError: null
> {code:java}
> $ git clone https://github.com/apache/tinkerpop.git
> $ git checkout master
> $ mvn --version
> Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
> 2018-06-17T14:33:14-04:00)
> Maven home: /opt/maven
> Java version: 11, vendor: Oracle Corporation, runtime:
> /Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.13.6", arch: "x86_64", family: "mac"
> {code}
>
>
> {code:java}
> $ mvn clean install
> [INFO] Scanning for projects...
> [WARNING] The project org.apache.tinkerpop:tinkerpop:pom:3.4.0-SNAPSHOT uses
> prerequisites which is only intended for maven-plugin projects but not for
> non maven-plugin projects. For such purposes you should use the
> maven-enforcer-plugin. See
> https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] Apache TinkerPop
> [pom]
> [INFO] Apache TinkerPop :: Gremlin Shaded
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Core
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Test
> [jar]
> [INFO] Apache TinkerPop :: TinkerGraph Gremlin
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Groovy
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Driver
> [jar]
> [INFO] Apache TinkerPop :: Neo4j Gremlin
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Server
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Javascript
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Python
> [jar]
> [INFO] Apache TinkerPop :: Gremlin.Net
> [pom]
> [INFO] Apache TinkerPop :: Gremlin.Net - Source
> [pom]
> [INFO] Apache TinkerPop :: Gremlin.Net - Tests
> [pom]
> [INFO] Apache TinkerPop :: Hadoop Gremlin
> [jar]
> [INFO] Apache TinkerPop :: Spark Gremlin
> [jar]
> [INFO] Apache TinkerPop :: SPARQL Gremlin
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Console
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Archetype
> [pom]
> [INFO] Apache TinkerPop :: Archetype - TinkerGraph
> [jar]
> [INFO] Apache TinkerPop :: Archetype - Server
> [jar]
> [INFO] Apache TinkerPop :: Archetype - DSL
> [jar]
> [INFO] Apache Tink
[jira] [Commented] (TINKERPOP-2262) Improve Netty protocol handling
[ https://issues.apache.org/jira/browse/TINKERPOP-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16957471#comment-16957471 ] Robert Dale commented on TINKERPOP-2262: TP 3.3 uses Netty 4.0.x. Does the affects version still apply? I don't think we would update 3.3 to use Netty 4.1.x otherwise we would have done that. > Improve Netty protocol handling > --- > > Key: TINKERPOP-2262 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2262 > Project: TinkerPop > Issue Type: Improvement > Components: driver, server >Affects Versions: 3.3.7, 3.4.2 >Reporter: Divij Vaidya >Priority: Major > > 4.1.37 adds [https://github.com/netty/netty/pull/9116] which is critical to > the stability of the Java Client. > After the upgrade a follow-up task would : > 1. change the Java Client to set the newly introduced flag > "closeOnProtocolViolation" to false. This would prevent causing all the other > requests using the same channel to fail when a single request causes a > protocol violation. > 2. introduce the protocol exception error handling code on the client to > handle protocol violation exceptions. Currently, the code force replaces the > channel, thus closing all the other requests being served on the channel.[ > https://netty.io/news/2019/06/28/4-1-37-Final.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TINKERPOP-2262) Improve Netty protocol handling
[ https://issues.apache.org/jira/browse/TINKERPOP-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16957469#comment-16957469 ] Robert Dale commented on TINKERPOP-2262: Updated to Netty 4.1.42 outside of this ticket. > Improve Netty protocol handling > --- > > Key: TINKERPOP-2262 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2262 > Project: TinkerPop > Issue Type: Improvement > Components: driver, server >Affects Versions: 3.3.7, 3.4.2 >Reporter: Divij Vaidya >Priority: Major > > 4.1.37 adds [https://github.com/netty/netty/pull/9116] which is critical to > the stability of the Java Client. > After the upgrade a follow-up task would : > 1. change the Java Client to set the newly introduced flag > "closeOnProtocolViolation" to false. This would prevent causing all the other > requests using the same channel to fail when a single request causes a > protocol violation. > 2. introduce the protocol exception error handling code on the client to > handle protocol violation exceptions. Currently, the code force replaces the > channel, thus closing all the other requests being served on the channel.[ > https://netty.io/news/2019/06/28/4-1-37-Final.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (TINKERPOP-2262) Improve Netty protocol handling
[ https://issues.apache.org/jira/browse/TINKERPOP-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale updated TINKERPOP-2262: --- Summary: Improve Netty protocol handling (was: Upgrade to Netty 4.1.37) > Improve Netty protocol handling > --- > > Key: TINKERPOP-2262 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2262 > Project: TinkerPop > Issue Type: Improvement > Components: driver, server >Affects Versions: 3.3.7, 3.4.2 >Reporter: Divij Vaidya >Priority: Major > > 4.1.37 adds [https://github.com/netty/netty/pull/9116] which is critical to > the stability of the Java Client. > After the upgrade a follow-up task would : > 1. change the Java Client to set the newly introduced flag > "closeOnProtocolViolation" to false. This would prevent causing all the other > requests using the same channel to fail when a single request causes a > protocol violation. > 2. introduce the protocol exception error handling code on the client to > handle protocol violation exceptions. Currently, the code force replaces the > channel, thus closing all the other requests being served on the channel.[ > https://netty.io/news/2019/06/28/4-1-37-Final.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TINKERPOP-2289) Use address instead of hostname for connection
[ https://issues.apache.org/jira/browse/TINKERPOP-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16943795#comment-16943795 ] Robert Dale commented on TINKERPOP-2289: I think that would be sufficient. > Use address instead of hostname for connection > -- > > Key: TINKERPOP-2289 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2289 > Project: TinkerPop > Issue Type: Bug > Components: driver >Affects Versions: 3.4.3 >Reporter: Hua Jiang >Assignee: Stephen Mallette >Priority: Minor > Fix For: 3.5.0, 3.3.9, 3.4.4 > > > The current implementation uses hostname to create connections. It causes two > problems in a scenario where multiple addresses are bound to the same domain > name. > # Load balancing is broken because multiple `Host` may connect to the same > address, and some addresses may have no connection at all. > # It produces misleading log messages because the address in the host label > may not be the one the host is actually connected to. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TINKERPOP-2289) Use address instead of hostname for connection
[
https://issues.apache.org/jira/browse/TINKERPOP-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16943754#comment-16943754
]
Robert Dale commented on TINKERPOP-2289:
Java has a built-in mechanism [1] to disable IPv6 which would give you only one
address.
{code:java}
$ groovysh
groovy:000> InetAddress.getAllByName("localhost")
===> [localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1]
$ groovysh -Djava.net.preferIPv4Stack=true
groovy:000> InetAddress.getAllByName("localhost")
===> [localhost/127.0.0.1]
{code}
I'm not sure I would try to "fix" it beyond this.
1.
https://docs.oracle.com/javase/8/docs/api/java/net/doc-files/net-properties.html
> Use address instead of hostname for connection
> --
>
> Key: TINKERPOP-2289
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2289
> Project: TinkerPop
> Issue Type: Bug
> Components: driver
>Affects Versions: 3.4.3
>Reporter: Hua Jiang
>Assignee: Stephen Mallette
>Priority: Minor
> Fix For: 3.5.0, 3.3.9, 3.4.4
>
>
> The current implementation uses hostname to create connections. It causes two
> problems in a scenario where multiple addresses are bound to the same domain
> name.
> # Load balancing is broken because multiple `Host` may connect to the same
> address, and some addresses may have no connection at all.
> # It produces misleading log messages because the address in the host label
> may not be the one the host is actually connected to.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (TINKERPOP-2275) Update jackson databind 2.9.9.3+
[ https://issues.apache.org/jira/browse/TINKERPOP-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16906556#comment-16906556 ] Robert Dale commented on TINKERPOP-2275: 2.9.9.3 was released. > Update jackson databind 2.9.9.3+ > > > Key: TINKERPOP-2275 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2275 > Project: TinkerPop > Issue Type: Improvement > Components: io >Affects Versions: 3.3.7, 3.4.2 >Reporter: Robert Dale >Assignee: Robert Dale >Priority: Minor > Labels: security > Fix For: 3.3.9, 3.4.4 > > > > Fixes more gadget vulnerabilities with ehcache and logback in the classpath. > [https://app.snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-455617] > > Note that the fix is in 2.9.9.2. However, that version broke things. Waiting > for 2.9.9.3 to be released. > [https://github.com/FasterXML/jackson-databind/issues/2395] > > TinkerPop is not directly affected hence low priority (let alone that the fix > isn't even available). > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Closed] (TINKERPOP-2275) Update jackson databind 2.9.9.3+
[ https://issues.apache.org/jira/browse/TINKERPOP-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale closed TINKERPOP-2275. -- Resolution: Fixed > Update jackson databind 2.9.9.3+ > > > Key: TINKERPOP-2275 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2275 > Project: TinkerPop > Issue Type: Improvement > Components: io >Affects Versions: 3.3.7, 3.4.2 >Reporter: Robert Dale >Assignee: Robert Dale >Priority: Minor > Labels: security > Fix For: 3.3.9, 3.4.4 > > > > Fixes more gadget vulnerabilities with ehcache and logback in the classpath. > [https://app.snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-455617] > > Note that the fix is in 2.9.9.2. However, that version broke things. Waiting > for 2.9.9.3 to be released. > [https://github.com/FasterXML/jackson-databind/issues/2395] > > TinkerPop is not directly affected hence low priority (let alone that the fix > isn't even available). > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (TINKERPOP-2275) Update jackson databind 2.9.9.3+
[ https://issues.apache.org/jira/browse/TINKERPOP-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale updated TINKERPOP-2275: --- Fix Version/s: 3.4.4 3.3.9 > Update jackson databind 2.9.9.3+ > > > Key: TINKERPOP-2275 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2275 > Project: TinkerPop > Issue Type: Improvement > Components: io >Affects Versions: 3.3.7, 3.4.2 >Reporter: Robert Dale >Assignee: Robert Dale >Priority: Minor > Labels: security > Fix For: 3.3.9, 3.4.4 > > > > Fixes more gadget vulnerabilities with ehcache and logback in the classpath. > [https://app.snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-455617] > > Note that the fix is in 2.9.9.2. However, that version broke things. Waiting > for 2.9.9.3 to be released. > [https://github.com/FasterXML/jackson-databind/issues/2395] > > TinkerPop is not directly affected hence low priority (let alone that the fix > isn't even available). > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (TINKERPOP-2275) Update jackson databind 2.9.9.3+
Robert Dale created TINKERPOP-2275: -- Summary: Update jackson databind 2.9.9.3+ Key: TINKERPOP-2275 URL: https://issues.apache.org/jira/browse/TINKERPOP-2275 Project: TinkerPop Issue Type: Improvement Components: io Affects Versions: 3.4.2, 3.3.7 Reporter: Robert Dale Assignee: Robert Dale Fixes more gadget vulnerabilities with ehcache and logback in the classpath. [https://app.snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-455617] Note that the fix is in 2.9.9.2. However, that version broke things. Waiting for 2.9.9.3 to be released. [https://github.com/FasterXML/jackson-databind/issues/2395] TinkerPop is not directly affected hence low priority (let alone that the fix isn't even available). -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (TINKERPOP-2272) Rename steps and tokens that conflict with standard python functions
[
https://issues.apache.org/jira/browse/TINKERPOP-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Dale updated TINKERPOP-2272:
---
Description:
The following steps overlap standard python functions:
{code:java}
filter()
id()
max()
min()
range()
sum()
{code}
They need to be renamed to have the underscore suffix.
List discussion:
[https://groups.google.com/forum/#!topic/gremlin-users/Na4wKhZ4_dU]
was:
The following steps overlap standard python functions:
{code}
filter()
id()
max()
min()
range()
sum()
{code}
They need to be renamed to have the underscore suffix.
> Rename steps and tokens that conflict with standard python functions
>
>
> Key: TINKERPOP-2272
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2272
> Project: TinkerPop
> Issue Type: Improvement
> Components: python
>Affects Versions: 3.3.7
>Reporter: stephen mallette
>Assignee: stephen mallette
>Priority: Major
>
> The following steps overlap standard python functions:
> {code:java}
> filter()
> id()
> max()
> min()
> range()
> sum()
> {code}
> They need to be renamed to have the underscore suffix.
>
> List discussion:
> [https://groups.google.com/forum/#!topic/gremlin-users/Na4wKhZ4_dU]
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (TINKERPOP-2267) a very easily solved documentation problem
[ https://issues.apache.org/jira/browse/TINKERPOP-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16884656#comment-16884656 ] Robert Dale commented on TINKERPOP-2267: 3.1.0-incubating is very old and unsupported. Please try a newer version - 3.3.x, 3.4.x. > a very easily solved documentation problem > -- > > Key: TINKERPOP-2267 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2267 > Project: TinkerPop > Issue Type: Improvement > Components: documentation > Environment: Ubuntu, from within Docker >Reporter: Jeffrey B Brown >Priority: Minor > Original Estimate: 10m > Remaining Estimate: 10m > > This page[1] of the documentation indicates that in order to install the > neo4j plugin for gremlin server, one should run `bin/gremlin-server.sh -i > org.apache.tinkerpop neo4j-gremlin 3.1.0-incubating`. I was unable to run > that until I substituted `install` for `-i`. > [1] https://tinkerpop.apache.org/docs/3.1.0-incubating/#neo4j-gremlin -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (TINKERPOP-2260) Update jackson databind 2.9.9.1
[ https://issues.apache.org/jira/browse/TINKERPOP-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale updated TINKERPOP-2260: --- Labels: security (was: ) > Update jackson databind 2.9.9.1 > --- > > Key: TINKERPOP-2260 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2260 > Project: TinkerPop > Issue Type: Improvement > Components: io >Affects Versions: 3.3.7, 3.4.2 >Reporter: Robert Dale >Assignee: Robert Dale >Priority: Minor > Labels: security > > Vulnerable to deserialization of untrusted data with logback-core or jdom on > the classpath. > Upgrade to 2.9.9.1 or higher. > * https://app.snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-450917 > * https://app.snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-450207 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TINKERPOP-2260) Update jackson databind 2.9.9.1
[ https://issues.apache.org/jira/browse/TINKERPOP-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale updated TINKERPOP-2260: --- Fix Version/s: 3.5.0 3.4.3 3.3.8 > Update jackson databind 2.9.9.1 > --- > > Key: TINKERPOP-2260 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2260 > Project: TinkerPop > Issue Type: Improvement > Components: io >Affects Versions: 3.3.7, 3.4.2 >Reporter: Robert Dale >Assignee: Robert Dale >Priority: Minor > Labels: security > Fix For: 3.3.8, 3.4.3, 3.5.0 > > > Vulnerable to deserialization of untrusted data with logback-core or jdom on > the classpath. > Upgrade to 2.9.9.1 or higher. > * https://app.snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-450917 > * https://app.snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-450207 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (TINKERPOP-2260) Update jackson databind 2.9.9.1
[ https://issues.apache.org/jira/browse/TINKERPOP-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale closed TINKERPOP-2260. -- Resolution: Fixed > Update jackson databind 2.9.9.1 > --- > > Key: TINKERPOP-2260 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2260 > Project: TinkerPop > Issue Type: Improvement > Components: io >Affects Versions: 3.3.7, 3.4.2 >Reporter: Robert Dale >Assignee: Robert Dale >Priority: Minor > Labels: security > Fix For: 3.3.8, 3.4.3, 3.5.0 > > > Vulnerable to deserialization of untrusted data with logback-core or jdom on > the classpath. > Upgrade to 2.9.9.1 or higher. > * https://app.snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-450917 > * https://app.snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-450207 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TINKERPOP-2260) Update jackson databind 2.9.9.1
[
https://issues.apache.org/jira/browse/TINKERPOP-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16881998#comment-16881998
]
Robert Dale commented on TINKERPOP-2260:
Updated via CTR -
[https://github.com/apache/tinkerpop/commit/5e2554816916635118bd825a0fe3146d7ed33cf3]
{{mvn clean install}} success
> Update jackson databind 2.9.9.1
> ---
>
> Key: TINKERPOP-2260
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2260
> Project: TinkerPop
> Issue Type: Improvement
> Components: io
>Affects Versions: 3.3.7, 3.4.2
>Reporter: Robert Dale
>Assignee: Robert Dale
>Priority: Minor
>
> Vulnerable to deserialization of untrusted data with logback-core or jdom on
> the classpath.
> Upgrade to 2.9.9.1 or higher.
> * https://app.snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-450917
> * https://app.snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-450207
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (TINKERPOP-2260) Update jackson databind 2.9.9.1
Robert Dale created TINKERPOP-2260: -- Summary: Update jackson databind 2.9.9.1 Key: TINKERPOP-2260 URL: https://issues.apache.org/jira/browse/TINKERPOP-2260 Project: TinkerPop Issue Type: Improvement Components: io Affects Versions: 3.4.2, 3.3.7 Reporter: Robert Dale Assignee: Robert Dale Vulnerable to deserialization of untrusted data with logback-core or jdom on the classpath. Upgrade to 2.9.9.1 or higher. * https://app.snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-450917 * https://app.snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-450207 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (TINKERPOP-2223) Update jackson databind
Robert Dale created TINKERPOP-2223: -- Summary: Update jackson databind Key: TINKERPOP-2223 URL: https://issues.apache.org/jira/browse/TINKERPOP-2223 Project: TinkerPop Issue Type: Improvement Components: io Affects Versions: 3.4.1, 3.3.6 Reporter: Robert Dale https://app.snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-174736 Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.9.9 or higher. Security vulnerability is specific to having mysql jars on the classpath. Does not affect us directly. Low priority, let's put it on the roadmap. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TINKERPOP-2219) Upgrade Netty version
[ https://issues.apache.org/jira/browse/TINKERPOP-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16841262#comment-16841262 ] Robert Dale commented on TINKERPOP-2219: * [Netty 4.1.36.Final released|https://netty.io/news/2019/04/30/4-1-36-Final.html] on 30-Apr-19 * [Netty 4.1.35.Final released|https://netty.io/news/2019/04/17/4-1-35-Final.html] on 17-Apr-19 * [Netty 4.1.34.Final released|https://netty.io/news/2019/03/08/4-1-34-Final.html] on 08-Mar-19 * [Netty 4.1.33.Final released|https://netty.io/news/2019/01/21/4-1-33-Final.html] on 21-Jan-19 * [Netty 4.1.32.Final released|https://netty.io/news/2018/11/29/4-1-32-Final.html] on 29-Nov-18 > Upgrade Netty version > - > > Key: TINKERPOP-2219 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2219 > Project: TinkerPop > Issue Type: Improvement > Components: driver, server >Affects Versions: 3.3.6, 3.4.1 >Reporter: Divij Vaidya >Priority: Minor > Fix For: 3.3.7, 3.4.2 > > > Please upgrade the Netty version for Tinkerpop. We are currently using a year > old version at 4.1.25-final. > The new versions contain numerous bug fixes and improvements. > My recommendation is to move to at least a 6 month old version (since newer > version might be unstable and have bugs) 4.1.32-final -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TINKERPOP-2219) Upgrade Netty version
[ https://issues.apache.org/jira/browse/TINKERPOP-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16841260#comment-16841260 ] Robert Dale commented on TINKERPOP-2219: I don't quite understand the justification for going to only 4.1.32. So are you saying that .32 is better because at least we know what bugs and security issues exist by way being fixed in .33, .34, .35, .36? > Upgrade Netty version > - > > Key: TINKERPOP-2219 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2219 > Project: TinkerPop > Issue Type: Improvement > Components: driver, server >Affects Versions: 3.3.6, 3.4.1 >Reporter: Divij Vaidya >Priority: Minor > Fix For: 3.3.7, 3.4.2 > > > Please upgrade the Netty version for Tinkerpop. We are currently using a year > old version at 4.1.25-final. > The new versions contain numerous bug fixes and improvements. > My recommendation is to move to at least a 6 month old version (since newer > version might be unstable and have bugs) 4.1.32-final -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TINKERPOP-2219) Upgrade Netty version
[ https://issues.apache.org/jira/browse/TINKERPOP-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16841255#comment-16841255 ] Robert Dale commented on TINKERPOP-2219: https://netty.io/news/2018/11/29/4-1-32-Final.html > Upgrade Netty version > - > > Key: TINKERPOP-2219 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2219 > Project: TinkerPop > Issue Type: Improvement > Components: driver, server >Affects Versions: 3.3.6, 3.4.1 >Reporter: Divij Vaidya >Priority: Minor > Fix For: 3.3.7, 3.4.2 > > > Please upgrade the Netty version for Tinkerpop. We are currently using a year > old version at 4.1.25-final. > The new versions contain numerous bug fixes and improvements. > My recommendation is to move to at least a 6 month old version (since newer > version might be unstable and have bugs) 4.1.32-final -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TINKERPOP-2185) Use commons-configuration2 instead of commns-configuration
[ https://issues.apache.org/jira/browse/TINKERPOP-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16809777#comment-16809777 ] Robert Dale commented on TINKERPOP-2185: [~alexott] Neither one is listed as a vulnerability. So I don't see any need to update to the redhat version. > Use commons-configuration2 instead of commns-configuration > -- > > Key: TINKERPOP-2185 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2185 > Project: TinkerPop > Issue Type: Bug > Components: structure >Affects Versions: 3.3.6, 3.4.1 >Reporter: Alex Ott >Assignee: stephen mallette >Priority: Major > > Product called Whitesource reports vulnerabilities in the > commons-configuration 1.10 that is dependency of the gremlin-core module. As > result, some projects couldn't be allowed to production because of the > failing check. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TINKERPOP-2185) Use commons-configuration2 instead of commns-configuration
[ https://issues.apache.org/jira/browse/TINKERPOP-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16809001#comment-16809001 ] Robert Dale commented on TINKERPOP-2185: [~alexott] do you have a link to a vulnerability report? > Use commons-configuration2 instead of commns-configuration > -- > > Key: TINKERPOP-2185 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2185 > Project: TinkerPop > Issue Type: Bug > Components: structure >Affects Versions: 3.3.6, 3.4.1 >Reporter: Alex Ott >Assignee: stephen mallette >Priority: Major > > Product called Whitesource reports vulnerabilities in the > commons-configuration 1.10 that is dependency of the gremlin-core module. As > result, some projects couldn't be allowed to production because of the > failing check. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (TINKERPOP-2174) Improve Docker Image Security
Robert Dale created TINKERPOP-2174: -- Summary: Improve Docker Image Security Key: TINKERPOP-2174 URL: https://issues.apache.org/jira/browse/TINKERPOP-2174 Project: TinkerPop Issue Type: Improvement Components: console, server Affects Versions: 3.3.5, 3.4.0 Reporter: Robert Dale Assignee: Robert Dale - use least privileged user - use the dynamic tag to get the latest image: openjdk:8-jre-alpine -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TINKERPOP-2076) TinkerPop does not build with current (v11) Java version
[
https://issues.apache.org/jira/browse/TINKERPOP-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16787838#comment-16787838
]
Robert Dale commented on TINKERPOP-2076:
I didn't read it thoroughly. I saw the {{module java9unsafe {...}} solution in
the desc. Looks like it turned out that it wasn't that simple.
> TinkerPop does not build with current (v11) Java version
>
>
> Key: TINKERPOP-2076
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2076
> Project: TinkerPop
> Issue Type: Improvement
> Components: build-release
>Affects Versions: 3.3.4
> Environment: $ java --version
> java 11 2018-09-25
> Java(TM) SE Runtime Environment 18.9 (build 11+28)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11+28, mixed mode)
>Reporter: Steve Strassmann
>Assignee: stephen mallette
>Priority: Major
>
> I cannot build TinkerPop with a current (v11) Java version.
> On the gremlin-users Google group, Robert Dale suggests using Java 8, but
> that is deprecated. Recommended: support current Java versions. Stephen
> Mallette says "we need to start worrying about such things."
> Oracle [says Java 8 is
> deprecated|https://www.oracle.com/technetwork/java/javase/overview/index.html]:
> {quote}{color:#d04437}[End of Public Updates for Oracle JDK
> 8|https://www.oracle.com/technetwork/java/javase/eol-135779.html]{color}
> Oracle will not post further updates of Java SE 8 to its public download
> sites for commercial use after January 2019.
> {quote}
>
> See issue posted in Gremlin-users Google Group:
>
> [https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/gremlin-users/Kgnq4BkrZXQ]
> {{unable to build Tinkerpop from master with mvn clean install. }}
>
> The error appears to be
> An API incompatibility was encountered while executing
> org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce:
> java.lang.ExceptionInInitializerError: null
> {code:java}
> $ git clone https://github.com/apache/tinkerpop.git
> $ git checkout master
> $ mvn --version
> Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
> 2018-06-17T14:33:14-04:00)
> Maven home: /opt/maven
> Java version: 11, vendor: Oracle Corporation, runtime:
> /Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.13.6", arch: "x86_64", family: "mac"
> {code}
>
>
> {code:java}
> $ mvn clean install
> [INFO] Scanning for projects...
> [WARNING] The project org.apache.tinkerpop:tinkerpop:pom:3.4.0-SNAPSHOT uses
> prerequisites which is only intended for maven-plugin projects but not for
> non maven-plugin projects. For such purposes you should use the
> maven-enforcer-plugin. See
> https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] Apache TinkerPop
> [pom]
> [INFO] Apache TinkerPop :: Gremlin Shaded
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Core
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Test
> [jar]
> [INFO] Apache TinkerPop :: TinkerGraph Gremlin
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Groovy
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Driver
> [jar]
> [INFO] Apache TinkerPop :: Neo4j Gremlin
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Server
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Javascript
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Python
> [jar]
> [INFO] Apache TinkerPop :: Gremlin.Net
> [pom]
> [INFO] Apache TinkerPop :: Gremlin.Net - Source
> [pom]
> [INFO] Apache TinkerPop :: Gremlin.Net - Tests
> [pom]
> [INFO] Apache TinkerPop :: Hadoop Gremlin
> [jar]
> [INFO] Apache TinkerPop :: Spark Gremlin
> [jar]
> [INFO] Apache TinkerPop :: SPARQL Gremlin
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Console
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Archetype
> [pom]
> [INFO] Apache TinkerPop :: Archetype - TinkerGraph
> [jar]
> [INFO] Apache TinkerPop :: Archetype - Server
> [jar]
> [INFO] Apache TinkerPop :: A
[jira] [Commented] (TINKERPOP-2076) TinkerPop does not build with current (v11) Java version
[
https://issues.apache.org/jira/browse/TINKERPOP-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16787203#comment-16787203
]
Robert Dale commented on TINKERPOP-2076:
Did you try the workaround in https://issues.apache.org/jira/browse/SPARK-24421
?
> TinkerPop does not build with current (v11) Java version
>
>
> Key: TINKERPOP-2076
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2076
> Project: TinkerPop
> Issue Type: Improvement
> Components: build-release
>Affects Versions: 3.3.4
> Environment: $ java --version
> java 11 2018-09-25
> Java(TM) SE Runtime Environment 18.9 (build 11+28)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11+28, mixed mode)
>Reporter: Steve Strassmann
>Assignee: stephen mallette
>Priority: Major
>
> I cannot build TinkerPop with a current (v11) Java version.
> On the gremlin-users Google group, Robert Dale suggests using Java 8, but
> that is deprecated. Recommended: support current Java versions. Stephen
> Mallette says "we need to start worrying about such things."
> Oracle [says Java 8 is
> deprecated|https://www.oracle.com/technetwork/java/javase/overview/index.html]:
> {quote}{color:#d04437}[End of Public Updates for Oracle JDK
> 8|https://www.oracle.com/technetwork/java/javase/eol-135779.html]{color}
> Oracle will not post further updates of Java SE 8 to its public download
> sites for commercial use after January 2019.
> {quote}
>
> See issue posted in Gremlin-users Google Group:
>
> [https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/gremlin-users/Kgnq4BkrZXQ]
> {{unable to build Tinkerpop from master with mvn clean install. }}
>
> The error appears to be
> An API incompatibility was encountered while executing
> org.apache.maven.plugins:maven-enforcer-plugin:1.4.1:enforce:
> java.lang.ExceptionInInitializerError: null
> {code:java}
> $ git clone https://github.com/apache/tinkerpop.git
> $ git checkout master
> $ mvn --version
> Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
> 2018-06-17T14:33:14-04:00)
> Maven home: /opt/maven
> Java version: 11, vendor: Oracle Corporation, runtime:
> /Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.13.6", arch: "x86_64", family: "mac"
> {code}
>
>
> {code:java}
> $ mvn clean install
> [INFO] Scanning for projects...
> [WARNING] The project org.apache.tinkerpop:tinkerpop:pom:3.4.0-SNAPSHOT uses
> prerequisites which is only intended for maven-plugin projects but not for
> non maven-plugin projects. For such purposes you should use the
> maven-enforcer-plugin. See
> https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] Apache TinkerPop
> [pom]
> [INFO] Apache TinkerPop :: Gremlin Shaded
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Core
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Test
> [jar]
> [INFO] Apache TinkerPop :: TinkerGraph Gremlin
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Groovy
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Driver
> [jar]
> [INFO] Apache TinkerPop :: Neo4j Gremlin
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Server
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Javascript
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Python
> [jar]
> [INFO] Apache TinkerPop :: Gremlin.Net
> [pom]
> [INFO] Apache TinkerPop :: Gremlin.Net - Source
> [pom]
> [INFO] Apache TinkerPop :: Gremlin.Net - Tests
> [pom]
> [INFO] Apache TinkerPop :: Hadoop Gremlin
> [jar]
> [INFO] Apache TinkerPop :: Spark Gremlin
> [jar]
> [INFO] Apache TinkerPop :: SPARQL Gremlin
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Console
> [jar]
> [INFO] Apache TinkerPop :: Gremlin Archetype
> [pom]
> [INFO] Apache TinkerPop :: Archetype - TinkerGraph
> [jar]
> [INFO] Apache TinkerPop :: Archetype - Server
> [jar]
> [INFO] Apache TinkerPop :: Archetype - DSL
> [jar]
> [IN
[jira] [Commented] (TINKERPOP-2170) Compare.eq doesn't produce consistent results
[
https://issues.apache.org/jira/browse/TINKERPOP-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16778050#comment-16778050
]
Robert Dale commented on TINKERPOP-2170:
Just to be clear, I'm saying that this is not a bug but user error.
> Compare.eq doesn't produce consistent results
> -
>
> Key: TINKERPOP-2170
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2170
> Project: TinkerPop
> Issue Type: Bug
> Components: process
>Affects Versions: 3.3.4
>Reporter: Daniel Choi
>Assignee: Daniel Kuppitz
>Priority: Major
>
> https://issues.apache.org/jira/browse/TINKERPOP-2056 introduced a change to
> start using NumberHelper for comparisons.
>
> This seems to have introduced an interesting side effect:
> {code:java}
> Assert.assertTrue(Compare.eq.test(new Double(1.53), new Float(1.53)));
> {code}
> now fails in 3.3.4+ versions. Interestingly,
> {code:java}
> Assert.assertTrue(Compare.eq.test(new Double(1.5), new Float(1.5)));
> {code}
> works fine. It seems the problem is coming from the fact that the
> NumberHelper.DOUBLE_NUMBER_HELPER is chosen for the comparison of float and
> double numbers, where
> {code:java}
> new Float(1.53).doubleValue();
> => 1.529713897705
> new Double(1.53).doubleValue();
> => 1.53{code}
> Not sure what the correct implementation here would be, but nonetheless this
> seems to be a backwards incompatible change.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (TINKERPOP-2170) Compare.eq doesn't produce consistent results
[
https://issues.apache.org/jira/browse/TINKERPOP-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16778027#comment-16778027
]
Robert Dale commented on TINKERPOP-2170:
In general, equality between floats and/or doubles should not be relied upon
regardless of language. At best, between(x-tolerance,x+tolerance) should be
used.
[https://randomascii.wordpress.com/2012/02/25/comparing-floating-point-numbers-2012-edition/]
[https://randomascii.wordpress.com/2012/06/26/doubles-are-not-floats-so-dont-compare-them/]
> Compare.eq doesn't produce consistent results
> -
>
> Key: TINKERPOP-2170
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2170
> Project: TinkerPop
> Issue Type: Bug
> Components: process
>Affects Versions: 3.3.4
>Reporter: Daniel Choi
>Assignee: Daniel Kuppitz
>Priority: Major
>
> https://issues.apache.org/jira/browse/TINKERPOP-2056 introduced a change to
> start using NumberHelper for comparisons.
>
> This seems to have introduced an interesting side effect:
> {code:java}
> Assert.assertTrue(Compare.eq.test(new Double(1.53), new Float(1.53)));
> {code}
> now fails in 3.3.4+ versions. Interestingly,
> {code:java}
> Assert.assertTrue(Compare.eq.test(new Double(1.5), new Float(1.5)));
> {code}
> works fine. It seems the problem is coming from the fact that the
> NumberHelper.DOUBLE_NUMBER_HELPER is chosen for the comparison of float and
> double numbers, where
> {code:java}
> new Float(1.53).doubleValue();
> => 1.529713897705
> new Double(1.53).doubleValue();
> => 1.53{code}
> Not sure what the correct implementation here would be, but nonetheless this
> seems to be a backwards incompatible change.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (TINKERPOP-2121) Bump Jackson Databind 2.9.8
[ https://issues.apache.org/jira/browse/TINKERPOP-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale reassigned TINKERPOP-2121: -- Assignee: Robert Dale > Bump Jackson Databind 2.9.8 > --- > > Key: TINKERPOP-2121 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2121 > Project: TinkerPop > Issue Type: Improvement > Components: io >Affects Versions: 3.4.0, 3.3.4, 3.2.10 >Reporter: Robert Dale >Assignee: Robert Dale >Priority: Major > Labels: security > Fix For: 3.4.0, 3.3.5, 3.2.11 > > > > Fixes: CVE-2018-19360, CVE-2018-19361, CVE-2018-19362, CVE-2018-1000873 > Release notes: > [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.9.8] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (TINKERPOP-2121) Bump Jackson Databind 2.9.8
[ https://issues.apache.org/jira/browse/TINKERPOP-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale closed TINKERPOP-2121. -- Resolution: Fixed > Bump Jackson Databind 2.9.8 > --- > > Key: TINKERPOP-2121 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2121 > Project: TinkerPop > Issue Type: Improvement > Components: io >Affects Versions: 3.4.0, 3.3.4, 3.2.10 >Reporter: Robert Dale >Assignee: Robert Dale >Priority: Major > Labels: security > Fix For: 3.4.0, 3.3.5, 3.2.11 > > > > Fixes: CVE-2018-19360, CVE-2018-19361, CVE-2018-19362, CVE-2018-1000873 > Release notes: > [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.9.8] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TINKERPOP-2121) Bump Jackson Databind 2.9.8
[ https://issues.apache.org/jira/browse/TINKERPOP-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale updated TINKERPOP-2121: --- Fix Version/s: 3.2.11 3.3.5 3.4.0 > Bump Jackson Databind 2.9.8 > --- > > Key: TINKERPOP-2121 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2121 > Project: TinkerPop > Issue Type: Improvement > Components: io >Affects Versions: 3.4.0, 3.3.4, 3.2.10 >Reporter: Robert Dale >Priority: Major > Labels: security > Fix For: 3.4.0, 3.3.5, 3.2.11 > > > > Fixes: CVE-2018-19360, CVE-2018-19361, CVE-2018-19362, CVE-2018-1000873 > Release notes: > [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.9.8] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (TINKERPOP-2121) Bump Jackson Databind 2.9.8
Robert Dale created TINKERPOP-2121: -- Summary: Bump Jackson Databind 2.9.8 Key: TINKERPOP-2121 URL: https://issues.apache.org/jira/browse/TINKERPOP-2121 Project: TinkerPop Issue Type: Improvement Reporter: Robert Dale -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TINKERPOP-2121) Bump Jackson Databind 2.9.8
[ https://issues.apache.org/jira/browse/TINKERPOP-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale updated TINKERPOP-2121: --- Labels: security (was: ) > Bump Jackson Databind 2.9.8 > --- > > Key: TINKERPOP-2121 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2121 > Project: TinkerPop > Issue Type: Improvement > Components: io >Affects Versions: 3.4.0, 3.3.4, 3.2.10 >Reporter: Robert Dale >Priority: Major > Labels: security > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TINKERPOP-2121) Bump Jackson Databind 2.9.8
[ https://issues.apache.org/jira/browse/TINKERPOP-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale updated TINKERPOP-2121: --- Description: Fixes: CVE-2018-19360, CVE-2018-19361, CVE-2018-19362, CVE-2018-1000873 Release notes: [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.9.8] > Bump Jackson Databind 2.9.8 > --- > > Key: TINKERPOP-2121 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2121 > Project: TinkerPop > Issue Type: Improvement > Components: io >Affects Versions: 3.4.0, 3.3.4, 3.2.10 >Reporter: Robert Dale >Priority: Major > Labels: security > > > Fixes: CVE-2018-19360, CVE-2018-19361, CVE-2018-19362, CVE-2018-1000873 > Release notes: > [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.9.8] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TINKERPOP-2121) Bump Jackson Databind 2.9.8
[ https://issues.apache.org/jira/browse/TINKERPOP-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale updated TINKERPOP-2121: --- Component/s: io > Bump Jackson Databind 2.9.8 > --- > > Key: TINKERPOP-2121 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2121 > Project: TinkerPop > Issue Type: Improvement > Components: io >Affects Versions: 3.4.0, 3.3.4, 3.2.10 >Reporter: Robert Dale >Priority: Major > Labels: security > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TINKERPOP-2121) Bump Jackson Databind 2.9.8
[ https://issues.apache.org/jira/browse/TINKERPOP-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale updated TINKERPOP-2121: --- Affects Version/s: 3.4.0 3.3.4 3.2.10 > Bump Jackson Databind 2.9.8 > --- > > Key: TINKERPOP-2121 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2121 > Project: TinkerPop > Issue Type: Improvement > Components: io >Affects Versions: 3.4.0, 3.3.4, 3.2.10 >Reporter: Robert Dale >Priority: Major > Labels: security > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TINKERPOP-2098) gremlin-server.sh start does not seem to work as advertised
[
https://issues.apache.org/jira/browse/TINKERPOP-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16696206#comment-16696206
]
Robert Dale commented on TINKERPOP-2098:
The options are in a somewhat common command-line help format.
{noformat}
{start|stop|restart|status|console|install |}{noformat}
reads as:
'start'
or 'stop'
or 'restart'
or 'status'
or 'console'
or 'install' with required, placeholder parameters 'group', 'artifact',
'version'
or placeholder 'conf file'
Using this format, if having 'conf file' were an option for 'start', it would
have displayed
{noformat}
{start [conf file] | stop | }
{noformat}
*What would you suggest to make it more clear?*
It would also be great if you could pinpoint places in the docs where it's
confusing. I couldn't find any instances where 'start' and 'conf file' were
intermixed or implied one could be used with the other.
The first mention of starting Gremlin Server shows correct usage.
* [http://tinkerpop.apache.org/docs/current/reference/#starting-gremlin-server]
Configuring describes each parameter and how to configure the env vars.
* [http://tinkerpop.apache.org/docs/current/reference/#_configuring_2]
Just reading through that with your requirements in mind. If I want to run in
the background, then I must use 'start' since it 'Start[s] the server in the
background'. I can't use parameter 'conf file' because it starts in the
foreground. If I want to override the default 'conf/gremlin-server.yaml', then
I must "set GREMLIN_YAML in bin/gemlin-server.conf".
*What would you suggest to make it more clear?*
> gremlin-server.sh start does not seem to work as advertised
> ---
>
> Key: TINKERPOP-2098
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2098
> Project: TinkerPop
> Issue Type: Improvement
> Components: server
>Affects Versions: 3.3.4
>Reporter: Kelvin R. Lawrence
>Priority: Minor
>
> This may be as simple as a documentation issue but the help text for Gremlin
> server implies that I should be able to do:
> {code:java}
> gremlin-server.sh start conf/myyaml.yaml{code}
> However when I do that it does not seem to actually be reading my YAML file
> or if it is it is not reading it fully as I am specifying the WsAndHttp
> channelizer in the YAML and when the server starts the HTTP endpoint is not
> available.
>
> If I start the server in the terminal with
>
> {code:java}
> gremlin-server.sh conf/myyaml.yaml{code}
>
> all is fine but I want to start it in the background.
>
> I spoke to [~pluradj] and he had me try using the environment variable to
> specify the YAML file name and that worked with the *start* keyword.
>
> Is *gremlin-server.sh start conf/myyaml.yam*l supposed to work?
>
> If not it would be good to change the help text for gremlin-server.sh which
> currently reads as follows:
>
>
> {code:java}
> Usage: bin/gremlin-server.sh {start|stop|restart|status|console|install
> |}{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (TINKERPOP-2086) Publish docs port for docker/build.sh -d
[
https://issues.apache.org/jira/browse/TINKERPOP-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16673024#comment-16673024
]
Robert Dale commented on TINKERPOP-2086:
I don't seem to have this problem. I run {{docker/build.sh -d}} and then go to
the URL presented and it just works. Maybe it has to do with your docker
environment?
> Publish docs port for docker/build.sh -d
>
>
> Key: TINKERPOP-2086
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2086
> Project: TinkerPop
> Issue Type: Improvement
> Components: build-release
>Affects Versions: 3.2.10
>Reporter: Florian Hockmann
>Priority: Minor
>
> The easiest way to generate our docs is by using Docker via
> {{./docker/build.sh -d}} which generates the docs. However, to actually
> verify that changes to the docs look as expected, one has to manually inspect
> the generated docs.
> We could simply publish port 80 (maybe to another port like 8080) to make the
> docs accessible on the host for manual inspection.
> A workaround is currently to start another container that exposes the port
> and relays to the TinkerPop container with socat:
> {code}
> docker run -p 8080:80 --link [tinkerpop_container]:target alpine/socat
> tcp-listen:80,fork,reuseaddr tcp-connect:target:80{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (TINKERPOP-2068) Bump Jackson Databind 2.9.7
[ https://issues.apache.org/jira/browse/TINKERPOP-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale updated TINKERPOP-2068: --- Description: Jackson Databind vulnerability flagged by: * https://app.snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-72451 * [https://app.snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-72449] * [https://app.snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-72450] * https://app.snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-72448 Jackson Databind Release Notes: [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.9.7] was:Jackson Databind vulnerabily: https://cwe.mitre.org/data/definitions/502.html > Bump Jackson Databind 2.9.7 > --- > > Key: TINKERPOP-2068 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2068 > Project: TinkerPop > Issue Type: Improvement > Components: io >Affects Versions: 3.3.4, 3.2.10 >Reporter: Robert Dale >Assignee: Robert Dale >Priority: Major > Labels: security > > Jackson Databind vulnerability flagged by: > * https://app.snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-72451 > * [https://app.snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-72449] > * [https://app.snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-72450] > * https://app.snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-72448 > Jackson Databind Release Notes: > [https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.9.7] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TINKERPOP-2078) Hide use of EmptyGraph or RemoteGraph behind a more unified method for TraversalSource construction
[
https://issues.apache.org/jira/browse/TINKERPOP-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16663682#comment-16663682
]
Robert Dale commented on TINKERPOP-2078:
Looks good. (y)
> Hide use of EmptyGraph or RemoteGraph behind a more unified method for
> TraversalSource construction
> ---
>
> Key: TINKERPOP-2078
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2078
> Project: TinkerPop
> Issue Type: Improvement
> Components: structure
>Affects Versions: 3.3.4
>Reporter: stephen mallette
>Assignee: stephen mallette
>Priority: Major
>
> {{RemoteGraph}} was long ago deprecated for {{withRemote()}} typically
> spawned from {{EmptyGraph}} which is weird. For GLVs, make sure
> {{EmptyGraph}} didn't leak into them and deal with those issues as needed.
> Update all docs to stop using {{EmptyGraph}}. Provide a way to unify
> {{TraversalSource}} construction for both local and remote connected graphs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (TINKERPOP-2068) Bump Jackson Databind 2.9.7
Robert Dale created TINKERPOP-2068: -- Summary: Bump Jackson Databind 2.9.7 Key: TINKERPOP-2068 URL: https://issues.apache.org/jira/browse/TINKERPOP-2068 Project: TinkerPop Issue Type: Improvement Components: io Affects Versions: 3.3.4, 3.2.10 Reporter: Robert Dale Assignee: Robert Dale Jackson Databind vulnerabily: https://cwe.mitre.org/data/definitions/502.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (TINKERPOP-2037) Remove unused groovy-sql dependency
[ https://issues.apache.org/jira/browse/TINKERPOP-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale closed TINKERPOP-2037. -- Resolution: Fixed > Remove unused groovy-sql dependency > --- > > Key: TINKERPOP-2037 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2037 > Project: TinkerPop > Issue Type: Improvement > Components: driver >Reporter: Robert Dale >Assignee: Robert Dale >Priority: Trivial > Fix For: 3.4.0 > > > See thread - > https://lists.apache.org/thread.html/da6008600e76d828f435cba7d4f7d9c0334e45e854dab8a9ad967232@%3Cdev.tinkerpop.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TINKERPOP-2051) Uniqueness of property ids
[ https://issues.apache.org/jira/browse/TINKERPOP-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16631836#comment-16631836 ] Robert Dale commented on TINKERPOP-2051: Just want to clarify scope here. We originally discussed TinkerGraph. Is the current thought that this is a graph implementation requirement? I ask because the ticket has component `structure` and [~spmallette]'s comment applies to providers and users. So I'm a little fuzzy on if this is only a TinkerGraph issue and/or Graph Provider issue. I don't see a mention of any - vertex, edge, vertex property, etc - ID requirements on the [Provider Docs|http://tinkerpop.apache.org/docs/3.3.3/dev/provider/#_provider_documentation] or [Reference Docs|http://tinkerpop.apache.org/docs/3.3.3/reference/]. These should probably be improved to include the importance of unique IDs in any case. > Uniqueness of property ids > -- > > Key: TINKERPOP-2051 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2051 > Project: TinkerPop > Issue Type: Bug > Components: structure >Affects Versions: 3.2.9 >Reporter: Daniel Kuppitz >Priority: Major > Labels: breaking > > Right now we don't ensure property id uniqueness. As shown in [this > discussion|https://lists.apache.org/thread.html/e28d61e1f3b674b617765a0f28174d45691db0812e7c56761d1456c3@%3Cdev.tinkerpop.apache.org%3E], > this can lead to very odd results, hence I marked this ticket as a Bug. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TINKERPOP-2045) Remove non-indy groovy dependencies
[ https://issues.apache.org/jira/browse/TINKERPOP-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale updated TINKERPOP-2045: --- Component/s: (was: server) (was: console) groovy > Remove non-indy groovy dependencies > --- > > Key: TINKERPOP-2045 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2045 > Project: TinkerPop > Issue Type: Improvement > Components: driver, groovy >Affects Versions: 3.3.3, 3.2.9 >Reporter: Robert Dale >Assignee: Robert Dale >Priority: Minor > > Console and Server include conflicting core groovy dependencies of indy and > non-indy jars. Depending on the shell's sort order, the user may or may not > get the invokedynamic improvement. > See also > [DISCUSS|https://lists.apache.org/thread.html/de2c6dcfcc26fcfea6ce787d79f51f473390b24c74dbbff203fec67b@%3Cdev.tinkerpop.apache.org%3E] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (TINKERPOP-2045) Remove non-indy groovy dependencies
Robert Dale created TINKERPOP-2045: -- Summary: Remove non-indy groovy dependencies Key: TINKERPOP-2045 URL: https://issues.apache.org/jira/browse/TINKERPOP-2045 Project: TinkerPop Issue Type: Improvement Components: console, driver, server Affects Versions: 3.2.9, 3.3.3 Reporter: Robert Dale Assignee: Robert Dale Console and Server include conflicting core groovy dependencies of indy and non-indy jars. Depending on the shell's sort order, the user may or may not get the invokedynamic improvement. See also [DISCUSS|https://lists.apache.org/thread.html/de2c6dcfcc26fcfea6ce787d79f51f473390b24c74dbbff203fec67b@%3Cdev.tinkerpop.apache.org%3E] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TINKERPOP-2044) Cannot reconnect to Azure cosmos host that becomes available again
[ https://issues.apache.org/jira/browse/TINKERPOP-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626638#comment-16626638 ] Robert Dale commented on TINKERPOP-2044: My first reaction is to make this a user configurable query like in so many jdbc drivers. I wonder if there's something more appropriate or clever. > Cannot reconnect to Azure cosmos host that becomes available again > -- > > Key: TINKERPOP-2044 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2044 > Project: TinkerPop > Issue Type: Bug > Components: driver >Affects Versions: 3.3.3 >Reporter: Dantis P S >Priority: Major > > If a Azure Cosmos Gremlin host goes down and if it becomes available again, > the tinkerpop3 java driver cannot reconnect to it. > Sample code is available at [https://github.com/cancure/tinkerpopcosmos] > > These are the steps to reproduce - > 1) Start the application after providing proper connection details in > remote.yaml file. > 2) Call the end point POST [http://localhost:8080/query.] Pass a valid > gremlin query as HTTP body E.g. g.V(1).id() > 3) Disconnect computer from internet. > 4) Do step 2. > 5) Reconnect computer to the internet. > 6) Do step 2. > Any query executed from this point onwards gets the error - > "java.lang.RuntimeException: java.util.concurrent.TimeoutException: Timed out > while waiting for an available host - check the client configuration and > connectivity to the server if this message persists". > > The issue seems to be coming from > org.apache.tinkerpop.gremlin.driver.ConnectionPool.java. In line #403, the > gremlin query used for ping message is '' (Empty string in single quotes). > final RequestMessage ping = > RequestMessage.build(Tokens.OPS_EVAL).add(Tokens.ARGS_GREMLIN, "''").create(); > > Cosmos server returns an error saying that the gremlin query's grammar is > incorrect. Because of this error the rest of the lines of the method does not > get executed. > > Fix will be to use a gremlin query which is valid for all supported graph DBs. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TINKERPOP-2030) KeepAlive task executed for every Connection.write call
[
https://issues.apache.org/jira/browse/TINKERPOP-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16624397#comment-16624397
]
Robert Dale commented on TINKERPOP-2030:
LGTM
> KeepAlive task executed for every Connection.write call
> ---
>
> Key: TINKERPOP-2030
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2030
> Project: TinkerPop
> Issue Type: Bug
> Components: driver
>Affects Versions: 3.3.2
>Reporter: Simone Rondelli
>Assignee: stephen mallette
>Priority: Major
>
> The Gremlin Driver communicates with the server via {{Connection.write()}}.
> The {{write()}} method has a logic in the end to schedule a task to keep the
> connection alive, which by default is scheduled to be run after 30min, every
> 30 min.
> {code:java}
> // try to keep the connection alive if the channel allows such things -
> websockets will
> if (channelizer.supportsKeepAlive() && keepAliveInterval > 0) {
> final ScheduledFuture oldKeepAliveFuture =
> keepAliveFuture.getAndSet(cluster.executor().scheduleAtFixedRate(() -> {
> logger.debug("Request sent to server to keep {} alive",
> thisConnection);
> try {
>
> channel.writeAndFlush(channelizer.createKeepAliveMessage());
> } catch (Exception ex) {
> // will just log this for now - a future real request can
> be responsible for the failure that
> // marks the host as dead. this also may not mean the
> host is actually dead. more robust handling
> // is in play for real requests, not this simple ping
> logger.warn(String.format("Keep-alive did not succeed on
> %s", thisConnection), ex);
> }
> }, keepAliveInterval, keepAliveInterval, TimeUnit.MILLISECONDS));
> // try to cancel the old future if it's still un-executed - no
> need to ping since a new write has come
> // through on the connection
> if (oldKeepAliveFuture != null) oldKeepAliveFuture.cancel(true);
> }
> {code}
> The problem with this is that on every call of the {{wirte()}} method, which
> basically means on every query executed, the {[Connection}} schedule a
> KeepAlive task which won't be run for at least 30 minutes. This lead the
> {{Cluster.executor()}} queue to fill up with tasks waiting for completion.
> One possible solution to fix this would be to schedule avoid this KeepAlive
> task to be instantiated more than once per connection:
> {code:java}
> final class Connection {
> ...
> private final AtomicBoolean keepAliveInitialized = new
> AtomicBoolean(false);
> public ChannelPromise write(final RequestMessage requestMessage, final
> CompletableFuture future) {
> ...
>
> // FIX HERE: with keepAliveInitialized.compareAndSet(false, true) we
> ensure the keepAlive task is run only once per connection.
> if (channelizer.supportsKeepAlive() && keepAliveInterval > 0 &&
> keepAliveInitialized.compareAndSet(false, true)) {
> ...
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (TINKERPOP-2032) Update jython-standalone
[ https://issues.apache.org/jira/browse/TINKERPOP-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale closed TINKERPOP-2032. -- Resolution: Fixed > Update jython-standalone > > > Key: TINKERPOP-2032 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2032 > Project: TinkerPop > Issue Type: Bug > Components: python >Affects Versions: 3.3.3, 3.2.9 >Reporter: Robert Dale >Assignee: Robert Dale >Priority: Major > Fix For: 3.4.0, 3.3.4, 3.2.10 > > > [https://snyk.io/vuln/SNYK-JAVA-ORGPYTHON-31451] > Overview > org.python:jython-standalone Affected versions of this package are > vulnerable to Arbitrary Code Execution by sending a serialized function to > the deserializer, which in turn will execute the code. > References > [ CVE|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4000] > [Jython Bug Report|http://bugs.jython.org/issue2454] > [ Fix Commit|https://hg.python.org/jython/rev/d06e29d100c0] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TINKERPOP-2032) Update jython-standalone
[ https://issues.apache.org/jira/browse/TINKERPOP-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale updated TINKERPOP-2032: --- Fix Version/s: 3.2.10 3.3.4 3.4.0 > Update jython-standalone > > > Key: TINKERPOP-2032 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2032 > Project: TinkerPop > Issue Type: Bug > Components: python >Affects Versions: 3.3.3, 3.2.9 >Reporter: Robert Dale >Assignee: Robert Dale >Priority: Major > Fix For: 3.4.0, 3.3.4, 3.2.10 > > > [https://snyk.io/vuln/SNYK-JAVA-ORGPYTHON-31451] > Overview > org.python:jython-standalone Affected versions of this package are > vulnerable to Arbitrary Code Execution by sending a serialized function to > the deserializer, which in turn will execute the code. > References > [ CVE|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4000] > [Jython Bug Report|http://bugs.jython.org/issue2454] > [ Fix Commit|https://hg.python.org/jython/rev/d06e29d100c0] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (TINKERPOP-2038) Make groovy script cache size configurable
Robert Dale created TINKERPOP-2038: -- Summary: Make groovy script cache size configurable Key: TINKERPOP-2038 URL: https://issues.apache.org/jira/browse/TINKERPOP-2038 Project: TinkerPop Issue Type: Improvement Components: groovy Affects Versions: 3.2.9 Reporter: Robert Dale See [thread|https://groups.google.com/d/msg/gremlin-users/fm6Og2i1uXw/0J3F309IBAAJ] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (TINKERPOP-2037) Remove unused groovy-sql dependency
Robert Dale created TINKERPOP-2037: -- Summary: Remove unused groovy-sql dependency Key: TINKERPOP-2037 URL: https://issues.apache.org/jira/browse/TINKERPOP-2037 Project: TinkerPop Issue Type: Improvement Components: driver Reporter: Robert Dale Assignee: Robert Dale Fix For: 3.4.0 See thread - https://lists.apache.org/thread.html/da6008600e76d828f435cba7d4f7d9c0334e45e854dab8a9ad967232@%3Cdev.tinkerpop.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (TINKERPOP-2032) Update jython-standalone
Robert Dale created TINKERPOP-2032: -- Summary: Update jython-standalone Key: TINKERPOP-2032 URL: https://issues.apache.org/jira/browse/TINKERPOP-2032 Project: TinkerPop Issue Type: Bug Components: python Affects Versions: 3.2.9, 3.3.3 Reporter: Robert Dale Assignee: Robert Dale [https://snyk.io/vuln/SNYK-JAVA-ORGPYTHON-31451] Overview org.python:jython-standalone Affected versions of this package are vulnerable to Arbitrary Code Execution by sending a serialized function to the deserializer, which in turn will execute the code. References [ CVE|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4000] [Jython Bug Report|http://bugs.jython.org/issue2454] [ Fix Commit|https://hg.python.org/jython/rev/d06e29d100c0] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (TINKERPOP-2023) Gremlin Server should not create self-signed certs
[ https://issues.apache.org/jira/browse/TINKERPOP-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale resolved TINKERPOP-2023. Resolution: Fixed > Gremlin Server should not create self-signed certs > -- > > Key: TINKERPOP-2023 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2023 > Project: TinkerPop > Issue Type: Improvement > Components: server >Affects Versions: 3.2.9 >Reporter: Robert Dale >Assignee: Robert Dale >Priority: Minor > Labels: breaking, deprecation > Fix For: 3.4.0, 3.3.4, 3.2.10 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (TINKERPOP-2023) Gremlin Server should not create self-signed certs
[ https://issues.apache.org/jira/browse/TINKERPOP-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale closed TINKERPOP-2023. -- > Gremlin Server should not create self-signed certs > -- > > Key: TINKERPOP-2023 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2023 > Project: TinkerPop > Issue Type: Improvement > Components: server >Affects Versions: 3.2.9 >Reporter: Robert Dale >Assignee: Robert Dale >Priority: Minor > Labels: breaking, deprecation > Fix For: 3.4.0, 3.3.4, 3.2.10 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TINKERPOP-2023) Gremlin Server should not create self-signed certs
[ https://issues.apache.org/jira/browse/TINKERPOP-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale updated TINKERPOP-2023: --- Labels: breaking deprecation (was: breaking deprecation security) > Gremlin Server should not create self-signed certs > -- > > Key: TINKERPOP-2023 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2023 > Project: TinkerPop > Issue Type: Improvement > Components: server >Affects Versions: 3.2.9 >Reporter: Robert Dale >Assignee: Robert Dale >Priority: Minor > Labels: breaking, deprecation > Fix For: 3.4.0, 3.3.4, 3.2.10 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (TINKERPOP-2023) Gremlin Server should not create self-signed certs
[ https://issues.apache.org/jira/browse/TINKERPOP-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale reopened TINKERPOP-2023: > Gremlin Server should not create self-signed certs > -- > > Key: TINKERPOP-2023 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2023 > Project: TinkerPop > Issue Type: Improvement > Components: server >Affects Versions: 3.2.9 >Reporter: Robert Dale >Assignee: Robert Dale >Priority: Minor > Labels: breaking, deprecation > Fix For: 3.4.0, 3.3.4, 3.2.10 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TINKERPOP-2023) Gremlin Server should not create self-signed certs
[ https://issues.apache.org/jira/browse/TINKERPOP-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale updated TINKERPOP-2023: --- Fix Version/s: 3.2.10 3.3.4 3.4.0 > Gremlin Server should not create self-signed certs > -- > > Key: TINKERPOP-2023 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2023 > Project: TinkerPop > Issue Type: Improvement > Components: server >Affects Versions: 3.2.9 >Reporter: Robert Dale >Assignee: Robert Dale >Priority: Minor > Labels: breaking, deprecation, security > Fix For: 3.4.0, 3.3.4, 3.2.10 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (TINKERPOP-2023) Gremlin Server should not create self-signed certs
[ https://issues.apache.org/jira/browse/TINKERPOP-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale closed TINKERPOP-2023. -- Resolution: Fixed > Gremlin Server should not create self-signed certs > -- > > Key: TINKERPOP-2023 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2023 > Project: TinkerPop > Issue Type: Improvement > Components: server >Affects Versions: 3.2.9 >Reporter: Robert Dale >Assignee: Robert Dale >Priority: Minor > Labels: breaking, deprecation, security > Fix For: 3.4.0, 3.3.4, 3.2.10 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TINKERPOP-2023) Gremlin Server should not create self-signed certs
[ https://issues.apache.org/jira/browse/TINKERPOP-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale updated TINKERPOP-2023: --- Labels: breaking deprecation security (was: breaking deprecation) > Gremlin Server should not create self-signed certs > -- > > Key: TINKERPOP-2023 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2023 > Project: TinkerPop > Issue Type: Improvement > Components: server >Affects Versions: 3.2.9 >Reporter: Robert Dale >Assignee: Robert Dale >Priority: Minor > Labels: breaking, deprecation, security > Fix For: 3.4.0, 3.3.4, 3.2.10 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (TINKERPOP-2022) Cluster SSL should trust default ca certs by default
[ https://issues.apache.org/jira/browse/TINKERPOP-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale closed TINKERPOP-2022. -- Resolution: Fixed > Cluster SSL should trust default ca certs by default > > > Key: TINKERPOP-2022 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2022 > Project: TinkerPop > Issue Type: Improvement > Components: driver >Affects Versions: 3.2.9 >Reporter: Robert Dale >Assignee: Robert Dale >Priority: Minor > Labels: security > Fix For: 3.4.0, 3.3.4, 3.2.10 > > > See thread > https://groups.google.com/d/msg/gremlin-users/2z7Si4wM0SU/lL3OqR0LCgAJ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TINKERPOP-2022) Cluster SSL should trust default ca certs by default
[ https://issues.apache.org/jira/browse/TINKERPOP-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale updated TINKERPOP-2022: --- Labels: security (was: ) > Cluster SSL should trust default ca certs by default > > > Key: TINKERPOP-2022 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2022 > Project: TinkerPop > Issue Type: Improvement > Components: driver >Affects Versions: 3.2.9 >Reporter: Robert Dale >Assignee: Robert Dale >Priority: Minor > Labels: security > Fix For: 3.4.0, 3.3.4, 3.2.10 > > > See thread > https://groups.google.com/d/msg/gremlin-users/2z7Si4wM0SU/lL3OqR0LCgAJ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TINKERPOP-2022) Cluster SSL should trust default ca certs by default
[ https://issues.apache.org/jira/browse/TINKERPOP-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale updated TINKERPOP-2022: --- Fix Version/s: 3.2.10 3.3.4 3.4.0 > Cluster SSL should trust default ca certs by default > > > Key: TINKERPOP-2022 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2022 > Project: TinkerPop > Issue Type: Improvement > Components: driver >Affects Versions: 3.2.9 >Reporter: Robert Dale >Assignee: Robert Dale >Priority: Minor > Fix For: 3.4.0, 3.3.4, 3.2.10 > > > See thread > https://groups.google.com/d/msg/gremlin-users/2z7Si4wM0SU/lL3OqR0LCgAJ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (TINKERPOP-2023) Gremlin Server should not create self-signed certs
Robert Dale created TINKERPOP-2023: -- Summary: Gremlin Server should not create self-signed certs Key: TINKERPOP-2023 URL: https://issues.apache.org/jira/browse/TINKERPOP-2023 Project: TinkerPop Issue Type: Improvement Components: server Affects Versions: 3.2.9 Reporter: Robert Dale Assignee: Robert Dale -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (TINKERPOP-2022) Cluster SSL should trust default ca certs by default
Robert Dale created TINKERPOP-2022: -- Summary: Cluster SSL should trust default ca certs by default Key: TINKERPOP-2022 URL: https://issues.apache.org/jira/browse/TINKERPOP-2022 Project: TinkerPop Issue Type: Improvement Components: driver Affects Versions: 3.2.9 Reporter: Robert Dale Assignee: Robert Dale See thread https://groups.google.com/d/msg/gremlin-users/2z7Si4wM0SU/lL3OqR0LCgAJ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TINKERPOP-940) Convert LocalTraversals to MatchSteps in OLAP and Solve the StarGraph Problem
[
https://issues.apache.org/jira/browse/TINKERPOP-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16570347#comment-16570347
]
Robert Dale commented on TINKERPOP-940:
---
It is documented in the Where step
[http://tinkerpop.apache.org/docs/current/reference/#where-step]
{noformat}
The anonymous traversal of where() processes the current object "locally". In
OLAP, where the atomic unit of computing is the vertex and its local "star
graph," it is important that the anonymous traversal does not leave the
confines of the vertex’s star graph. In other words, it can not traverse to an
adjacent vertex’s properties or edges. Note that is only a temporary limitation
that will be addressed in a future version of TinkerPop3 (see TINKERPOP-693).
{noformat}
However, TINKERPOP-693 has been closed. Will this address the limitation or
should we just remove it from the documentation?
> Convert LocalTraversals to MatchSteps in OLAP and Solve the StarGraph Problem
> -
>
> Key: TINKERPOP-940
> URL: https://issues.apache.org/jira/browse/TINKERPOP-940
> Project: TinkerPop
> Issue Type: Improvement
> Components: process
>Affects Versions: 3.1.0-incubating
>Reporter: Marko A. Rodriguez
>Assignee: Marko A. Rodriguez
>Priority: Major
>
> This fails in OLAP.
> {code}
> g.V().match(
> as('a').out('sungBy').as('b'),
> as('a').out('writtenBy').as('b')).
> select('a','b').by('name')
> {code}
> However, this passes:
> {code}
> g.V().match(
> as('a').out('sungBy').as('b'),
> as('a').out('writtenBy').as('b'),
> as('a').values('name').as('c'),
> as('b').values('name').as('d')).
> select('c','d')
> {code}
> Can all "local star graph" OLAP problems be strategized into MatchSteps? It
> would be a decoration strategy of some sort [~dkuppitz]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (TINKERPOP-940) Convert LocalTraversals to MatchSteps in OLAP and Solve the StarGraph Problem
[
https://issues.apache.org/jira/browse/TINKERPOP-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16570347#comment-16570347
]
Robert Dale edited comment on TINKERPOP-940 at 8/6/18 3:18 PM:
---
It is documented in the Where step
[http://tinkerpop.apache.org/docs/current/reference/#where-step]
{noformat}
The anonymous traversal of where() processes the current object "locally". In
OLAP, where the atomic unit of computing is the vertex and its local "star
graph," it is important that the anonymous traversal does not leave the
confines
of the vertex’s star graph. In other words, it can not traverse to an adjacent
vertex’s properties or edges. Note that is only a temporary limitation that
will be addressed in a future version of TinkerPop3 (see TINKERPOP-693).
{noformat}
However, TINKERPOP-693 has been closed. Will this address the limitation or
should we just remove it from the documentation?
was (Author: rdale):
It is documented in the Where step
[http://tinkerpop.apache.org/docs/current/reference/#where-step]
{noformat}
The anonymous traversal of where() processes the current object "locally". In
OLAP, where the atomic unit of computing is the vertex and its local "star
graph," it is important that the anonymous traversal does not leave the
confines of the vertex’s star graph. In other words, it can not traverse to an
adjacent vertex’s properties or edges. Note that is only a temporary limitation
that will be addressed in a future version of TinkerPop3 (see TINKERPOP-693).
{noformat}
However, TINKERPOP-693 has been closed. Will this address the limitation or
should we just remove it from the documentation?
> Convert LocalTraversals to MatchSteps in OLAP and Solve the StarGraph Problem
> -
>
> Key: TINKERPOP-940
> URL: https://issues.apache.org/jira/browse/TINKERPOP-940
> Project: TinkerPop
> Issue Type: Improvement
> Components: process
>Affects Versions: 3.1.0-incubating
>Reporter: Marko A. Rodriguez
>Assignee: Marko A. Rodriguez
>Priority: Major
>
> This fails in OLAP.
> {code}
> g.V().match(
> as('a').out('sungBy').as('b'),
> as('a').out('writtenBy').as('b')).
> select('a','b').by('name')
> {code}
> However, this passes:
> {code}
> g.V().match(
> as('a').out('sungBy').as('b'),
> as('a').out('writtenBy').as('b'),
> as('a').values('name').as('c'),
> as('b').values('name').as('d')).
> select('c','d')
> {code}
> Can all "local star graph" OLAP problems be strategized into MatchSteps? It
> would be a decoration strategy of some sort [~dkuppitz]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (TINKERPOP-2016) Upgrade Jackson FasterXML to 2.9.5 or later to fix security vulnerability
[ https://issues.apache.org/jira/browse/TINKERPOP-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale closed TINKERPOP-2016. -- Resolution: Fixed > Upgrade Jackson FasterXML to 2.9.5 or later to fix security vulnerability > - > > Key: TINKERPOP-2016 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2016 > Project: TinkerPop > Issue Type: Improvement > Components: io >Affects Versions: 3.3.3, 3.2.9 >Reporter: Luke Daugherty >Assignee: Robert Dale >Priority: Major > Labels: security > Fix For: 3.4.0, 3.3.4, 3.2.10 > > > The jackson libraries included in groovy-shaded-3.3.3 have a CVE reported > against them so the library is reported as High risk by vulnerability > scanners such as Nexus. > *[CVE-2018-7489|http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-7489]* -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TINKERPOP-2016) Upgrade Jackson FasterXML to 2.9.5 or later to fix security vulnerability
[ https://issues.apache.org/jira/browse/TINKERPOP-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale updated TINKERPOP-2016: --- Component/s: io > Upgrade Jackson FasterXML to 2.9.5 or later to fix security vulnerability > - > > Key: TINKERPOP-2016 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2016 > Project: TinkerPop > Issue Type: Improvement > Components: io >Affects Versions: 3.3.3, 3.2.9 >Reporter: Luke Daugherty >Assignee: Robert Dale >Priority: Major > Labels: security > Fix For: 3.4.0, 3.3.4, 3.2.10 > > > The jackson libraries included in groovy-shaded-3.3.3 have a CVE reported > against them so the library is reported as High risk by vulnerability > scanners such as Nexus. > *[CVE-2018-7489|http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-7489]* -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TINKERPOP-2016) Upgrade Jackson FasterXML to 2.9.5 or later to fix security vulnerability
[ https://issues.apache.org/jira/browse/TINKERPOP-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale updated TINKERPOP-2016: --- Labels: security (was: ) > Upgrade Jackson FasterXML to 2.9.5 or later to fix security vulnerability > - > > Key: TINKERPOP-2016 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2016 > Project: TinkerPop > Issue Type: Improvement >Affects Versions: 3.3.3, 3.2.9 >Reporter: Luke Daugherty >Assignee: Robert Dale >Priority: Major > Labels: security > Fix For: 3.4.0, 3.3.4, 3.2.10 > > > The jackson libraries included in groovy-shaded-3.3.3 have a CVE reported > against them so the library is reported as High risk by vulnerability > scanners such as Nexus. > *[CVE-2018-7489|http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-7489]* -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TINKERPOP-2016) Upgrade Jackson FasterXML to 2.9.5 or later to fix security vulnerability
[ https://issues.apache.org/jira/browse/TINKERPOP-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale updated TINKERPOP-2016: --- Fix Version/s: 3.2.10 3.3.4 3.4.0 > Upgrade Jackson FasterXML to 2.9.5 or later to fix security vulnerability > - > > Key: TINKERPOP-2016 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2016 > Project: TinkerPop > Issue Type: Improvement >Affects Versions: 3.3.3, 3.2.9 >Reporter: Luke Daugherty >Assignee: Robert Dale >Priority: Major > Labels: security > Fix For: 3.4.0, 3.3.4, 3.2.10 > > > The jackson libraries included in groovy-shaded-3.3.3 have a CVE reported > against them so the library is reported as High risk by vulnerability > scanners such as Nexus. > *[CVE-2018-7489|http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-7489]* -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TINKERPOP-2016) Upgrade Jackson FasterXML to 2.9.5 or later to fix security vulnerability
[ https://issues.apache.org/jira/browse/TINKERPOP-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale updated TINKERPOP-2016: --- Labels: security (was: ) > Upgrade Jackson FasterXML to 2.9.5 or later to fix security vulnerability > - > > Key: TINKERPOP-2016 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2016 > Project: TinkerPop > Issue Type: Bug >Affects Versions: 3.3.3, 3.2.9 >Reporter: Luke Daugherty >Assignee: Robert Dale >Priority: Major > Labels: security > > The jackson libraries included in groovy-shaded-3.3.3 have a CVE reported > against them so the library is reported as High risk by vulnerability > scanners such as Nexus. > *[CVE-2018-7489|http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-7489]* -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TINKERPOP-2016) Upgrade Jackson FasterXML to 2.9.5 or later to fix security vulnerability
[ https://issues.apache.org/jira/browse/TINKERPOP-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale updated TINKERPOP-2016: --- Affects Version/s: 3.2.9 > Upgrade Jackson FasterXML to 2.9.5 or later to fix security vulnerability > - > > Key: TINKERPOP-2016 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2016 > Project: TinkerPop > Issue Type: Bug >Affects Versions: 3.3.3, 3.2.9 >Reporter: Luke Daugherty >Assignee: Robert Dale >Priority: Major > > The jackson libraries included in groovy-shaded-3.3.3 have a CVE reported > against them so the library is reported as High risk by vulnerability > scanners such as Nexus. > *[CVE-2018-7489|http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-7489]* -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (TINKERPOP-2016) Upgrade Jackson FasterXML to 2.9.5 or later to fix security vulnerability
[ https://issues.apache.org/jira/browse/TINKERPOP-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale reassigned TINKERPOP-2016: -- Assignee: Robert Dale > Upgrade Jackson FasterXML to 2.9.5 or later to fix security vulnerability > - > > Key: TINKERPOP-2016 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2016 > Project: TinkerPop > Issue Type: Bug >Affects Versions: 3.3.3 >Reporter: Luke Daugherty >Assignee: Robert Dale >Priority: Major > > The jackson libraries included in groovy-shaded-3.3.3 have a CVE reported > against them so the library is reported as High risk by vulnerability > scanners such as Nexus. > *[CVE-2018-7489|http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-7489]* -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TINKERPOP-2003) After a long period (almost 5days)of parallel requests(almost 200 request per second),client.submit blocked
[
https://issues.apache.org/jira/browse/TINKERPOP-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16539997#comment-16539997
]
Robert Dale commented on TINKERPOP-2003:
Can you post the actual queries that time out from your Gremlin Server's
gremlin.log?
It should look like this
{noformat}
[WARN] AbstractEvalOpProcessor - Script evaluation exceeded the configured
threshold for request [RequestMessage{, requestId=..., op='eval', processor='',
args={gremlin=g.V(), batchSize=64}}]
{noformat}
It may also be helpful to see relevant stacktraces from the server.
I would also turn on GC logging to rule out any really long garbage collection
pause times.
What database are you using? Have you ruled out any contention there?
> After a long period (almost 5days)of parallel requests(almost 200 request per
> second),client.submit blocked
> ---
>
> Key: TINKERPOP-2003
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2003
> Project: TinkerPop
> Issue Type: Bug
> Components: driver
>Affects Versions: 3.3.0
>Reporter: xifenghz
>Priority: Major
>
> After a long period (almost 5days)of parallel requests(almost 200 request per
> second),client.submit blocked for scriptEvaluationTimeout configured,and
> return timeout.At the same time,many TCP connections in Gremlin Server are in
> CLOSE_WAIT state.
> Here is my usages:
> cluster = Cluster.build(FileUtils.toFile(config)).create();
> client = cluster.connect();
> ResultSet resultSet = null;
> {color:#ff}synchronized (Service.class){color}
> { resultSet = client.submit(gremlinScript); }
> CompletableFuture> future = null;
> List results = null;
> future = resultSet.all();
> results = future.get();
>
> The code snippet above runs in a java web app based on SpringMVC.I found a PR
> related to my question.
> [https://github.com/apache/tinkerpop/pull/367/commits/58d8bade7425c7a7865382990eaaed2b7d90659c#diff-06d5dfb02d5d2c807c2387c3e9338709]
> In this PR,the author seems to say gremlin doer not support high concurrency。
> {color:#ff}Removed recommendations for submitting parallel requests on a
> session from docs.{color}
> {color:#33}So,I submit the gremlin script in order(use synchronized
> keyword,just as my code snippet ).But in order to lift throughput,I do not
> lock the code for getting result from Gremlin Server。I want to know some
> details about how Gremlin Server receive and process requests,such as the
> receiver and executor threads are the same one?If so ,the Gremlin server can
> only process the requests one by one ? {color}
> {color:#33}I wonder whether or not Gremlin supports high concurrency(such
> as 200 second per second,including simple vertex or edge queries and complex
> combinatorial queries).If so,please help to find out why the process time for
> a simple script such as query vertex exceed scriptEvaluationTimeout. If
> not，is there other ways to make Gremlin Server support high concurrency,such
> as multi-gremlinserver。{color}
> Thank you sincerely for your help。
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (TINKERPOP-1992) count has negative time in profile
[
https://issues.apache.org/jira/browse/TINKERPOP-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16520793#comment-16520793
]
Robert Dale edited comment on TINKERPOP-1992 at 6/22/18 9:29 PM:
-
Tested on TinkerGraph
Steps to reproduce:
{noformat}
gremlin> graph = TinkerFactory.createModern()
==>tinkergraph[vertices:6 edges:6]
gremlin> g = graph.traversal()
==>graphtraversalsource[tinkergraph[vertices:6 edges:6], standard]
gremlin> g.V().group().by().by(bothE().count()).profile()
==>Traversal Metrics
Step Count
Traversers Time (ms)% Dur
=
TinkerGraphStep(vertex,[]) 6
6 2.66057.28
GroupStep(identity,[VertexStep(BOTH,edge), Prof... 1
1 1.98442.72
VertexStep(BOTH,edge) 12
12 0.557
CountGlobalStep 6
6 -0.506
>TOTAL -
- 4.645-
{noformat}
was (Author: rdale):
Tested on TinkerGraph
Steps to reproduce:
{noformat}
gremlin> graph = TinkerFactory.createModern()
==>tinkergraph[vertices:6 edges:6]
gremlin> g = graph.traversal()
==>graphtraversalsource[tinkergraph[vertices:6 edges:6], standard]
gremlin> g.V().group().by().by(bothE().count()).profile()
==>Traversal Metrics
Step Count Traversers Time (ms) % Dur
=
TinkerGraphStep(vertex,[]) 6 6 2.660 57.28
GroupStep(identity,[VertexStep(BOTH,edge), Prof... 1 1 1.984 42.72
VertexStep(BOTH,edge) 12 12 0.557
CountGlobalStep 6 6 -0.506
>TOTAL - - 4.645 -
{noformat}
> count has negative time in profile
> --
>
> Key: TINKERPOP-1992
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1992
> Project: TinkerPop
> Issue Type: Bug
> Components: process
>Affects Versions: 3.3.3, 3.2.9
>Reporter: Robert Dale
>Priority: Minor
>
> {noformat}
> gremlin> g.V().group().by().by(bothE().count()).profile()
> ==>Traversal Metrics
> Step Count
> Traversers Time (ms)% Dur
> =
> TinkerGraphStep(vertex,[]) 19172
> 19172 4.957 5.24
> GroupStep(identity,[VertexStep(BOTH,edge), Prof... 1
> 1 89.69694.76
> VertexStep(BOTH,edge)84812
> 84812 50.723
> CountGlobalStep 19172
> 19172 -39.649
> >TOTAL -
> - 94.654-
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (TINKERPOP-1992) count has negative time in profile
[
https://issues.apache.org/jira/browse/TINKERPOP-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16520793#comment-16520793
]
Robert Dale edited comment on TINKERPOP-1992 at 6/22/18 9:28 PM:
-
Tested on TinkerGraph
Steps to reproduce:
{noformat}
gremlin> graph = TinkerFactory.createModern()
==>tinkergraph[vertices:6 edges:6]
gremlin> g = graph.traversal()
==>graphtraversalsource[tinkergraph[vertices:6 edges:6], standard]
gremlin> g.V().group().by().by(bothE().count()).profile()
==>Traversal Metrics
Step Count Traversers Time (ms) % Dur
=
TinkerGraphStep(vertex,[]) 6 6 2.660 57.28
GroupStep(identity,[VertexStep(BOTH,edge), Prof... 1 1 1.984 42.72
VertexStep(BOTH,edge) 12 12 0.557
CountGlobalStep 6 6 -0.506
>TOTAL - - 4.645 -
{noformat}
was (Author: rdale):
Tested on TinkerGraph
> count has negative time in profile
> --
>
> Key: TINKERPOP-1992
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1992
> Project: TinkerPop
> Issue Type: Bug
> Components: process
>Affects Versions: 3.3.3, 3.2.9
>Reporter: Robert Dale
>Priority: Minor
>
> {noformat}
> gremlin> g.V().group().by().by(bothE().count()).profile()
> ==>Traversal Metrics
> Step Count
> Traversers Time (ms)% Dur
> =
> TinkerGraphStep(vertex,[]) 19172
> 19172 4.957 5.24
> GroupStep(identity,[VertexStep(BOTH,edge), Prof... 1
> 1 89.69694.76
> VertexStep(BOTH,edge)84812
> 84812 50.723
> CountGlobalStep 19172
> 19172 -39.649
> >TOTAL -
> - 94.654-
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (TINKERPOP-1992) count has negative time in profile
[
https://issues.apache.org/jira/browse/TINKERPOP-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16520793#comment-16520793
]
Robert Dale commented on TINKERPOP-1992:
Tested on TinkerGraph
> count has negative time in profile
> --
>
> Key: TINKERPOP-1992
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1992
> Project: TinkerPop
> Issue Type: Bug
> Components: process
>Affects Versions: 3.3.3, 3.2.9
>Reporter: Robert Dale
>Priority: Minor
>
> {noformat}
> gremlin> g.V().group().by().by(bothE().count()).profile()
> ==>Traversal Metrics
> Step Count
> Traversers Time (ms)% Dur
> =
> TinkerGraphStep(vertex,[]) 19172
> 19172 4.957 5.24
> GroupStep(identity,[VertexStep(BOTH,edge), Prof... 1
> 1 89.69694.76
> VertexStep(BOTH,edge)84812
> 84812 50.723
> CountGlobalStep 19172
> 19172 -39.649
> >TOTAL -
> - 94.654-
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (TINKERPOP-1992) count has negative time in profile
[
https://issues.apache.org/jira/browse/TINKERPOP-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16520789#comment-16520789
]
Robert Dale commented on TINKERPOP-1992:
I've tried other variants of count() and groupCount(). It seems to be this
specific usage only.
> count has negative time in profile
> --
>
> Key: TINKERPOP-1992
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1992
> Project: TinkerPop
> Issue Type: Bug
> Components: process
>Affects Versions: 3.3.3, 3.2.9
>Reporter: Robert Dale
>Priority: Minor
>
> {noformat}
> gremlin> g.V().group().by().by(bothE().count()).profile()
> ==>Traversal Metrics
> Step Count
> Traversers Time (ms)% Dur
> =
> TinkerGraphStep(vertex,[]) 19172
> 19172 4.957 5.24
> GroupStep(identity,[VertexStep(BOTH,edge), Prof... 1
> 1 89.69694.76
> VertexStep(BOTH,edge)84812
> 84812 50.723
> CountGlobalStep 19172
> 19172 -39.649
> >TOTAL -
> - 94.654-
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (TINKERPOP-1992) count has negative time
Robert Dale created TINKERPOP-1992:
--
Summary: count has negative time
Key: TINKERPOP-1992
URL: https://issues.apache.org/jira/browse/TINKERPOP-1992
Project: TinkerPop
Issue Type: Bug
Components: process
Affects Versions: 3.2.9, 3.3.3
Reporter: Robert Dale
{noformat}
gremlin> g.V().group().by().by(bothE().count()).profile()
==>Traversal Metrics
Step Count
Traversers Time (ms)% Dur
=
TinkerGraphStep(vertex,[]) 19172
19172 4.957 5.24
GroupStep(identity,[VertexStep(BOTH,edge), Prof... 1
1 89.69694.76
VertexStep(BOTH,edge)84812
84812 50.723
CountGlobalStep 19172
19172 -39.649
>TOTAL -
- 94.654-
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (TINKERPOP-1992) count has negative time in profile
[
https://issues.apache.org/jira/browse/TINKERPOP-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Dale updated TINKERPOP-1992:
---
Summary: count has negative time in profile (was: count has negative time)
> count has negative time in profile
> --
>
> Key: TINKERPOP-1992
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1992
> Project: TinkerPop
> Issue Type: Bug
> Components: process
>Affects Versions: 3.3.3, 3.2.9
>Reporter: Robert Dale
>Priority: Minor
>
> {noformat}
> gremlin> g.V().group().by().by(bothE().count()).profile()
> ==>Traversal Metrics
> Step Count
> Traversers Time (ms)% Dur
> =
> TinkerGraphStep(vertex,[]) 19172
> 19172 4.957 5.24
> GroupStep(identity,[VertexStep(BOTH,edge), Prof... 1
> 1 89.69694.76
> VertexStep(BOTH,edge)84812
> 84812 50.723
> CountGlobalStep 19172
> 19172 -39.649
> >TOTAL -
> - 94.654-
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (TINKERPOP-1575) Neo4j indicies not used when multiple labels are searched for
[
https://issues.apache.org/jira/browse/TINKERPOP-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516391#comment-16516391
]
Robert Dale commented on TINKERPOP-1575:
Is there a line between neo4j-gremlin being a simple reference and is
performance optimized?
> Neo4j indicies not used when multiple labels are searched for
> -
>
> Key: TINKERPOP-1575
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1575
> Project: TinkerPop
> Issue Type: Improvement
> Components: neo4j
>Affects Versions: 3.2.3
>Reporter: Branden Moore
>Priority: Minor
>
> When using a Neo4j-based graph, indicies are not used when more than one
> label is searched for.
> {noformat}
> gremlin> g.V().hasLabel("alpha").has("myProp", 10)
> Final Traversal [Neo4jGraphStep(vertex,[~label.eq(alpha),myProp.eq(10)]))]
> gremlin> g.V().hasLabel("alpha", "beta").has("myProp", 10)
> Final Traversal
> [Neo4jGraphStep(vertex,[~label.within(alpha,beta),myProp.eq(10)]))]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (TINKERPOP-1987) Bump to Netty 4.1.x
[ https://issues.apache.org/jira/browse/TINKERPOP-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516385#comment-16516385 ] Robert Dale commented on TINKERPOP-1987: See also https://issues.apache.org/jira/browse/TINKERPOP-1884?focusedCommentId=16415424&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16415424 See DISCUSS - https://lists.apache.org/thread.html/b3ade6b0edb9acbcecda12472a65a71b7889518f95868a6b56fa@%3Cdev.tinkerpop.apache.org%3E > Bump to Netty 4.1.x > --- > > Key: TINKERPOP-1987 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1987 > Project: TinkerPop > Issue Type: Improvement > Components: server >Affects Versions: 3.4.0 >Reporter: Robert Dale >Priority: Major > > Netty 4.0.x is EOL: > https://twitter.com/normanmaurer/status/960798363695435778 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (TINKERPOP-1987) Bump to Netty 4.1.x
Robert Dale created TINKERPOP-1987: -- Summary: Bump to Netty 4.1.x Key: TINKERPOP-1987 URL: https://issues.apache.org/jira/browse/TINKERPOP-1987 Project: TinkerPop Issue Type: Improvement Components: server Affects Versions: 3.4.0 Reporter: Robert Dale Netty 4.0.x is EOL: https://twitter.com/normanmaurer/status/960798363695435778 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TINKERPOP-1978) Check for Websocket connection state when retrieved from Connection Pool missing
[
https://issues.apache.org/jira/browse/TINKERPOP-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16515642#comment-16515642
]
Robert Dale commented on TINKERPOP-1978:
Then there's the issue of GLV-specific connection pools. Do we try to make
them on parity with the Java driver?
> Check for Websocket connection state when retrieved from Connection Pool
> missing
>
>
> Key: TINKERPOP-1978
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1978
> Project: TinkerPop
> Issue Type: Bug
> Components: dotnet
>Affects Versions: 3.3.3
>Reporter: Jamilu Abubakar
>Priority: Major
>
> When retrieving a connection from the connection pool there is no check to
> see what the current connection state of the websocket is before it is used.
> This means that if the websocket were to be closed because the server
> recycled or the connection was aborted by the server since it was last used
> and its Send method were to be called the following exception would be thrown:
> {quote}Error during execution ExecuteJObjectQueryAsync method. Exception:
> System.Net.Http.WinHttpException (0x80072EFF): The connection with the server
> was terminated abnormally
> at System.Net.WebSockets.WinHttpWebSocket.SendAsync(ArraySegment`1 buffer,
> WebSocketMessageType messageType, Boolean endOfMessage, CancellationToken
> cancellationToken)
> at System.Net.WebSockets.WebSocketHandle.SendAsync(ArraySegment`1 buffer,
> WebSocketMessageType messageType, Boolean endOfMessage, CancellationToken
> cancellationToken)
> at Gremlin.Net.Driver.WebSocketConnection.d__5.MoveNext()
> {quote}
>
> Please add check the Websocket state before use, handle exceptions due to
> closed or aborted connections and ideally have an extensible retry handler.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (TINKERPOP-1978) Check for Websocket connection state when retrieved from Connection Pool missing
[
https://issues.apache.org/jira/browse/TINKERPOP-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16515641#comment-16515641
]
Robert Dale commented on TINKERPOP-1978:
Does `connectionPool.keepAliveInterval` remove stale connections?
> Check for Websocket connection state when retrieved from Connection Pool
> missing
>
>
> Key: TINKERPOP-1978
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1978
> Project: TinkerPop
> Issue Type: Bug
> Components: dotnet
>Affects Versions: 3.3.3
>Reporter: Jamilu Abubakar
>Priority: Major
>
> When retrieving a connection from the connection pool there is no check to
> see what the current connection state of the websocket is before it is used.
> This means that if the websocket were to be closed because the server
> recycled or the connection was aborted by the server since it was last used
> and its Send method were to be called the following exception would be thrown:
> {quote}Error during execution ExecuteJObjectQueryAsync method. Exception:
> System.Net.Http.WinHttpException (0x80072EFF): The connection with the server
> was terminated abnormally
> at System.Net.WebSockets.WinHttpWebSocket.SendAsync(ArraySegment`1 buffer,
> WebSocketMessageType messageType, Boolean endOfMessage, CancellationToken
> cancellationToken)
> at System.Net.WebSockets.WebSocketHandle.SendAsync(ArraySegment`1 buffer,
> WebSocketMessageType messageType, Boolean endOfMessage, CancellationToken
> cancellationToken)
> at Gremlin.Net.Driver.WebSocketConnection.d__5.MoveNext()
> {quote}
>
> Please add check the Websocket state before use, handle exceptions due to
> closed or aborted connections and ideally have an extensible retry handler.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (TINKERPOP-1978) Check for Websocket connection state when retrieved from Connection Pool missing
[
https://issues.apache.org/jira/browse/TINKERPOP-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16515637#comment-16515637
]
Robert Dale commented on TINKERPOP-1978:
I think if you limit the scope of this to testing only if there is a viable
connection to the server, it can easily be achieved by checking the WebSocket
state (is it open?) and/or with a WebSocket ping (is it still connected?). It
could be a user option as to which method is used (what are the app
requirements?) Ideally, the driver would also have the option of background
checking to mitigate any in-line call latency. ;)
> Check for Websocket connection state when retrieved from Connection Pool
> missing
>
>
> Key: TINKERPOP-1978
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1978
> Project: TinkerPop
> Issue Type: Bug
> Components: dotnet
>Affects Versions: 3.3.3
>Reporter: Jamilu Abubakar
>Priority: Major
>
> When retrieving a connection from the connection pool there is no check to
> see what the current connection state of the websocket is before it is used.
> This means that if the websocket were to be closed because the server
> recycled or the connection was aborted by the server since it was last used
> and its Send method were to be called the following exception would be thrown:
> {quote}Error during execution ExecuteJObjectQueryAsync method. Exception:
> System.Net.Http.WinHttpException (0x80072EFF): The connection with the server
> was terminated abnormally
> at System.Net.WebSockets.WinHttpWebSocket.SendAsync(ArraySegment`1 buffer,
> WebSocketMessageType messageType, Boolean endOfMessage, CancellationToken
> cancellationToken)
> at System.Net.WebSockets.WebSocketHandle.SendAsync(ArraySegment`1 buffer,
> WebSocketMessageType messageType, Boolean endOfMessage, CancellationToken
> cancellationToken)
> at Gremlin.Net.Driver.WebSocketConnection.d__5.MoveNext()
> {quote}
>
> Please add check the Websocket state before use, handle exceptions due to
> closed or aborted connections and ideally have an extensible retry handler.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (TINKERPOP-1942) Binary serialization format
[ https://issues.apache.org/jira/browse/TINKERPOP-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16509612#comment-16509612 ] Robert Dale commented on TINKERPOP-1942: [~jorgebg] so when will the proof of concept be ready? :D > Binary serialization format > --- > > Key: TINKERPOP-1942 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1942 > Project: TinkerPop > Issue Type: Improvement > Components: io >Reporter: Jorge Bay >Priority: Major > > We should provide a binary serialization format designed to reduce > serialization overhead and minimizing the size of the payload that is > transmitted over the wire. > It could be implemented in a very similar way as Kryo support but with > interoperability in mind and ultimately we could fade Gryo out, as now with > the GLVs it doesn't have a role to play. > The main benefit would be the performance improvement, making serialization > and deserialization processing time negligible on both the server and the > client. > Background: > https://lists.apache.org/thread.html/13e70235591853801bab16ed457ee4f56f3dfe2d1c5817c34a036408@%3Cdev.tinkerpop.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TINKERPOP-1942) Binary serialization format
[ https://issues.apache.org/jira/browse/TINKERPOP-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16508273#comment-16508273 ] Robert Dale commented on TINKERPOP-1942: [~newkek] makes some excellent points. Extensibility must be preserved for Graph Providers. I read https://github.com/FasterXML/jackson-docs/wiki/Presentation:-Jackson-Performance and here are some key points: - Use of the binary format may be problematic more generally, as well; dealing with binary formats is very difficult from Javascript and, specifically, it is SLOWER than handling of JSON - Smile appears to be an easy conversion, just replace JsonFactory with SmileFactory - Smile has similar performance to using the Streaming API (which I believe we already use so we may not see much improvement here) - size of the data will decrease, typically by a similar amount (30-50%) (uncompressed) If we take "minimal compactness" a step further, then we should be able to add Gzip/LZO compression to the Channelizer today. Netty already has some WebSocket compression support. https://netty.io/4.1/api/io/netty/handler/codec/http/websocketx/extensions/compression/WebSocketServerCompressionHandler.html So it seems that the highest return with the least amount of work would be to do (in order): 1. Adding compression to Gremlin Server 2. Adding Smile as an option > Binary serialization format > --- > > Key: TINKERPOP-1942 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1942 > Project: TinkerPop > Issue Type: Improvement > Components: io >Reporter: Jorge Bay >Priority: Major > > We should provide a binary serialization format designed to reduce > serialization overhead and minimizing the size of the payload that is > transmitted over the wire. > It could be implemented in a very similar way as Kryo support but with > interoperability in mind and ultimately we could fade Gryo out, as now with > the GLVs it doesn't have a role to play. > The main benefit would be the performance improvement, making serialization > and deserialization processing time negligible on both the server and the > client. > Background: > https://lists.apache.org/thread.html/13e70235591853801bab16ed457ee4f56f3dfe2d1c5817c34a036408@%3Cdev.tinkerpop.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TINKERPOP-1961) Duplicate copies of images directory in docs
[
https://issues.apache.org/jira/browse/TINKERPOP-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16467739#comment-16467739
]
Robert Dale commented on TINKERPOP-1961:
the src zip does not contain duplicate images/ but the console and server zips
do
* [|https://issues.apache.org/jira/secure/AddComment!default.jspa?id=13157575]
> Duplicate copies of images directory in docs
>
>
> Key: TINKERPOP-1961
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1961
> Project: TinkerPop
> Issue Type: Bug
> Components: build-release
>Affects Versions: 3.2.6
>Reporter: stephen mallette
>Priority: Minor
>
> Starting at 3.2.6 we started getting duplicate copies of images being created
> on {{publish-docs.sh}}. For example:
> http://tinkerpop.apache.org/docs/3.2.9-SNAPSHOT/images/
> http://tinkerpop.apache.org/docs/3.2.9-SNAPSHOT/static/images/
> Would be nice to figure out what's causing that so as to reduce the size of
> the upload (not sure but that could also be bloating the zip distributions)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (TINKERPOP-1961) Duplicate copies of images directory in docs
[
https://issues.apache.org/jira/browse/TINKERPOP-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16467739#comment-16467739
]
Robert Dale edited comment on TINKERPOP-1961 at 5/8/18 5:41 PM:
the src zip does not contain duplicate images/ but the console and server zips
do
was (Author: rdale):
the src zip does not contain duplicate images/ but the console and server zips
do
* [|https://issues.apache.org/jira/secure/AddComment!default.jspa?id=13157575]
> Duplicate copies of images directory in docs
>
>
> Key: TINKERPOP-1961
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1961
> Project: TinkerPop
> Issue Type: Bug
> Components: build-release
>Affects Versions: 3.2.6
>Reporter: stephen mallette
>Priority: Minor
>
> Starting at 3.2.6 we started getting duplicate copies of images being created
> on {{publish-docs.sh}}. For example:
> http://tinkerpop.apache.org/docs/3.2.9-SNAPSHOT/images/
> http://tinkerpop.apache.org/docs/3.2.9-SNAPSHOT/static/images/
> Would be nice to figure out what's causing that so as to reduce the size of
> the upload (not sure but that could also be bloating the zip distributions)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (TINKERPOP-1959) Provide a way to submit scripts to the server
[ https://issues.apache.org/jira/browse/TINKERPOP-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16467735#comment-16467735 ] Robert Dale commented on TINKERPOP-1959: the src zip does not contain duplicate images/ but the console and server zips do > Provide a way to submit scripts to the server > - > > Key: TINKERPOP-1959 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1959 > Project: TinkerPop > Issue Type: Improvement > Components: javascript >Affects Versions: 3.2.8 >Reporter: stephen mallette >Priority: Critical > > It is currently only possible to submit bytecode based requests to the server > with gremlin-javascript. We should also provide some means for submitting > scripts. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (TINKERPOP-1959) Provide a way to submit scripts to the server
[ https://issues.apache.org/jira/browse/TINKERPOP-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Dale updated TINKERPOP-1959: --- Comment: was deleted (was: the src zip does not contain duplicate images/ but the console and server zips do) > Provide a way to submit scripts to the server > - > > Key: TINKERPOP-1959 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1959 > Project: TinkerPop > Issue Type: Improvement > Components: javascript >Affects Versions: 3.2.8 >Reporter: stephen mallette >Priority: Critical > > It is currently only possible to submit bytecode based requests to the server > with gremlin-javascript. We should also provide some means for submitting > scripts. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (TINKERPOP-1951) gremlin-server.bat doesn't support paths containing spaces
[
https://issues.apache.org/jira/browse/TINKERPOP-1951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Dale reassigned TINKERPOP-1951:
--
Assignee: (was: Robert Dale)
> gremlin-server.bat doesn't support paths containing spaces
> --
>
> Key: TINKERPOP-1951
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1951
> Project: TinkerPop
> Issue Type: Improvement
> Components: server
>Affects Versions: 3.3.2
> Environment: Windows operating system
>Reporter: Cédric L. Charlier
>Priority: Trivial
>
> If you copy the TinkerPop Gremlin Server to the folder
> {noformat}
> C:\Program Files\Apache TinkerPop\Server
> {noformat}
> then it would be impossible to start the server with the gremlin-server.bat
> file provided with the solution.
> The issue is that the spaces of the folder name will not be correctly handled
> when defining the CLASSPATH.
> It's possible to easily fix this issue by replacing the line
> {code:java}
> java -Dlog4j.configuration=conf/log4j-server.properties %JAVA_OPTIONS%
> %JAVA_ARGS% -cp %LIBDIR%\*;%EXTDIR%;
> org.apache.tinkerpop.gremlin.server.GremlinServer %*
> {code}
> by
> {code:java}
> java -Dlog4j.configuration=conf/log4j-server.properties %JAVA_OPTIONS%
> %JAVA_ARGS% -cp "%LIBDIR%\*;%EXTDIR%;"
> org.apache.tinkerpop.gremlin.server.GremlinServer %*
> {code}
> (the value provided for the -cp argument must be surrounded by double quotes).
> Same case a few lines bellow this occurrence with
> {code:java}
> java -Dlog4j.configuration=conf/log4j-server.properties %JAVA_OPTIONS%
> %JAVA_ARGS% -cp %LIBDIR%\*;%EXTDIR%;
> org.apache.tinkerpop.gremlin.server.util.GremlinServerInstall %RESTVAR%
> {code}
> to be replaced by
> {code:java}
> java -Dlog4j.configuration=conf/log4j-server.properties %JAVA_OPTIONS%
> %JAVA_ARGS% -cp "%LIBDIR%\*;%EXTDIR%;"
> org.apache.tinkerpop.gremlin.server.util.GremlinServerInstall %RESTVAR%
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (TINKERPOP-1953) Bump to Groovy 2.4.15
[
https://issues.apache.org/jira/browse/TINKERPOP-1953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448106#comment-16448106
]
Robert Dale commented on TINKERPOP-1953:
Related to https://issues.apache.org/jira/browse/GROOVY-8494
> Bump to Groovy 2.4.15
> -
>
> Key: TINKERPOP-1953
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1953
> Project: TinkerPop
> Issue Type: Improvement
> Components: groovy
>Affects Versions: 3.2.8
>Reporter: stephen mallette
>Assignee: stephen mallette
>Priority: Critical
> Fix For: 3.4.0, 3.2.9, 3.3.3
>
>
> Bump to Groovy 2.4.15 to get a critical fix to this problem:
> {code}
> gremlin> org.apache.tinkerpop.gremlin.util.function.Lambda.function("{
> it.get() }")
> (class: org/apache/tinkerpop/gremlin/util/function/Lambda$function, method:
> callStatic signature:
> (Ljava/lang/Class;[Ljava/lang/Object;)Ljava/lang/Object;) Illegal type in
> constant pool
> Type ':help' or ':h' for help.
> Display stack trace? [yN]n
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (TINKERPOP-1948) Sum-step should work on properties of type 'Duration'.
[
https://issues.apache.org/jira/browse/TINKERPOP-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16445902#comment-16445902
]
Robert Dale commented on TINKERPOP-1948:
Or maybe types that are in `Extended` types should not be implied to have
first-class support but rather are there for transport purposes only. That is,
these are here so you can set/get these types from your data store, but don't
necessarily work in traversals. But if it's going to cause ambiguity issues,
then maybe that support should just go away completely.
IMO, Duration should really just be stored as a number. All Temporal types can
be distilled to a number. The client's Object-Graph-Mapper should handle
converting that data type.
> Sum-step should work on properties of type 'Duration'.
> --
>
> Key: TINKERPOP-1948
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1948
> Project: TinkerPop
> Issue Type: Improvement
> Components: process
>Affects Versions: 3.3.2
>Reporter: Daniel C. Weber
>Priority: Minor
>
> Consider the following query:
> {code:java}
> g.inject(_P1, _P2).sum()
> {code}
> where _P1 and _P2 are bound to values of type 'gx:Duration' (Graphson).
> This will fail with the following error message:
> {code:java}
> [WARN] AbstractEvalOpProcessor - Exception processing a script on request
> [RequestMessage{, requestId=c3e3b3c1-a0dd-4029-b0b6-f7650f6866b3, op='eval',
> processor='', args={gremlin=g.inject(_P1, _P2).sum(), bindings={_P1=PT1S,
> _P2=PT2S}}}].
> java.lang.ClassCastException: java.time.Duration cannot be cast to
> java.lang.Number
> at
> org.apache.tinkerpop.gremlin.process.traversal.step.map.SumGlobalStep.projectTraverser(SumGlobalStep.java:52)
> at
> org.apache.tinkerpop.gremlin.process.traversal.step.map.SumGlobalStep.projectTraverser(SumGlobalStep.java:37)
> at
> org.apache.tinkerpop.gremlin.process.traversal.step.util.ReducingBarrierStep.processAllStarts(ReducingBarrierStep.java:84)
> at
> org.apache.tinkerpop.gremlin.process.traversal.step.util.ReducingBarrierStep.processNextStart(ReducingBarrierStep.java:113)
> at
> org.apache.tinkerpop.gremlin.process.traversal.step.util.AbstractStep.hasNext(AbstractStep.java:143)
> at
> org.apache.tinkerpop.gremlin.process.traversal.util.DefaultTraversal.hasNext(DefaultTraversal.java:192)
> at
> org.apache.tinkerpop.gremlin.server.op.AbstractOpProcessor.handleIterator(AbstractOpProcessor.java:89)
> at
> org.apache.tinkerpop.gremlin.server.op.AbstractEvalOpProcessor.lambda$evalOpInternal$5(AbstractEvalOpProcessor.java:252)
> at
> org.apache.tinkerpop.gremlin.groovy.engine.GremlinExecutor.lambda$eval$0(GremlinExecutor.java:274)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> This is obviously due to the fact that the Sum-steps expects its arguments to
> be of type Number, which Duration obviously is not. Since summation of
> Durations is easily available through [this
> method|[https://docs.oracle.com/javase/8/docs/api/java/time/Duration.html#plus-java.time.Duration-]]
> it's worth consideration. The feature would save us an ugly roundtrip by
> saving longs since in some of our queries, we use sum().
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (TINKERPOP-1940) Command parsing problem with files for long options in gremlin.sh
[
https://issues.apache.org/jira/browse/TINKERPOP-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16442412#comment-16442412
]
Robert Dale edited comment on TINKERPOP-1940 at 4/18/18 12:27 PM:
--
I disagree.
{noformat}
`--` is a special case that says ignore any `-` or `--` args after this. It
does not allow you to pass arguments starting with `-` to other parameters.
The normal way of referencing a file starting with `-`, as goofy as that may
be, is to use `./`:
`bin/gremlin.sh --interactive ./-l`
{noformat}
You can try to 'fix' it if you want, but it's really not standard and I don't
think it's worth the
time and effort even as trivial as it may be.
was (Author: rdale):
I disagree. {noformat}`--` is a special case that says ignore any `-` or `--`
args after this. It does not allow you to pass arguments starting with `-` to
other parameters.
The normal way of referencing a file starting with `-`, as goofy as that may
be, is to use `./`:
`bin/gremlin.sh --interactive ./-l`
{noformat}
You can try to 'fix' it if you want, but it's really not standard and I don't
think it's worth the time and effort even as trivial as it may be.
> Command parsing problem with files for long options in gremlin.sh
> -
>
> Key: TINKERPOP-1940
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1940
> Project: TinkerPop
> Issue Type: Improvement
> Components: console
>Affects Versions: 3.2.8
>Reporter: stephen mallette
>Assignee: stephen mallette
>Priority: Minor
> Fix For: 3.4.0, 3.2.9, 3.3.3
>
>
> A bit of an edge case, but shows that there's still something amiss in the
> command parser:
> {code}
> $ echo '1+1' > '-l'
> $ cat -- -l
> 1+1
> $ bin/gremlin.sh --interactive -l
> bin/gremlin.sh: line 85: $3: unbound variable
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (TINKERPOP-1940) Command parsing problem with files for long options in gremlin.sh
[
https://issues.apache.org/jira/browse/TINKERPOP-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16442412#comment-16442412
]
Robert Dale edited comment on TINKERPOP-1940 at 4/18/18 12:27 PM:
--
I disagree.
{noformat}
`--` is a special case that says ignore any `-` or `--` args after this. It
does not allow you to pass arguments starting with `-` to other parameters.
The normal way of referencing a file starting with `-`, as goofy as that may be,
is to use `./`:
`bin/gremlin.sh --interactive ./-l`
{noformat}
You can try to 'fix' it if you want, but it's really not standard and I don't
think it's worth the
time and effort even as trivial as it may be.
was (Author: rdale):
I disagree.
{noformat}
`--` is a special case that says ignore any `-` or `--` args after this. It
does not allow you to pass arguments starting with `-` to other parameters.
The normal way of referencing a file starting with `-`, as goofy as that may
be, is to use `./`:
`bin/gremlin.sh --interactive ./-l`
{noformat}
You can try to 'fix' it if you want, but it's really not standard and I don't
think it's worth the
time and effort even as trivial as it may be.
> Command parsing problem with files for long options in gremlin.sh
> -
>
> Key: TINKERPOP-1940
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1940
> Project: TinkerPop
> Issue Type: Improvement
> Components: console
>Affects Versions: 3.2.8
>Reporter: stephen mallette
>Assignee: stephen mallette
>Priority: Minor
> Fix For: 3.4.0, 3.2.9, 3.3.3
>
>
> A bit of an edge case, but shows that there's still something amiss in the
> command parser:
> {code}
> $ echo '1+1' > '-l'
> $ cat -- -l
> 1+1
> $ bin/gremlin.sh --interactive -l
> bin/gremlin.sh: line 85: $3: unbound variable
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
