[jira] [Commented] (TINKERPOP-1319) several FeatureRequirement annotations are incorrect in gremlin-test
[ https://issues.apache.org/jira/browse/TINKERPOP-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15365238#comment-15365238 ] ASF GitHub Bot commented on TINKERPOP-1319: --- Github user pluradj commented on the issue: https://github.com/apache/tinkerpop/pull/335 I'll rerun it too > several FeatureRequirement annotations are incorrect in gremlin-test > > > Key: TINKERPOP-1319 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1319 > Project: TinkerPop > Issue Type: Bug > Components: test-suite >Affects Versions: 3.2.0-incubating, 3.1.2-incubating >Reporter: Jason Plurad >Assignee: Jason Plurad >Priority: Minor > Fix For: 3.1.3, 3.2.1 > > > Several {{@FeatureRequirement}} annotations are incorrect in these > {{gremlin-test}} tests > * EdgeTest.java > * FeatureSupportTest.java > * GraphTest.java > * PropertyTest.java > * VertexPropertyTest.java > * VertexTest.java > I'll submit a patch for this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] tinkerpop issue #335: TINKERPOP-1319: fix incorrect FeatureRequirement annot...
Github user pluradj commented on the issue: https://github.com/apache/tinkerpop/pull/335 I'll rerun it too --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (TINKERPOP-1319) several FeatureRequirement annotations are incorrect in gremlin-test
[ https://issues.apache.org/jira/browse/TINKERPOP-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15365187#comment-15365187 ] ASF GitHub Bot commented on TINKERPOP-1319: --- Github user dkuppitz commented on the issue: https://github.com/apache/tinkerpop/pull/335 Hmm, that's odd. Maybe just another random error on my side. I'll try it one more time and let it run over night. > several FeatureRequirement annotations are incorrect in gremlin-test > > > Key: TINKERPOP-1319 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1319 > Project: TinkerPop > Issue Type: Bug > Components: test-suite >Affects Versions: 3.2.0-incubating, 3.1.2-incubating >Reporter: Jason Plurad >Assignee: Jason Plurad >Priority: Minor > Fix For: 3.1.3, 3.2.1 > > > Several {{@FeatureRequirement}} annotations are incorrect in these > {{gremlin-test}} tests > * EdgeTest.java > * FeatureSupportTest.java > * GraphTest.java > * PropertyTest.java > * VertexPropertyTest.java > * VertexTest.java > I'll submit a patch for this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] tinkerpop issue #335: TINKERPOP-1319: fix incorrect FeatureRequirement annot...
Github user dkuppitz commented on the issue: https://github.com/apache/tinkerpop/pull/335 Hmm, that's odd. Maybe just another random error on my side. I'll try it one more time and let it run over night. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (TINKERPOP-1319) several FeatureRequirement annotations are incorrect in gremlin-test
[ https://issues.apache.org/jira/browse/TINKERPOP-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15365167#comment-15365167 ] ASF GitHub Bot commented on TINKERPOP-1319: --- Github user pluradj commented on the issue: https://github.com/apache/tinkerpop/pull/335 ``` [INFO] [INFO] Reactor Summary: [INFO] [INFO] Apache TinkerPop .. SUCCESS [49.025s] [INFO] Apache TinkerPop :: Gremlin Shaded SUCCESS [10.134s] [INFO] Apache TinkerPop :: Gremlin Core .. SUCCESS [33.447s] [INFO] Apache TinkerPop :: Gremlin Test .. SUCCESS [8.743s] [INFO] Apache TinkerPop :: Gremlin Groovy SUCCESS [1:28.938s] [INFO] Apache TinkerPop :: Gremlin Groovy Test ... SUCCESS [9.088s] [INFO] Apache TinkerPop :: TinkerGraph Gremlin ... SUCCESS [4:05.011s] [INFO] Apache TinkerPop :: Hadoop Gremlin SUCCESS [6:23.000s] [INFO] Apache TinkerPop :: Spark Gremlin . SUCCESS [13:38.044s] [INFO] Apache TinkerPop :: Giraph Gremlin SUCCESS [2:01:30.357s] [INFO] Apache TinkerPop :: Neo4j Gremlin . SUCCESS [31:45.126s] [INFO] Apache TinkerPop :: Gremlin Driver SUCCESS [8.683s] [INFO] Apache TinkerPop :: Gremlin Server SUCCESS [12:03.655s] [INFO] Apache TinkerPop :: Gremlin Console ... SUCCESS [1:57.427s] [INFO] Apache TinkerPop :: Gremlin Archetype . SUCCESS [0.222s] [INFO] Apache TinkerPop :: Archetype - TinkerGraph ... SUCCESS [16.966s] [INFO] Apache TinkerPop :: Archetype - Server SUCCESS [13.702s] [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 3:15:22.725s [INFO] Finished at: Wed Jul 06 21:31:50 UTC 2016 [INFO] Final Memory: 106M/275M [INFO] Untagged: tinkerpop:build-1467828977 Deleted: sha256:fc0be61b8011cafa062bca435b24f0f1fa407d4891c2f93ca831ae5dd17c4184 Deleted: sha256:125d80aa8cb9f1988c9545af45434b45e997fa197a05e21ff0be06d31eb5c9f9 Deleted: sha256:ad8bc8dc69b8cf2e2d1a45d71ec3ceac476b10d9d410741157940a990ea54050 Deleted: sha256:4343aa626aa513ab75e38a1605adeb64bf8db026f4cc56b42b343b4798319a15 Deleted: sha256:94de2ed6571c94cbd0f154b71c7ca3f04d32e77228b79ed5922396ab4b340d62 Deleted: sha256:1915ffba96ed51ac0a85ba201be2c77eada5cb587b225841b0ae2841cb4403eb ``` Worked for me. Is this something I should wait on before committing? > several FeatureRequirement annotations are incorrect in gremlin-test > > > Key: TINKERPOP-1319 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1319 > Project: TinkerPop > Issue Type: Bug > Components: test-suite >Affects Versions: 3.2.0-incubating, 3.1.2-incubating >Reporter: Jason Plurad >Assignee: Jason Plurad >Priority: Minor > Fix For: 3.1.3, 3.2.1 > > > Several {{@FeatureRequirement}} annotations are incorrect in these > {{gremlin-test}} tests > * EdgeTest.java > * FeatureSupportTest.java > * GraphTest.java > * PropertyTest.java > * VertexPropertyTest.java > * VertexTest.java > I'll submit a patch for this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] tinkerpop issue #335: TINKERPOP-1319: fix incorrect FeatureRequirement annot...
Github user pluradj commented on the issue: https://github.com/apache/tinkerpop/pull/335 ``` [INFO] [INFO] Reactor Summary: [INFO] [INFO] Apache TinkerPop .. SUCCESS [49.025s] [INFO] Apache TinkerPop :: Gremlin Shaded SUCCESS [10.134s] [INFO] Apache TinkerPop :: Gremlin Core .. SUCCESS [33.447s] [INFO] Apache TinkerPop :: Gremlin Test .. SUCCESS [8.743s] [INFO] Apache TinkerPop :: Gremlin Groovy SUCCESS [1:28.938s] [INFO] Apache TinkerPop :: Gremlin Groovy Test ... SUCCESS [9.088s] [INFO] Apache TinkerPop :: TinkerGraph Gremlin ... SUCCESS [4:05.011s] [INFO] Apache TinkerPop :: Hadoop Gremlin SUCCESS [6:23.000s] [INFO] Apache TinkerPop :: Spark Gremlin . SUCCESS [13:38.044s] [INFO] Apache TinkerPop :: Giraph Gremlin SUCCESS [2:01:30.357s] [INFO] Apache TinkerPop :: Neo4j Gremlin . SUCCESS [31:45.126s] [INFO] Apache TinkerPop :: Gremlin Driver SUCCESS [8.683s] [INFO] Apache TinkerPop :: Gremlin Server SUCCESS [12:03.655s] [INFO] Apache TinkerPop :: Gremlin Console ... SUCCESS [1:57.427s] [INFO] Apache TinkerPop :: Gremlin Archetype . SUCCESS [0.222s] [INFO] Apache TinkerPop :: Archetype - TinkerGraph ... SUCCESS [16.966s] [INFO] Apache TinkerPop :: Archetype - Server SUCCESS [13.702s] [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 3:15:22.725s [INFO] Finished at: Wed Jul 06 21:31:50 UTC 2016 [INFO] Final Memory: 106M/275M [INFO] Untagged: tinkerpop:build-1467828977 Deleted: sha256:fc0be61b8011cafa062bca435b24f0f1fa407d4891c2f93ca831ae5dd17c4184 Deleted: sha256:125d80aa8cb9f1988c9545af45434b45e997fa197a05e21ff0be06d31eb5c9f9 Deleted: sha256:ad8bc8dc69b8cf2e2d1a45d71ec3ceac476b10d9d410741157940a990ea54050 Deleted: sha256:4343aa626aa513ab75e38a1605adeb64bf8db026f4cc56b42b343b4798319a15 Deleted: sha256:94de2ed6571c94cbd0f154b71c7ca3f04d32e77228b79ed5922396ab4b340d62 Deleted: sha256:1915ffba96ed51ac0a85ba201be2c77eada5cb587b225841b0ae2841cb4403eb ``` Worked for me. Is this something I should wait on before committing? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (TINKERPOP-1338) Bump to Groovy 2.4.7
[ https://issues.apache.org/jira/browse/TINKERPOP-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15365068#comment-15365068 ] ASF GitHub Bot commented on TINKERPOP-1338: --- Github user dkuppitz commented on the issue: https://github.com/apache/tinkerpop/pull/356 VOTE: +1 > Bump to Groovy 2.4.7 > > > Key: TINKERPOP-1338 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1338 > Project: TinkerPop > Issue Type: Improvement > Components: groovy >Affects Versions: 3.2.0-incubating >Reporter: stephen mallette >Priority: Minor > Fix For: 3.2.1 > > > Provides a number of bug fixes: > http://groovy-lang.org/changelogs/changelog-2.4.7.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] tinkerpop issue #356: TINKERPOP-1338 Bumped groovy to 2.4.7
Github user dkuppitz commented on the issue: https://github.com/apache/tinkerpop/pull/356 VOTE: +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (TINKERPOP-1338) Bump to Groovy 2.4.7
[ https://issues.apache.org/jira/browse/TINKERPOP-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364981#comment-15364981 ] ASF GitHub Bot commented on TINKERPOP-1338: --- Github user okram commented on the issue: https://github.com/apache/tinkerpop/pull/356 VOTE +1. > Bump to Groovy 2.4.7 > > > Key: TINKERPOP-1338 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1338 > Project: TinkerPop > Issue Type: Improvement > Components: groovy >Affects Versions: 3.2.0-incubating >Reporter: stephen mallette >Priority: Minor > Fix For: 3.2.1 > > > Provides a number of bug fixes: > http://groovy-lang.org/changelogs/changelog-2.4.7.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] tinkerpop issue #356: TINKERPOP-1338 Bumped groovy to 2.4.7
Github user okram commented on the issue: https://github.com/apache/tinkerpop/pull/356 VOTE +1. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (TINKERPOP-1338) Bump to Groovy 2.4.7
[ https://issues.apache.org/jira/browse/TINKERPOP-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364951#comment-15364951 ] ASF GitHub Bot commented on TINKERPOP-1338: --- Github user robertdale commented on the issue: https://github.com/apache/tinkerpop/pull/356 I rebased to include @okram 's fix in the jira ticket. 4.5 hours later, "docker/build.sh -t -i -n" passed! > Bump to Groovy 2.4.7 > > > Key: TINKERPOP-1338 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1338 > Project: TinkerPop > Issue Type: Improvement > Components: groovy >Affects Versions: 3.2.0-incubating >Reporter: stephen mallette >Priority: Minor > Fix For: 3.2.1 > > > Provides a number of bug fixes: > http://groovy-lang.org/changelogs/changelog-2.4.7.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] tinkerpop issue #356: TINKERPOP-1338 Bumped groovy to 2.4.7
Github user robertdale commented on the issue: https://github.com/apache/tinkerpop/pull/356 I rebased to include @okram 's fix in the jira ticket. 4.5 hours later, "docker/build.sh -t -i -n" passed! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (TINKERPOP-1319) several FeatureRequirement annotations are incorrect in gremlin-test
[ https://issues.apache.org/jira/browse/TINKERPOP-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364830#comment-15364830 ] ASF GitHub Bot commented on TINKERPOP-1319: --- Github user pluradj commented on the issue: https://github.com/apache/tinkerpop/pull/335 Trying the docker build now. Not sure why that would be failing with the changes I made. > several FeatureRequirement annotations are incorrect in gremlin-test > > > Key: TINKERPOP-1319 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1319 > Project: TinkerPop > Issue Type: Bug > Components: test-suite >Affects Versions: 3.2.0-incubating, 3.1.2-incubating >Reporter: Jason Plurad >Assignee: Jason Plurad >Priority: Minor > Fix For: 3.1.3, 3.2.1 > > > Several {{@FeatureRequirement}} annotations are incorrect in these > {{gremlin-test}} tests > * EdgeTest.java > * FeatureSupportTest.java > * GraphTest.java > * PropertyTest.java > * VertexPropertyTest.java > * VertexTest.java > I'll submit a patch for this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] tinkerpop issue #335: TINKERPOP-1319: fix incorrect FeatureRequirement annot...
Github user pluradj commented on the issue: https://github.com/apache/tinkerpop/pull/335 Trying the docker build now. Not sure why that would be failing with the changes I made. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] tinkerpop pull request #:
Github user dalaro commented on the pull request: https://github.com/apache/tinkerpop/commit/f9706a38fbe546c0a7e5b038a6b99303d21aec01#commitcomment-18144496 @okram i don't understand the failure this caused, but the change seems innocuous to me... no objections --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] tinkerpop pull request #:
Github user okram commented on the pull request: https://github.com/apache/tinkerpop/commit/1915fa531a5b3fb20b59d258313224864448ae0a#commitcomment-18144354 In gremlin-core/src/main/java/org/apache/tinkerpop/gremlin/process/traversal/Translator.java: In gremlin-core/src/main/java/org/apache/tinkerpop/gremlin/process/traversal/Translator.java on line 52: Updated in latest push. Thanks for the heads up. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (TINKERPOP-1354) Include all static enum imports in request validation for bindings
[ https://issues.apache.org/jira/browse/TINKERPOP-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364460#comment-15364460 ] ASF GitHub Bot commented on TINKERPOP-1354: --- Github user asfgit closed the pull request at: https://github.com/apache/tinkerpop/pull/354 > Include all static enum imports in request validation for bindings > -- > > Key: TINKERPOP-1354 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1354 > Project: TinkerPop > Issue Type: Improvement > Components: server >Affects Versions: 3.1.2-incubating >Reporter: stephen mallette >Assignee: stephen mallette >Priority: Minor > Labels: breaking > Fix For: 3.1.3, 3.2.1 > > > Gremlin Server validates the bindings of incoming requests and returns an > error for any reserved terms. The list of reserved terms only includes {{T}} > but should also include others like {{Order}} and {{Scope}} so that users > don't inadvertently override them with a request binding. When that happens > Gremlin Server throws a not so easy to understand error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] tinkerpop pull request #354: TINKERPOP-1354 Added more invalid binding keys ...
Github user asfgit closed the pull request at: https://github.com/apache/tinkerpop/pull/354 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Closed] (TINKERPOP-1350) Server locks when submitting parallel requests on session
[ https://issues.apache.org/jira/browse/TINKERPOP-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stephen mallette closed TINKERPOP-1350. --- Resolution: Fixed > Server locks when submitting parallel requests on session > - > > Key: TINKERPOP-1350 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1350 > Project: TinkerPop > Issue Type: Bug > Components: server >Affects Versions: 3.1.2-incubating >Reporter: stephen mallette >Assignee: stephen mallette >Priority: Critical > Fix For: 3.1.3, 3.2.1 > > > This really is only a problem when there is some form of long blocking script > submitted and only on a session when done in parallel, like: > {code} > final ResultSet first = client.submit( > "Object mon1 = 'mon1';\n" + > "synchronized (mon1) {\n" + > "mon1.wait();\n" + > "} "); > final ResultSet second = client.submit( > "Object mon2 = 'mon2';\n" + > "synchronized (mon2) {\n" + > "mon2.wait();\n" + > "}"); > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [DISCUSS] Thinking on Release
Hi, > On Jul 6, 2016, at 8:25 AM, Ted Wilmes wrote: > > Sounds good and I will include benchmark numbers. I probably won't have > large scale Spark cluster #'s at the time of PR but maybe can get those out > during the freeze. I did have one question, should this work go into the > 3.1 line or just 3.2.x? Okay. There are some integration tests on MatchStep that consume a lot of memory due to path-data. I think we can get a good idea of speed on Spark simply by how much faster the integration tests run! :) But, of course, large scale cluster testing would be awesome. Regarding 3.1.x or 3.2.x — it depends. I suspect the changes are pretty complex and thus, it would be best to put into 3.2.x only, but if not, then yes, target 3.1.x and up merge to 3.2.x. Up to you. Thanks, Marko. > > Thanks, > Ted > > On Wed, Jul 6, 2016 at 9:15 AM, Marko Rodriguez > wrote: > >> @Ted: When you get that PR out, I will immediately focus on reviewing it. >> Please make sure your branch has master/ merged into it so we know we know >> that if the code/design is good, then there won’t be any hiccups on merge. >> >> *** Also, benchmarks that dropping paths is “good” will be very important >> so hopefully you have that coming too. >> >> Thanks, >> Marko. >> >> http://markorodriguez.com >> >> >> >>> On Jul 6, 2016, at 8:07 AM, Stephen Mallette >> wrote: >>> >>> We're starting to go through reviews now with some earnest. Unless there >>> are concerns, I think that we should target code freeze for Friday at >> this >>> point. >>> >>> On Wed, Jul 6, 2016 at 10:01 AM, Ted Wilmes wrote: >>> Quick update, I plan on getting a PR in late tonight or tomorrow morning for 1254. Thanks, Ted On Fri, Jul 1, 2016 at 6:04 PM, Stephen Mallette wrote: > Thanks for the update Ted. We may need an extra day or two to clear up some > other discussion on some of the other PRs - i don't think we can start >> a > code freeze on Monday as I'd proposed. > > On Fri, Jul 1, 2016 at 6:49 PM, Ted Wilmes wrote: > >> Hi everyone, >> I had some time this week and made further progress on 1254. Still > working >> out some kinks but I'll see how far I can get over the weekend. Have >> a >> good 4th. >> >> --Ted >> >> On Tue, Jun 28, 2016 at 11:50 AM, Marko Rodriguez < okramma...@gmail.com> >> wrote: >> >>> Hi, >>> >>> Ted — I think we should get that work into the next release. Thus, if > you >>> need more time (reasonable amount), then I say we delay accordingly. >>> >>> NOTE: The Gremlin-Python stuff will not get into the next release. It > has >>> gotten really complex/powerful and is currently 100+ commits ahead of >>> master/ ! :) .. As such, given the gargantuan undertaking, we will save >>> this work for a future release. >>> >>> Thanks, >>> Marko. >>> >>> http://markorodriguez.com >>> >>> >>> On Jun 28, 2016, at 10:36 AM, Ted Wilmes wrote: I would like to get TinkerPop-1254 in before code freeze. Shooting > for finishing it up by end of this week but I'll drop a note if it looks >>> like I won't make it. --Ted On Tue, Jun 28, 2016 at 5:35 AM, Stephen Mallette < >> spmalle...@gmail.com> wrote: > It's end of June - time to start firming up for release. We have a >>> number > of outstanding PRs that need votes/merge. Perhaps we try to get > those >>> all > in this week and begin code freeze next Monday (7/4)? > > I think we'll have to postpone the GLV work with gremlin-python for >> this > release. There's just too much left to do to get that in "right". > Are >>> there > any other open issues of importance? > > On Mon, Jun 6, 2016 at 9:18 AM, Marko Rodriguez < > okramma...@gmail.com >>> > wrote: > >> Yes, end of June-ish is best for me as I have few things on my > plate >>> the >> first half of this month. >> >> Thanks, >> Marko. >> >> http://markorodriguez.com >> >> >>> On Jun 6, 2016, at 4:46 AM, Stephen Mallette < > spmalle...@gmail.com> >> wrote: >>> >>> We didn't really discuss a date for release on this thread. I was >> thinking >>> that we could start looking at the week of July 4th as the target >> week >> for >>> VOTE and nail down a date as we get closer. >>> >>> On Wed, May 25, 2016 at 2:42 PM, Jason Plurad < plur...@gmail.com> > wrote: >>> I'd think from a TinkerPop branding perspective, it probably > helps >> to >> have
[jira] [Commented] (TINKERPOP-1350) Server locks when submitting parallel requests on session
[ https://issues.apache.org/jira/browse/TINKERPOP-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364393#comment-15364393 ] ASF GitHub Bot commented on TINKERPOP-1350: --- Github user asfgit closed the pull request at: https://github.com/apache/tinkerpop/pull/350 > Server locks when submitting parallel requests on session > - > > Key: TINKERPOP-1350 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1350 > Project: TinkerPop > Issue Type: Bug > Components: server >Affects Versions: 3.1.2-incubating >Reporter: stephen mallette >Assignee: stephen mallette >Priority: Critical > Fix For: 3.1.3, 3.2.1 > > > This really is only a problem when there is some form of long blocking script > submitted and only on a session when done in parallel, like: > {code} > final ResultSet first = client.submit( > "Object mon1 = 'mon1';\n" + > "synchronized (mon1) {\n" + > "mon1.wait();\n" + > "} "); > final ResultSet second = client.submit( > "Object mon2 = 'mon2';\n" + > "synchronized (mon2) {\n" + > "mon2.wait();\n" + > "}"); > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] tinkerpop pull request #350: TINKERPOP-1350 Fixed a problem with how timeout...
Github user asfgit closed the pull request at: https://github.com/apache/tinkerpop/pull/350 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] tinkerpop issue #315: Remove dashes from labels and property keys
Github user spmallette commented on the issue: https://github.com/apache/tinkerpop/pull/315 @analytically we're trying to finish reviewing PRs for the upcoming release of 3.2.1 and 3.1.3 - did you happen to see my note above? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] tinkerpop pull request #346: ResultSet.hasNext should be idempotent
Github user asfgit closed the pull request at: https://github.com/apache/tinkerpop/pull/346 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (TINKERPOP-1338) Bump to Groovy 2.4.7
[ https://issues.apache.org/jira/browse/TINKERPOP-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364375#comment-15364375 ] Marko A. Rodriguez commented on TINKERPOP-1338: --- The bug was in the @dalaro work where `Void` and `void` in the shim serializer are assuming `FieldSerializer`. I studied the Kryo code to note that `void` and `Void` are defaulted with `VoidSerializer`. The `spark-gremlin/` integration tests now pass and I have pushed the fix to master CTR. > Bump to Groovy 2.4.7 > > > Key: TINKERPOP-1338 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1338 > Project: TinkerPop > Issue Type: Improvement > Components: groovy >Affects Versions: 3.2.0-incubating >Reporter: stephen mallette >Priority: Minor > Fix For: 3.2.1 > > > Provides a number of bug fixes: > http://groovy-lang.org/changelogs/changelog-2.4.7.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TINKERPOP-1338) Bump to Groovy 2.4.7
[ https://issues.apache.org/jira/browse/TINKERPOP-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364373#comment-15364373 ] ASF GitHub Bot commented on TINKERPOP-1338: --- Github user robertdale commented on the issue: https://github.com/apache/tinkerpop/pull/356 This PR does include #353 but not #354 . In the meantime, I'm setting up docker. Thanks. > Bump to Groovy 2.4.7 > > > Key: TINKERPOP-1338 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1338 > Project: TinkerPop > Issue Type: Improvement > Components: groovy >Affects Versions: 3.2.0-incubating >Reporter: stephen mallette >Priority: Minor > Fix For: 3.2.1 > > > Provides a number of bug fixes: > http://groovy-lang.org/changelogs/changelog-2.4.7.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [DISCUSS] Thinking on Release
Sounds good and I will include benchmark numbers. I probably won't have large scale Spark cluster #'s at the time of PR but maybe can get those out during the freeze. I did have one question, should this work go into the 3.1 line or just 3.2.x? Thanks, Ted On Wed, Jul 6, 2016 at 9:15 AM, Marko Rodriguez wrote: > @Ted: When you get that PR out, I will immediately focus on reviewing it. > Please make sure your branch has master/ merged into it so we know we know > that if the code/design is good, then there won’t be any hiccups on merge. > > *** Also, benchmarks that dropping paths is “good” will be very important > so hopefully you have that coming too. > > Thanks, > Marko. > > http://markorodriguez.com > > > > > On Jul 6, 2016, at 8:07 AM, Stephen Mallette > wrote: > > > > We're starting to go through reviews now with some earnest. Unless there > > are concerns, I think that we should target code freeze for Friday at > this > > point. > > > > On Wed, Jul 6, 2016 at 10:01 AM, Ted Wilmes wrote: > > > >> Quick update, I plan on getting a PR in late tonight or tomorrow morning > >> for 1254. > >> > >> Thanks, > >> Ted > >> > >> On Fri, Jul 1, 2016 at 6:04 PM, Stephen Mallette > >> wrote: > >> > >>> Thanks for the update Ted. We may need an extra day or two to clear up > >> some > >>> other discussion on some of the other PRs - i don't think we can start > a > >>> code freeze on Monday as I'd proposed. > >>> > >>> On Fri, Jul 1, 2016 at 6:49 PM, Ted Wilmes wrote: > >>> > Hi everyone, > I had some time this week and made further progress on 1254. Still > >>> working > out some kinks but I'll see how far I can get over the weekend. Have > a > good 4th. > > --Ted > > On Tue, Jun 28, 2016 at 11:50 AM, Marko Rodriguez < > >> okramma...@gmail.com> > wrote: > > > Hi, > > > > Ted — I think we should get that work into the next release. Thus, if > >>> you > > need more time (reasonable amount), then I say we delay accordingly. > > > > NOTE: The Gremlin-Python stuff will not get into the next release. It > >>> has > > gotten really complex/powerful and is currently 100+ commits ahead of > > master/ ! :) .. As such, given the gargantuan undertaking, we will > >> save > > this work for a future release. > > > > Thanks, > > Marko. > > > > http://markorodriguez.com > > > > > > > >> On Jun 28, 2016, at 10:36 AM, Ted Wilmes > >> wrote: > >> > >> I would like to get TinkerPop-1254 in before code freeze. Shooting > >>> for > >> finishing it up by end of this week but I'll drop a note if it > >> looks > > like I > >> won't make it. > >> > >> --Ted > >> > >> On Tue, Jun 28, 2016 at 5:35 AM, Stephen Mallette < > spmalle...@gmail.com> > >> wrote: > >> > >>> It's end of June - time to start firming up for release. We have a > > number > >>> of outstanding PRs that need votes/merge. Perhaps we try to get > >>> those > > all > >>> in this week and begin code freeze next Monday (7/4)? > >>> > >>> I think we'll have to postpone the GLV work with gremlin-python > >> for > this > >>> release. There's just too much left to do to get that in "right". > >>> Are > > there > >>> any other open issues of importance? > >>> > >>> On Mon, Jun 6, 2016 at 9:18 AM, Marko Rodriguez < > >>> okramma...@gmail.com > > > >>> wrote: > >>> > Yes, end of June-ish is best for me as I have few things on my > >>> plate > > the > first half of this month. > > Thanks, > Marko. > > http://markorodriguez.com > > > > On Jun 6, 2016, at 4:46 AM, Stephen Mallette < > >>> spmalle...@gmail.com> > wrote: > > > > We didn't really discuss a date for release on this thread. I > >> was > thinking > > that we could start looking at the week of July 4th as the > >> target > week > for > > VOTE and nail down a date as we get closer. > > > > On Wed, May 25, 2016 at 2:42 PM, Jason Plurad < > >> plur...@gmail.com> > >>> wrote: > > > >> I'd think from a TinkerPop branding perspective, it probably > >>> helps > to > have > >> the name in there. It's Apache TinkerPop, not Apache Gremlin. > >> > >> I just took a quick look on a mirror, and some other Apache > projects > >> (Spark, Kafka, HBase, NiFi, Pig, Zookeeper) don't even include > apache > >>> in > >> their distributables, so maybe we can just do: > >> > >> tinkerpop-gremlin-console-x.y.z.zip > >> tinkerpop-gremlin-server-x.y.z.zip > >> > >> > >> On Wed, May 25, 2016 at 11:03 AM Stephen Mallette < > >>> spmalle...@gmail.com > > > >> wrote: > >> >
[GitHub] tinkerpop issue #356: TINKERPOP-1338 Bumped groovy to 2.4.7
Github user robertdale commented on the issue: https://github.com/apache/tinkerpop/pull/356 This PR does include #353 but not #354 . In the meantime, I'm setting up docker. Thanks. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: [DISCUSS] Thinking on Release
@Ted: When you get that PR out, I will immediately focus on reviewing it. Please make sure your branch has master/ merged into it so we know we know that if the code/design is good, then there won’t be any hiccups on merge. *** Also, benchmarks that dropping paths is “good” will be very important so hopefully you have that coming too. Thanks, Marko. http://markorodriguez.com > On Jul 6, 2016, at 8:07 AM, Stephen Mallette wrote: > > We're starting to go through reviews now with some earnest. Unless there > are concerns, I think that we should target code freeze for Friday at this > point. > > On Wed, Jul 6, 2016 at 10:01 AM, Ted Wilmes wrote: > >> Quick update, I plan on getting a PR in late tonight or tomorrow morning >> for 1254. >> >> Thanks, >> Ted >> >> On Fri, Jul 1, 2016 at 6:04 PM, Stephen Mallette >> wrote: >> >>> Thanks for the update Ted. We may need an extra day or two to clear up >> some >>> other discussion on some of the other PRs - i don't think we can start a >>> code freeze on Monday as I'd proposed. >>> >>> On Fri, Jul 1, 2016 at 6:49 PM, Ted Wilmes wrote: >>> Hi everyone, I had some time this week and made further progress on 1254. Still >>> working out some kinks but I'll see how far I can get over the weekend. Have a good 4th. --Ted On Tue, Jun 28, 2016 at 11:50 AM, Marko Rodriguez < >> okramma...@gmail.com> wrote: > Hi, > > Ted — I think we should get that work into the next release. Thus, if >>> you > need more time (reasonable amount), then I say we delay accordingly. > > NOTE: The Gremlin-Python stuff will not get into the next release. It >>> has > gotten really complex/powerful and is currently 100+ commits ahead of > master/ ! :) .. As such, given the gargantuan undertaking, we will >> save > this work for a future release. > > Thanks, > Marko. > > http://markorodriguez.com > > > >> On Jun 28, 2016, at 10:36 AM, Ted Wilmes >> wrote: >> >> I would like to get TinkerPop-1254 in before code freeze. Shooting >>> for >> finishing it up by end of this week but I'll drop a note if it >> looks > like I >> won't make it. >> >> --Ted >> >> On Tue, Jun 28, 2016 at 5:35 AM, Stephen Mallette < spmalle...@gmail.com> >> wrote: >> >>> It's end of June - time to start firming up for release. We have a > number >>> of outstanding PRs that need votes/merge. Perhaps we try to get >>> those > all >>> in this week and begin code freeze next Monday (7/4)? >>> >>> I think we'll have to postpone the GLV work with gremlin-python >> for this >>> release. There's just too much left to do to get that in "right". >>> Are > there >>> any other open issues of importance? >>> >>> On Mon, Jun 6, 2016 at 9:18 AM, Marko Rodriguez < >>> okramma...@gmail.com > >>> wrote: >>> Yes, end of June-ish is best for me as I have few things on my >>> plate > the first half of this month. Thanks, Marko. http://markorodriguez.com > On Jun 6, 2016, at 4:46 AM, Stephen Mallette < >>> spmalle...@gmail.com> wrote: > > We didn't really discuss a date for release on this thread. I >> was thinking > that we could start looking at the week of July 4th as the >> target week for > VOTE and nail down a date as we get closer. > > On Wed, May 25, 2016 at 2:42 PM, Jason Plurad < >> plur...@gmail.com> >>> wrote: > >> I'd think from a TinkerPop branding perspective, it probably >>> helps to have >> the name in there. It's Apache TinkerPop, not Apache Gremlin. >> >> I just took a quick look on a mirror, and some other Apache projects >> (Spark, Kafka, HBase, NiFi, Pig, Zookeeper) don't even include apache >>> in >> their distributables, so maybe we can just do: >> >> tinkerpop-gremlin-console-x.y.z.zip >> tinkerpop-gremlin-server-x.y.z.zip >> >> >> On Wed, May 25, 2016 at 11:03 AM Stephen Mallette < >>> spmalle...@gmail.com > >> wrote: >> >>> jason i think that was a suggestion to conform more to >> standard >>> apache >>> releases from someone in incubator. if it was mandatory we >> would > have >>> burned for that too many times to count at this point. i'm >> good >>> to change >>> it if everyone else is. what do we want them to be? >>> >>> apache-tinkerpop-console-x.y.z.zip >>> apache-tinkerpop-server-x.y.z.zip >>> >>> or the full business: >>> >>> apache-tinkerpop-gremlin-console-x.y.z.zip >>> apache-tinkerpop
Re: [DISCUSS] Thinking on Release
We're starting to go through reviews now with some earnest. Unless there are concerns, I think that we should target code freeze for Friday at this point. On Wed, Jul 6, 2016 at 10:01 AM, Ted Wilmes wrote: > Quick update, I plan on getting a PR in late tonight or tomorrow morning > for 1254. > > Thanks, > Ted > > On Fri, Jul 1, 2016 at 6:04 PM, Stephen Mallette > wrote: > > > Thanks for the update Ted. We may need an extra day or two to clear up > some > > other discussion on some of the other PRs - i don't think we can start a > > code freeze on Monday as I'd proposed. > > > > On Fri, Jul 1, 2016 at 6:49 PM, Ted Wilmes wrote: > > > > > Hi everyone, > > > I had some time this week and made further progress on 1254. Still > > working > > > out some kinks but I'll see how far I can get over the weekend. Have a > > > good 4th. > > > > > > --Ted > > > > > > On Tue, Jun 28, 2016 at 11:50 AM, Marko Rodriguez < > okramma...@gmail.com> > > > wrote: > > > > > > > Hi, > > > > > > > > Ted — I think we should get that work into the next release. Thus, if > > you > > > > need more time (reasonable amount), then I say we delay accordingly. > > > > > > > > NOTE: The Gremlin-Python stuff will not get into the next release. It > > has > > > > gotten really complex/powerful and is currently 100+ commits ahead of > > > > master/ ! :) .. As such, given the gargantuan undertaking, we will > save > > > > this work for a future release. > > > > > > > > Thanks, > > > > Marko. > > > > > > > > http://markorodriguez.com > > > > > > > > > > > > > > > > > On Jun 28, 2016, at 10:36 AM, Ted Wilmes > wrote: > > > > > > > > > > I would like to get TinkerPop-1254 in before code freeze. Shooting > > for > > > > > finishing it up by end of this week but I'll drop a note if it > looks > > > > like I > > > > > won't make it. > > > > > > > > > > --Ted > > > > > > > > > > On Tue, Jun 28, 2016 at 5:35 AM, Stephen Mallette < > > > spmalle...@gmail.com> > > > > > wrote: > > > > > > > > > >> It's end of June - time to start firming up for release. We have a > > > > number > > > > >> of outstanding PRs that need votes/merge. Perhaps we try to get > > those > > > > all > > > > >> in this week and begin code freeze next Monday (7/4)? > > > > >> > > > > >> I think we'll have to postpone the GLV work with gremlin-python > for > > > this > > > > >> release. There's just too much left to do to get that in "right". > > Are > > > > there > > > > >> any other open issues of importance? > > > > >> > > > > >> On Mon, Jun 6, 2016 at 9:18 AM, Marko Rodriguez < > > okramma...@gmail.com > > > > > > > > >> wrote: > > > > >> > > > > >>> Yes, end of June-ish is best for me as I have few things on my > > plate > > > > the > > > > >>> first half of this month. > > > > >>> > > > > >>> Thanks, > > > > >>> Marko. > > > > >>> > > > > >>> http://markorodriguez.com > > > > >>> > > > > >>> > > > > On Jun 6, 2016, at 4:46 AM, Stephen Mallette < > > spmalle...@gmail.com> > > > > >>> wrote: > > > > > > > > We didn't really discuss a date for release on this thread. I > was > > > > >>> thinking > > > > that we could start looking at the week of July 4th as the > target > > > week > > > > >>> for > > > > VOTE and nail down a date as we get closer. > > > > > > > > On Wed, May 25, 2016 at 2:42 PM, Jason Plurad < > plur...@gmail.com> > > > > >> wrote: > > > > > > > > > I'd think from a TinkerPop branding perspective, it probably > > helps > > > to > > > > >>> have > > > > > the name in there. It's Apache TinkerPop, not Apache Gremlin. > > > > > > > > > > I just took a quick look on a mirror, and some other Apache > > > projects > > > > > (Spark, Kafka, HBase, NiFi, Pig, Zookeeper) don't even include > > > apache > > > > >> in > > > > > their distributables, so maybe we can just do: > > > > > > > > > > tinkerpop-gremlin-console-x.y.z.zip > > > > > tinkerpop-gremlin-server-x.y.z.zip > > > > > > > > > > > > > > > On Wed, May 25, 2016 at 11:03 AM Stephen Mallette < > > > > >> spmalle...@gmail.com > > > > > > > > > wrote: > > > > > > > > > >> jason i think that was a suggestion to conform more to > standard > > > > >> apache > > > > >> releases from someone in incubator. if it was mandatory we > would > > > > have > > > > >> burned for that too many times to count at this point. i'm > good > > to > > > > >>> change > > > > >> it if everyone else is. what do we want them to be? > > > > >> > > > > >> apache-tinkerpop-console-x.y.z.zip > > > > >> apache-tinkerpop-server-x.y.z.zip > > > > >> > > > > >> or the full business: > > > > >> > > > > >> apache-tinkerpop-gremlin-console-x.y.z.zip > > > > >> apache-tinkerpop-gremlin-server-x.y.z.zip > > > > >> > > > > >> i guess we lost "-incubating" now so the latter doesn't look > so > > > bad > > > > >> to > > > > >>> me > > > > >> anymore. > > > > >> > > > > >> > > > > >
[jira] [Commented] (TINKERPOP-1319) several FeatureRequirement annotations are incorrect in gremlin-test
[ https://issues.apache.org/jira/browse/TINKERPOP-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364346#comment-15364346 ] ASF GitHub Bot commented on TINKERPOP-1319: --- Github user dkuppitz commented on the issue: https://github.com/apache/tinkerpop/pull/335 `docker/build.sh -t -i -n` fails for me in Spark Gremlin. > several FeatureRequirement annotations are incorrect in gremlin-test > > > Key: TINKERPOP-1319 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1319 > Project: TinkerPop > Issue Type: Bug > Components: test-suite >Affects Versions: 3.2.0-incubating, 3.1.2-incubating >Reporter: Jason Plurad >Assignee: Jason Plurad >Priority: Minor > Fix For: 3.1.3, 3.2.1 > > > Several {{@FeatureRequirement}} annotations are incorrect in these > {{gremlin-test}} tests > * EdgeTest.java > * FeatureSupportTest.java > * GraphTest.java > * PropertyTest.java > * VertexPropertyTest.java > * VertexTest.java > I'll submit a patch for this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] tinkerpop issue #335: TINKERPOP-1319: fix incorrect FeatureRequirement annot...
Github user dkuppitz commented on the issue: https://github.com/apache/tinkerpop/pull/335 `docker/build.sh -t -i -n` fails for me in Spark Gremlin. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: [DISCUSS] Thinking on Release
Quick update, I plan on getting a PR in late tonight or tomorrow morning for 1254. Thanks, Ted On Fri, Jul 1, 2016 at 6:04 PM, Stephen Mallette wrote: > Thanks for the update Ted. We may need an extra day or two to clear up some > other discussion on some of the other PRs - i don't think we can start a > code freeze on Monday as I'd proposed. > > On Fri, Jul 1, 2016 at 6:49 PM, Ted Wilmes wrote: > > > Hi everyone, > > I had some time this week and made further progress on 1254. Still > working > > out some kinks but I'll see how far I can get over the weekend. Have a > > good 4th. > > > > --Ted > > > > On Tue, Jun 28, 2016 at 11:50 AM, Marko Rodriguez > > wrote: > > > > > Hi, > > > > > > Ted — I think we should get that work into the next release. Thus, if > you > > > need more time (reasonable amount), then I say we delay accordingly. > > > > > > NOTE: The Gremlin-Python stuff will not get into the next release. It > has > > > gotten really complex/powerful and is currently 100+ commits ahead of > > > master/ ! :) .. As such, given the gargantuan undertaking, we will save > > > this work for a future release. > > > > > > Thanks, > > > Marko. > > > > > > http://markorodriguez.com > > > > > > > > > > > > > On Jun 28, 2016, at 10:36 AM, Ted Wilmes wrote: > > > > > > > > I would like to get TinkerPop-1254 in before code freeze. Shooting > for > > > > finishing it up by end of this week but I'll drop a note if it looks > > > like I > > > > won't make it. > > > > > > > > --Ted > > > > > > > > On Tue, Jun 28, 2016 at 5:35 AM, Stephen Mallette < > > spmalle...@gmail.com> > > > > wrote: > > > > > > > >> It's end of June - time to start firming up for release. We have a > > > number > > > >> of outstanding PRs that need votes/merge. Perhaps we try to get > those > > > all > > > >> in this week and begin code freeze next Monday (7/4)? > > > >> > > > >> I think we'll have to postpone the GLV work with gremlin-python for > > this > > > >> release. There's just too much left to do to get that in "right". > Are > > > there > > > >> any other open issues of importance? > > > >> > > > >> On Mon, Jun 6, 2016 at 9:18 AM, Marko Rodriguez < > okramma...@gmail.com > > > > > > >> wrote: > > > >> > > > >>> Yes, end of June-ish is best for me as I have few things on my > plate > > > the > > > >>> first half of this month. > > > >>> > > > >>> Thanks, > > > >>> Marko. > > > >>> > > > >>> http://markorodriguez.com > > > >>> > > > >>> > > > On Jun 6, 2016, at 4:46 AM, Stephen Mallette < > spmalle...@gmail.com> > > > >>> wrote: > > > > > > We didn't really discuss a date for release on this thread. I was > > > >>> thinking > > > that we could start looking at the week of July 4th as the target > > week > > > >>> for > > > VOTE and nail down a date as we get closer. > > > > > > On Wed, May 25, 2016 at 2:42 PM, Jason Plurad > > > >> wrote: > > > > > > > I'd think from a TinkerPop branding perspective, it probably > helps > > to > > > >>> have > > > > the name in there. It's Apache TinkerPop, not Apache Gremlin. > > > > > > > > I just took a quick look on a mirror, and some other Apache > > projects > > > > (Spark, Kafka, HBase, NiFi, Pig, Zookeeper) don't even include > > apache > > > >> in > > > > their distributables, so maybe we can just do: > > > > > > > > tinkerpop-gremlin-console-x.y.z.zip > > > > tinkerpop-gremlin-server-x.y.z.zip > > > > > > > > > > > > On Wed, May 25, 2016 at 11:03 AM Stephen Mallette < > > > >> spmalle...@gmail.com > > > > > > > wrote: > > > > > > > >> jason i think that was a suggestion to conform more to standard > > > >> apache > > > >> releases from someone in incubator. if it was mandatory we would > > > have > > > >> burned for that too many times to count at this point. i'm good > to > > > >>> change > > > >> it if everyone else is. what do we want them to be? > > > >> > > > >> apache-tinkerpop-console-x.y.z.zip > > > >> apache-tinkerpop-server-x.y.z.zip > > > >> > > > >> or the full business: > > > >> > > > >> apache-tinkerpop-gremlin-console-x.y.z.zip > > > >> apache-tinkerpop-gremlin-server-x.y.z.zip > > > >> > > > >> i guess we lost "-incubating" now so the latter doesn't look so > > bad > > > >> to > > > >>> me > > > >> anymore. > > > >> > > > >> > > > >> On Wed, May 25, 2016 at 10:56 AM, Marko Rodriguez < > > > >>> okramma...@gmail.com> > > > >> wrote: > > > >> > > > >>> Hi, > > > >>> > > > >>> Yes, an imminent release is good. There are 2 severe bug fixes > in > > > > master/ > > > >>> (3.2.1) that I would like to get out there. 3.2.0 had lots of > > > >> internal > > > >>> changes to OLAP and I paid the price by incurring bugs. :| > > > >>> > > > Somebody had mentioned that our distributables are supposed to > > be > > > > named > > > apache-tinkerpop*.zip i
[jira] [Commented] (TINKERPOP-1338) Bump to Groovy 2.4.7
[ https://issues.apache.org/jira/browse/TINKERPOP-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364332#comment-15364332 ] ASF GitHub Bot commented on TINKERPOP-1338: --- Github user spmallette commented on the issue: https://github.com/apache/tinkerpop/pull/356 looks like this is failing in master too..so it's unrelated to your change. we will need to get that fixed and at that point you should rebase and try to full integration tests suite. i'll post back here when that's fixed on master > Bump to Groovy 2.4.7 > > > Key: TINKERPOP-1338 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1338 > Project: TinkerPop > Issue Type: Improvement > Components: groovy >Affects Versions: 3.2.0-incubating >Reporter: stephen mallette >Priority: Minor > Fix For: 3.2.1 > > > Provides a number of bug fixes: > http://groovy-lang.org/changelogs/changelog-2.4.7.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] tinkerpop issue #356: TINKERPOP-1338 Bumped groovy to 2.4.7
Github user spmallette commented on the issue: https://github.com/apache/tinkerpop/pull/356 looks like this is failing in master too..so it's unrelated to your change. we will need to get that fixed and at that point you should rebase and try to full integration tests suite. i'll post back here when that's fixed on master --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (TINKERPOP-1319) several FeatureRequirement annotations are incorrect in gremlin-test
[ https://issues.apache.org/jira/browse/TINKERPOP-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364316#comment-15364316 ] ASF GitHub Bot commented on TINKERPOP-1319: --- Github user okram commented on the issue: https://github.com/apache/tinkerpop/pull/335 VOTE +1 > several FeatureRequirement annotations are incorrect in gremlin-test > > > Key: TINKERPOP-1319 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1319 > Project: TinkerPop > Issue Type: Bug > Components: test-suite >Affects Versions: 3.2.0-incubating, 3.1.2-incubating >Reporter: Jason Plurad >Assignee: Jason Plurad >Priority: Minor > Fix For: 3.1.3, 3.2.1 > > > Several {{@FeatureRequirement}} annotations are incorrect in these > {{gremlin-test}} tests > * EdgeTest.java > * FeatureSupportTest.java > * GraphTest.java > * PropertyTest.java > * VertexPropertyTest.java > * VertexTest.java > I'll submit a patch for this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] tinkerpop issue #335: TINKERPOP-1319: fix incorrect FeatureRequirement annot...
Github user okram commented on the issue: https://github.com/apache/tinkerpop/pull/335 VOTE +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] tinkerpop issue #346: ResultSet.hasNext should be idempotent
Github user okram commented on the issue: https://github.com/apache/tinkerpop/pull/346 Smart. VOTE +1. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (TINKERPOP-1350) Server locks when submitting parallel requests on session
[ https://issues.apache.org/jira/browse/TINKERPOP-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364314#comment-15364314 ] ASF GitHub Bot commented on TINKERPOP-1350: --- Github user okram commented on the issue: https://github.com/apache/tinkerpop/pull/350 VOTE +1 > Server locks when submitting parallel requests on session > - > > Key: TINKERPOP-1350 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1350 > Project: TinkerPop > Issue Type: Bug > Components: server >Affects Versions: 3.1.2-incubating >Reporter: stephen mallette >Assignee: stephen mallette >Priority: Critical > Fix For: 3.1.3, 3.2.1 > > > This really is only a problem when there is some form of long blocking script > submitted and only on a session when done in parallel, like: > {code} > final ResultSet first = client.submit( > "Object mon1 = 'mon1';\n" + > "synchronized (mon1) {\n" + > "mon1.wait();\n" + > "} "); > final ResultSet second = client.submit( > "Object mon2 = 'mon2';\n" + > "synchronized (mon2) {\n" + > "mon2.wait();\n" + > "}"); > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TINKERPOP-1354) Include all static enum imports in request validation for bindings
[ https://issues.apache.org/jira/browse/TINKERPOP-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364313#comment-15364313 ] ASF GitHub Bot commented on TINKERPOP-1354: --- Github user okram commented on the issue: https://github.com/apache/tinkerpop/pull/354 VOTE +1 > Include all static enum imports in request validation for bindings > -- > > Key: TINKERPOP-1354 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1354 > Project: TinkerPop > Issue Type: Improvement > Components: server >Affects Versions: 3.1.2-incubating >Reporter: stephen mallette >Assignee: stephen mallette >Priority: Minor > Labels: breaking > Fix For: 3.1.3, 3.2.1 > > > Gremlin Server validates the bindings of incoming requests and returns an > error for any reserved terms. The list of reserved terms only includes {{T}} > but should also include others like {{Order}} and {{Scope}} so that users > don't inadvertently override them with a request binding. When that happens > Gremlin Server throws a not so easy to understand error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] tinkerpop issue #350: TINKERPOP-1350 Fixed a problem with how timeouts were ...
Github user okram commented on the issue: https://github.com/apache/tinkerpop/pull/350 VOTE +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] tinkerpop issue #354: TINKERPOP-1354 Added more invalid binding keys to Grem...
Github user okram commented on the issue: https://github.com/apache/tinkerpop/pull/354 VOTE +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (TINKERPOP-1338) Bump to Groovy 2.4.7
[ https://issues.apache.org/jira/browse/TINKERPOP-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364310#comment-15364310 ] ASF GitHub Bot commented on TINKERPOP-1338: --- Github user spmallette commented on the issue: https://github.com/apache/tinkerpop/pull/356 Note that it's not sufficient in this case to only run gremlin server integration tests. You should probably run the whole suite. When i run that with docker via `docker/build.sh -t -i -n` i get tons of: ```text Caused by: java.lang.IllegalArgumentException: Unable to create serializer "com.esotericsoftware.kryo.serializers.FieldSerializer" for class: void at com.esotericsoftware.kryo.Kryo.newSerializer(Kryo.java:335) at com.esotericsoftware.kryo.Kryo.newDefaultSerializer(Kryo.java:314) at com.twitter.chill.KryoBase.newDefaultSerializer(KryoBase.scala:48) at com.esotericsoftware.kryo.Kryo.getDefaultSerializer(Kryo.java:307) at com.esotericsoftware.kryo.Kryo.register(Kryo.java:351) at org.apache.tinkerpop.gremlin.spark.structure.io.gryo.GryoRegistrator.registerClasses(GryoRegistrator.java:94) at org.apache.tinkerpop.gremlin.spark.structure.io.gryo.GryoRegistrator.registerClasses(GryoRegistrator.java:65) at org.apache.spark.serializer.KryoSerializer$$anonfun$newKryo$6.apply(KryoSerializer.scala:124) at org.apache.spark.serializer.KryoSerializer$$anonfun$newKryo$6.apply(KryoSerializer.scala:124) at scala.Option.foreach(Option.scala:236) at org.apache.spark.serializer.KryoSerializer.newKryo(KryoSerializer.scala:124) at org.apache.tinkerpop.gremlin.spark.structure.io.gryo.IoRegistryAwareKryoSerializer.newKryo(IoRegistryAwareKryoSerializer.java:57) at org.apache.tinkerpop.gremlin.spark.structure.io.gryo.kryoshim.unshaded.UnshadedKryoShimService.initialize(UnshadedKryoShimService.java:144) at org.apache.tinkerpop.gremlin.spark.structure.io.gryo.kryoshim.unshaded.UnshadedKryoShimService.applyConfiguration(UnshadedKryoShimService.java:106) at org.apache.tinkerpop.gremlin.structure.io.gryo.kryoshim.KryoShimServiceLoader.load(KryoShimServiceLoader.java:125) at org.apache.tinkerpop.gremlin.spark.process.computer.SparkHadoopGraphGryoRegistratorProvider.getBaseConfiguration(SparkHadoopGraphGryoRegistratorProvider.java:48) at org.apache.tinkerpop.gremlin.AbstractGraphProvider.newGraphConfiguration(AbstractGraphProvider.java:70) at org.apache.tinkerpop.gremlin.GraphProvider.standardGraphConfiguration(GraphProvider.java:144) at org.apache.tinkerpop.gremlin.GraphManager$ManagedGraphProvider.standardGraphConfiguration(GraphManager.java:132) at org.apache.tinkerpop.gremlin.AbstractGremlinTest.setup(AbstractGremlinTest.java:81) at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.junit.rules.RunRules.evaluate(RunRules.java:20) at org.apache.tinkerpop.gremlin.process.GremlinProcessRunner.runChild(GremlinProcessRunner.java:54) at org.apache.tinkerpop.gremlin.process.GremlinProcessRunner.runChild(GremlinProcessRunner.java:37) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.junit.runners.Suite.runChild(Suite.java:128) at org.apache.tinkerpop.gremlin.AbstractGremlinSuite.runChild(AbstractGremlinSuite.java:212) at org.apache.tinkerpop.gremlin.AbstractGremlinSuite.runChild(AbstractGremlinSuite.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRu
[GitHub] tinkerpop issue #356: TINKERPOP-1338 Bumped groovy to 2.4.7
Github user spmallette commented on the issue: https://github.com/apache/tinkerpop/pull/356 Note that it's not sufficient in this case to only run gremlin server integration tests. You should probably run the whole suite. When i run that with docker via `docker/build.sh -t -i -n` i get tons of: ```text Caused by: java.lang.IllegalArgumentException: Unable to create serializer "com.esotericsoftware.kryo.serializers.FieldSerializer" for class: void at com.esotericsoftware.kryo.Kryo.newSerializer(Kryo.java:335) at com.esotericsoftware.kryo.Kryo.newDefaultSerializer(Kryo.java:314) at com.twitter.chill.KryoBase.newDefaultSerializer(KryoBase.scala:48) at com.esotericsoftware.kryo.Kryo.getDefaultSerializer(Kryo.java:307) at com.esotericsoftware.kryo.Kryo.register(Kryo.java:351) at org.apache.tinkerpop.gremlin.spark.structure.io.gryo.GryoRegistrator.registerClasses(GryoRegistrator.java:94) at org.apache.tinkerpop.gremlin.spark.structure.io.gryo.GryoRegistrator.registerClasses(GryoRegistrator.java:65) at org.apache.spark.serializer.KryoSerializer$$anonfun$newKryo$6.apply(KryoSerializer.scala:124) at org.apache.spark.serializer.KryoSerializer$$anonfun$newKryo$6.apply(KryoSerializer.scala:124) at scala.Option.foreach(Option.scala:236) at org.apache.spark.serializer.KryoSerializer.newKryo(KryoSerializer.scala:124) at org.apache.tinkerpop.gremlin.spark.structure.io.gryo.IoRegistryAwareKryoSerializer.newKryo(IoRegistryAwareKryoSerializer.java:57) at org.apache.tinkerpop.gremlin.spark.structure.io.gryo.kryoshim.unshaded.UnshadedKryoShimService.initialize(UnshadedKryoShimService.java:144) at org.apache.tinkerpop.gremlin.spark.structure.io.gryo.kryoshim.unshaded.UnshadedKryoShimService.applyConfiguration(UnshadedKryoShimService.java:106) at org.apache.tinkerpop.gremlin.structure.io.gryo.kryoshim.KryoShimServiceLoader.load(KryoShimServiceLoader.java:125) at org.apache.tinkerpop.gremlin.spark.process.computer.SparkHadoopGraphGryoRegistratorProvider.getBaseConfiguration(SparkHadoopGraphGryoRegistratorProvider.java:48) at org.apache.tinkerpop.gremlin.AbstractGraphProvider.newGraphConfiguration(AbstractGraphProvider.java:70) at org.apache.tinkerpop.gremlin.GraphProvider.standardGraphConfiguration(GraphProvider.java:144) at org.apache.tinkerpop.gremlin.GraphManager$ManagedGraphProvider.standardGraphConfiguration(GraphManager.java:132) at org.apache.tinkerpop.gremlin.AbstractGremlinTest.setup(AbstractGremlinTest.java:81) at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.junit.rules.RunRules.evaluate(RunRules.java:20) at org.apache.tinkerpop.gremlin.process.GremlinProcessRunner.runChild(GremlinProcessRunner.java:54) at org.apache.tinkerpop.gremlin.process.GremlinProcessRunner.runChild(GremlinProcessRunner.java:37) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.junit.runners.Suite.runChild(Suite.java:128) at org.apache.tinkerpop.gremlin.AbstractGremlinSuite.runChild(AbstractGremlinSuite.java:212) at org.apache.tinkerpop.gremlin.AbstractGremlinSuite.runChild(AbstractGremlinSuite.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) at org.apache.maven.surefire.junit4.JUnit4Provider.execute
[jira] [Commented] (TINKERPOP-1350) Server locks when submitting parallel requests on session
[ https://issues.apache.org/jira/browse/TINKERPOP-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364261#comment-15364261 ] ASF GitHub Bot commented on TINKERPOP-1350: --- Github user dkuppitz commented on the issue: https://github.com/apache/tinkerpop/pull/350 VOTE: +1 > Server locks when submitting parallel requests on session > - > > Key: TINKERPOP-1350 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1350 > Project: TinkerPop > Issue Type: Bug > Components: server >Affects Versions: 3.1.2-incubating >Reporter: stephen mallette >Assignee: stephen mallette >Priority: Critical > Fix For: 3.1.3, 3.2.1 > > > This really is only a problem when there is some form of long blocking script > submitted and only on a session when done in parallel, like: > {code} > final ResultSet first = client.submit( > "Object mon1 = 'mon1';\n" + > "synchronized (mon1) {\n" + > "mon1.wait();\n" + > "} "); > final ResultSet second = client.submit( > "Object mon2 = 'mon2';\n" + > "synchronized (mon2) {\n" + > "mon2.wait();\n" + > "}"); > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] tinkerpop issue #350: TINKERPOP-1350 Fixed a problem with how timeouts were ...
Github user dkuppitz commented on the issue: https://github.com/apache/tinkerpop/pull/350 VOTE: +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (TINKERPOP-1354) Include all static enum imports in request validation for bindings
[ https://issues.apache.org/jira/browse/TINKERPOP-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364222#comment-15364222 ] ASF GitHub Bot commented on TINKERPOP-1354: --- Github user dkuppitz commented on the issue: https://github.com/apache/tinkerpop/pull/354 VOTE: +1 > Include all static enum imports in request validation for bindings > -- > > Key: TINKERPOP-1354 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1354 > Project: TinkerPop > Issue Type: Improvement > Components: server >Affects Versions: 3.1.2-incubating >Reporter: stephen mallette >Assignee: stephen mallette >Priority: Minor > Labels: breaking > Fix For: 3.1.3, 3.2.1 > > > Gremlin Server validates the bindings of incoming requests and returns an > error for any reserved terms. The list of reserved terms only includes {{T}} > but should also include others like {{Order}} and {{Scope}} so that users > don't inadvertently override them with a request binding. When that happens > Gremlin Server throws a not so easy to understand error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] tinkerpop issue #354: TINKERPOP-1354 Added more invalid binding keys to Grem...
Github user dkuppitz commented on the issue: https://github.com/apache/tinkerpop/pull/354 VOTE: +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (TINKERPOP-1320) GremlinGroovyScriptEngineFileSandboxTest throws error: URI is not hierarchical
[ https://issues.apache.org/jira/browse/TINKERPOP-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364213#comment-15364213 ] ASF GitHub Bot commented on TINKERPOP-1320: --- Github user dkuppitz commented on the issue: https://github.com/apache/tinkerpop/pull/336 VOTE: +1 > GremlinGroovyScriptEngineFileSandboxTest throws error: URI is not hierarchical > -- > > Key: TINKERPOP-1320 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1320 > Project: TinkerPop > Issue Type: Bug > Components: test-suite >Affects Versions: 3.2.0-incubating, 3.1.2-incubating >Reporter: Jason Plurad >Assignee: Jason Plurad >Priority: Minor > Fix For: 3.1.3, 3.2.1 > > > This is similar to TINKERPOP-1317. The differences here are > * The {{TestHelper.generateTempFileFromResource()}} call to load the resource > is happening from the {{public static void init()}} method before a graph > instance is available. > * A reference to {{GremlinGroovyScriptEngineFileSandboxTest.class}} is still > required to located the {{sandbox.yaml}} found in the {{gremlin-test.jar}}. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] tinkerpop issue #336: TINKERPOP-1320 fix GremlinGroovyScriptEngineFileSandbo...
Github user dkuppitz commented on the issue: https://github.com/apache/tinkerpop/pull/336 VOTE: +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Closed] (TINKERPOP-1355) Design HasContainer for extension
[ https://issues.apache.org/jira/browse/TINKERPOP-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kuppitz closed TINKERPOP-1355. - Resolution: Fixed Fix Version/s: 3.2.1 > Design HasContainer for extension > - > > Key: TINKERPOP-1355 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1355 > Project: TinkerPop > Issue Type: Improvement > Components: process >Affects Versions: 3.2.0-incubating >Reporter: Bryn Cooke >Priority: Critical > Fix For: 3.2.1 > > > Currently HasContainer is final. This means that Graph implementations cannot > support their own type systems across the entire traversal. > Given the traversal: > g.V.has('foo', nonTinkerpopType).out('bar').has('foo', nonTinkerpopType) > Say that the initial traversal g.V.has('foo', nonTinkerpopType) is dealt with > via strategy, the non-Tinkerpop type can be dealt with. However the rest of > the traversal is processed via the default Tinkerpop pipeline, and as such it > doesn't know how to deal with type conversions/comparisons etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TINKERPOP-1355) Design HasContainer for extension
[ https://issues.apache.org/jira/browse/TINKERPOP-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364139#comment-15364139 ] ASF GitHub Bot commented on TINKERPOP-1355: --- Github user asfgit closed the pull request at: https://github.com/apache/tinkerpop/pull/355 > Design HasContainer for extension > - > > Key: TINKERPOP-1355 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1355 > Project: TinkerPop > Issue Type: Improvement > Components: process >Affects Versions: 3.2.0-incubating >Reporter: Bryn Cooke >Priority: Critical > > Currently HasContainer is final. This means that Graph implementations cannot > support their own type systems across the entire traversal. > Given the traversal: > g.V.has('foo', nonTinkerpopType).out('bar').has('foo', nonTinkerpopType) > Say that the initial traversal g.V.has('foo', nonTinkerpopType) is dealt with > via strategy, the non-Tinkerpop type can be dealt with. However the rest of > the traversal is processed via the default Tinkerpop pipeline, and as such it > doesn't know how to deal with type conversions/comparisons etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] tinkerpop pull request #355: TINKERPOP-1355 Design HasContainer for extensio...
Github user asfgit closed the pull request at: https://github.com/apache/tinkerpop/pull/355 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (TINKERPOP-1355) Design HasContainer for extension
[ https://issues.apache.org/jira/browse/TINKERPOP-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364130#comment-15364130 ] ASF GitHub Bot commented on TINKERPOP-1355: --- Github user spmallette commented on the issue: https://github.com/apache/tinkerpop/pull/355 VOTE +1 > Design HasContainer for extension > - > > Key: TINKERPOP-1355 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1355 > Project: TinkerPop > Issue Type: Improvement > Components: process >Affects Versions: 3.2.0-incubating >Reporter: Bryn Cooke >Priority: Critical > > Currently HasContainer is final. This means that Graph implementations cannot > support their own type systems across the entire traversal. > Given the traversal: > g.V.has('foo', nonTinkerpopType).out('bar').has('foo', nonTinkerpopType) > Say that the initial traversal g.V.has('foo', nonTinkerpopType) is dealt with > via strategy, the non-Tinkerpop type can be dealt with. However the rest of > the traversal is processed via the default Tinkerpop pipeline, and as such it > doesn't know how to deal with type conversions/comparisons etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] tinkerpop issue #355: TINKERPOP-1355 Design HasContainer for extension
Github user spmallette commented on the issue: https://github.com/apache/tinkerpop/pull/355 VOTE +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---