[
https://issues.apache.org/jira/browse/TINKERPOP3-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14948012#comment-14948012
]
Matt Frantz commented on TINKERPOP3-793:
If you want an exception, yes, the cu
[
https://issues.apache.org/jira/browse/TINKERPOP3-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947939#comment-14947939
]
Marko A. Rodriguez commented on TINKERPOP3-793:
---
I dunno. I think the ex
[
https://issues.apache.org/jira/browse/TINKERPOP3-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947937#comment-14947937
]
Marko A. Rodriguez commented on TINKERPOP3-871:
---
Sorry -- this would liv
[
https://issues.apache.org/jira/browse/TINKERPOP3-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947935#comment-14947935
]
Marko A. Rodriguez commented on TINKERPOP3-798:
---
Note that we would simp
[
https://issues.apache.org/jira/browse/TINKERPOP3-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947935#comment-14947935
]
Marko A. Rodriguez edited comment on TINKERPOP3-798 at 10/8/15 1:43 AM:
Hey,
> What exactly is being optimized by replacing two classes with a single
> class that has two modes?
I want to make Gremlin's instruction set as small as possible. This way,
implementers (previously known as vendors) don't have to write so many custom
steps/strategies for their graph syste
[
https://issues.apache.org/jira/browse/TINKERPOP3-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947905#comment-14947905
]
Marko A. Rodriguez commented on TINKERPOP3-798:
---
I was thinking some oth
[
https://issues.apache.org/jira/browse/TINKERPOP3-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947885#comment-14947885
]
Matt Frantz commented on TINKERPOP3-871:
I'm not sure I completely grok your s
[
https://issues.apache.org/jira/browse/TINKERPOP3-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947878#comment-14947878
]
Matt Frantz commented on TINKERPOP3-793:
If you think about framing this propo
[
https://issues.apache.org/jira/browse/TINKERPOP3-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947874#comment-14947874
]
Matt Frantz commented on TINKERPOP3-793:
The {{select}} logic has been "all" s
[
https://issues.apache.org/jira/browse/TINKERPOP3-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947869#comment-14947869
]
Matt Frantz commented on TINKERPOP3-793:
If you showed the traversal with the
What exactly is being optimized by replacing two classes with a single
class that has two modes? Are there cases where you can perform
optimizations without caring about the mode? Why not an abstract GroupStep
with two concrete subclasses? My understanding of this code is somewhat
superficial, s
[
https://issues.apache.org/jira/browse/TINKERPOP3-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947854#comment-14947854
]
Matt Frantz commented on TINKERPOP3-873:
This feels related to TINKERPOP3-787
[
https://issues.apache.org/jira/browse/TINKERPOP3-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947851#comment-14947851
]
Matt Frantz commented on TINKERPOP3-873:
Why is {{BulkSet}} more efficient?
{
[
https://issues.apache.org/jira/browse/TINKERPOP3-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Frantz updated TINKERPOP3-873:
---
Labels: breaking (was: )
> FoldStep should default to using BulkSet for efficiency.
> ---
[
https://issues.apache.org/jira/browse/TINKERPOP3-844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947845#comment-14947845
]
Matt Frantz commented on TINKERPOP3-844:
How about an overload of {{properties
[
https://issues.apache.org/jira/browse/TINKERPOP3-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947830#comment-14947830
]
Matt Frantz commented on TINKERPOP3-798:
Are {{keys}} and {{values}} new {{Sco
I think it fits with the general purpose of {{select}}, and it doesn't
introduce any new Java overloads. FTW
On Wed, Oct 7, 2015 at 12:37 PM, Marko Rodriguez
wrote:
> No, easy deprecation.
>
> Marko.
>
> http://markorodriguez.com
>
> On Oct 7, 2015, at 1:13 PM, Stephen Mallette wrote:
>
> > Tha
[
https://issues.apache.org/jira/browse/TINKERPOP3-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947824#comment-14947824
]
Matt Frantz commented on TINKERPOP3-716:
I'm working on a doc that provides th
[
https://issues.apache.org/jira/browse/TINKERPOP3-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947812#comment-14947812
]
Matt Frantz commented on TINKERPOP3-861:
I've been scratching my head over the
[
https://issues.apache.org/jira/browse/TINKERPOP3-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947798#comment-14947798
]
Marko A. Rodriguez commented on TINKERPOP3-871:
---
Nice idea. However, can
[
https://issues.apache.org/jira/browse/TINKERPOP3-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947795#comment-14947795
]
Daniel Kuppitz commented on TINKERPOP3-793:
---
I don't see this one as critica
Marko A. Rodriguez created TINKERPOP3-874:
-
Summary: Rename Gremlin-Spark properties using gremlin.spark
prefix.
Key: TINKERPOP3-874
URL: https://issues.apache.org/jira/browse/TINKERPOP3-874
P
[
https://issues.apache.org/jira/browse/TINKERPOP3-874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947794#comment-14947794
]
Russell Alexander Spitzer commented on TINKERPOP3-874:
--
+1
> Ren
[
https://issues.apache.org/jira/browse/TINKERPOP3-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947791#comment-14947791
]
Matt Frantz commented on TINKERPOP3-871:
I've been thinking about polymorphism
[
https://issues.apache.org/jira/browse/TINKERPOP3-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marko A. Rodriguez updated TINKERPOP3-793:
--
Labels: breaking (was: )
> select should stop traversal on unproductive by
[
https://issues.apache.org/jira/browse/TINKERPOP3-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947707#comment-14947707
]
Marko A. Rodriguez commented on TINKERPOP3-793:
---
You know what else we d
[
https://issues.apache.org/jira/browse/TINKERPOP3-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947700#comment-14947700
]
Daniel Kuppitz commented on TINKERPOP3-793:
---
I agree. Either {{filter}} or {
Hi,
So I branched and implemented this.
https://github.com/apache/incubator-tinkerpop/tree/TINKERPOP3-872
Dead simple implementation.
https://github.com/apache/incubator-tinkerpop/commit/db1cd97e3ec98938961e394489dd902acbb3009f
The one thing I don't like is the GroupStep(boolean
Marko A. Rodriguez created TINKERPOP3-873:
-
Summary: FoldStep should default to using BulkSet for efficiency.
Key: TINKERPOP3-873
URL: https://issues.apache.org/jira/browse/TINKERPOP3-873
Proje
[
https://issues.apache.org/jira/browse/TINKERPOP3-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marko A. Rodriguez closed TINKERPOP3-866.
-
Resolution: Fixed
This has been implemented. There is no perfect backwards com
[
https://issues.apache.org/jira/browse/TINKERPOP3-844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947409#comment-14947409
]
Marko A. Rodriguez edited comment on TINKERPOP3-844 at 10/7/15 8:20 PM:
[
https://issues.apache.org/jira/browse/TINKERPOP3-872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marko A. Rodriguez updated TINKERPOP3-872:
--
Description:
Check it. In the {{group_step_2/}} branch, we can now do this e
[
https://issues.apache.org/jira/browse/TINKERPOP3-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947460#comment-14947460
]
Marko A. Rodriguez commented on TINKERPOP3-793:
---
Everytime I go to do th
No, easy deprecation.
Marko.
http://markorodriguez.com
On Oct 7, 2015, at 1:13 PM, Stephen Mallette wrote:
> That one looks like an easy candidate for deprecation of mapKeys and
> selectKeys? or is removing the flatten behavior going to ultimately break
> the semantics of how that all operat
Hello,
Check it:
https://issues.apache.org/jira/browse/TINKERPOP3-872
GraphTraversal.groupCount() just uses GroupStep. Why is this so cool? Well,
cause there are two groupCounts() -- GroupCountStep and GroupSideEffectStep.
Two steps we don't have to maintain and we can focus our energie
Marko A. Rodriguez created TINKERPOP3-872:
-
Summary: Remove GroupCountStep in favor of new Reduce-based
GroupStep
Key: TINKERPOP3-872
URL: https://issues.apache.org/jira/browse/TINKERPOP3-872
[
https://issues.apache.org/jira/browse/TINKERPOP3-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947437#comment-14947437
]
Marko A. Rodriguez commented on TINKERPOP3-716:
---
I was thinking about th
[
https://issues.apache.org/jira/browse/TINKERPOP3-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947435#comment-14947435
]
David M. Brown commented on TINKERPOP3-869:
---
Yes mocking seems like a good o
[
https://issues.apache.org/jira/browse/TINKERPOP3-861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marko A. Rodriguez updated TINKERPOP3-861:
--
Issue Type: Improvement (was: Bug)
> Solve "The Number Problem" for Operato
[
https://issues.apache.org/jira/browse/TINKERPOP3-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947423#comment-14947423
]
Marko A. Rodriguez commented on TINKERPOP3-861:
---
Any progress on this [~
Hi dev@,
I'm still interested in someone taking the reigns on:
https://issues.apache.org/jira/browse/TINKERPOP3-841
Marko.
http://markorodriguez.com
On Sep 11, 2015, at 9:14 AM, Marko Rodriguez wrote:
> Hello,
>
> After the overwhelming support for having TinkerPop3 support Hadoop2,
[
https://issues.apache.org/jira/browse/TINKERPOP3-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947418#comment-14947418
]
stephen mallette commented on TINKERPOP3-869:
-
Interesting point [~davebsh
[
https://issues.apache.org/jira/browse/TINKERPOP3-844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947409#comment-14947409
]
Marko A. Rodriguez commented on TINKERPOP3-844:
---
Its interesting as we c
[
https://issues.apache.org/jira/browse/TINKERPOP3-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947401#comment-14947401
]
David M. Brown commented on TINKERPOP3-869:
---
A few thoughts and questions:
[
https://issues.apache.org/jira/browse/TINKERPOP3-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947401#comment-14947401
]
David M. Brown edited comment on TINKERPOP3-869 at 10/7/15 7:13 PM:
That one looks like an easy candidate for deprecation of mapKeys and
selectKeys? or is removing the flatten behavior going to ultimately break
the semantics of how that all operates?
On Wed, Oct 7, 2015 at 2:57 PM, Marko Rodriguez
wrote:
> Hello,
>
> Please see this ticket:
> https://is
[
https://issues.apache.org/jira/browse/TINKERPOP3-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marko A. Rodriguez closed TINKERPOP3-829.
-
Resolution: Fixed
Fix Version/s: 3.1.0-incubating
This has been fixed.
Hello,
https://issues.apache.org/jira/browse/TINKERPOP3-871
This is a good one. We currently use the idea of a "runtime strategy" for
MatchStep. What about OrStep, AndStep… others?
Thoughts?,
Marko.
http://markorodriguez.com
Marko A. Rodriguez created TINKERPOP3-871:
-
Summary: RuntimeStrategy as the general model for all such
execution time rewrites/re-orders
Key: TINKERPOP3-871
URL: https://issues.apache.org/jira/browse/TINKE
[
https://issues.apache.org/jira/browse/TINKERPOP3-852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947376#comment-14947376
]
stephen mallette commented on TINKERPOP3-852:
-
Ok - altered the packaging
[
https://issues.apache.org/jira/browse/TINKERPOP3-820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marko A. Rodriguez closed TINKERPOP3-820.
-
Resolution: Won't Fix
Going to close this as there is no easy was to modulate
Hello,
Please see this ticket:
https://issues.apache.org/jira/browse/TINKERPOP3-798
If anyone has any thoughts, please speak up.
Marko.
http://markorodriguez.com
[
https://issues.apache.org/jira/browse/TINKERPOP3-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947367#comment-14947367
]
Marko A. Rodriguez commented on TINKERPOP3-798:
---
Any good ideas here...
[
https://issues.apache.org/jira/browse/TINKERPOP3-776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marko A. Rodriguez closed TINKERPOP3-776.
-
Resolution: Won't Fix
Going to close this "grab bag." There are various specif
? … I would know you were using the "old way" by the fact that you added a 3rd
by()-modulator. I don't see how multi-properties effects this particular
situation you bring up. ?
Marko.
http://markorodriguez.com
On Oct 7, 2015, at 12:12 PM, Daniel Kuppitz wrote:
>>
>> g.V.group.by('name').by
>
> g.V.group.by('name').by(outE.weight).by(max(local))
> If you did this, I would know you were using "the old way" as your
> provided a reduce by()-modulator.
Actually you wouldn't know. Think about multi-properties and:
g.V().group().by('name').by(values('weight')).by(max(local))
Cheers,
Da
[
https://issues.apache.org/jira/browse/TINKERPOP3-852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947275#comment-14947275
]
stephen mallette commented on TINKERPOP3-852:
-
Gremlin Server ships with T
Hi everyone,
I was soo close to having group() be backwards compatible. However, I found
a corner case that makes it break.
If you do something like:
g.V.group.by('name').by(outE.weight).by(max(local))
If you did this, I would know you were using "the old way" as your provided a
reduce by
[
https://issues.apache.org/jira/browse/TINKERPOP3-852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947271#comment-14947271
]
Daniel Kuppitz commented on TINKERPOP3-852:
---
The Gremlin Server distribution
Mentors, I happened to notice graduation discussion on the general@incubator
mailing list for Kylin. Someone just said that a blocker to graduation was
the "name search" and they referenced a JIRA ticket:
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-86
I had thought we had done this f
I'm currently working on 852, I think I will be done today/tomorrow. Once
that's done, I can work on 319 - this only means: verify that the
TinkerGraph persistence works well with BLVP and write unit/integration
tests for it. The other pending things in 319 are subject to 3.1.0.
Let's push 838 to
Had to tack in this one for 3.0.2:
https://issues.apache.org/jira/browse/TINKERPOP3-870
a small bug in the java-driver. It has a workaround, but it's not nice.
Shouldn't be too hard to fix - diagnosing it in the first place was the
hard part.
On Wed, Oct 7, 2015 at 11:24 AM, Stephen Mallette
w
stephen mallette created TINKERPOP3-870:
---
Summary: Rebound client requires a connection to occur on the
underlying client.
Key: TINKERPOP3-870
URL: https://issues.apache.org/jira/browse/TINKERPOP3-870
[
https://issues.apache.org/jira/browse/TINKERPOP3-868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marko A. Rodriguez closed TINKERPOP3-868.
-
Resolution: Fixed
Assignee: Marko A. Rodriguez
This has been merged to m
[
https://issues.apache.org/jira/browse/TINKERPOP3-868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette updated TINKERPOP3-868:
Component/s: hadoop
> Allow Spark Gremlin Computer to Reuse Spark Contexts
> ---
[
https://issues.apache.org/jira/browse/TINKERPOP3-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette closed TINKERPOP3-867.
---
> TinkerGraphProvider does not initialize temp dir
> -
+1. As a consumer, I'd be more likely to read a "Migration" doc before a
Changelog. I'd only look at the Changelog if I were curious how they
implemented the fix. With the Migration doc, I'd expect to learn how to
make my app work with the new version.
On Wed, Oct 7, 2015 at 11:38 AM, Dylan Millik
+1 I like the idea of a todo list of sorts.
On Wed, Oct 7, 2015 at 5:18 PM, Marko Rodriguez
wrote:
> Yes. This is a good idea.
>
> Marko.
>
> http://markorodriguez.com
>
> On Oct 7, 2015, at 8:55 AM, Matt Frantz
> wrote:
>
> > I like the idea of creating "Migration" documents. Separate docs fo
There are currently 5 unresolved issues assigned to 3.0.2:
http://bit.ly/1Q7Ez8O
In summary we have:
https://issues.apache.org/jira/browse/TINKERPOP3-852 (Kuppitz)
https://issues.apache.org/jira/browse/TINKERPOP3-838 (Unassigned - probably
me/Kuppitz)
https://issues.apache.org/jira/browse/TINKERP
[
https://issues.apache.org/jira/browse/TINKERPOP3-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947015#comment-14947015
]
stephen mallette commented on TINKERPOP3-319:
-
TINKERPOP3-828 is complete
Yes. This is a good idea.
Marko.
http://markorodriguez.com
On Oct 7, 2015, at 8:55 AM, Matt Frantz wrote:
> I like the idea of creating "Migration" documents. Separate docs for
> implementers and clients would probably make it easier to consume.
> Refactoring the information as a "todo" list
[
https://issues.apache.org/jira/browse/TINKERPOP3-865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette updated TINKERPOP3-865:
Assignee: Jason Plurad (was: stephen mallette)
> Errors with HTTP REST basic au
[
https://issues.apache.org/jira/browse/TINKERPOP3-858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette updated TINKERPOP3-858:
Assignee: Jason Plurad (was: stephen mallette)
> Cleanup after failed :install
I like the idea of creating "Migration" documents. Separate docs for
implementers and clients would probably make it easier to consume.
Refactoring the information as a "todo" list, rather than having it go
chronologically by when each JIRA ticket was resolved would make it even
more developer-fri
Hi,
> - Don't keep the old GropupStep at all, and have the new GroupStep "concat"
> the second and third 'by' traversals if they exist.
This is not possible. In fact, I messed up my original examples. They should be:
g.V.group.by('name').by(outE.weight).by(max(local)) // old way
g.V.group.by('na
I'm fine with all items in the Graph hierarchy implementing AutoCloseable
(including GraphTraversal). I'm not sure what the implementation would
look like though and what it would do. Perhaps I'll take a look at
ResourceIterator from Neo4j. If we go with the idea that the user is
responsible for
Ok, how about making GraphTraversal implement AutoCloseable?
Thanks
Pieter
On 07/10/2015 14:28, Stephen Mallette wrote:
> n I think the best approach is to leave it to users to close()
> resources properly and keep document it as a convention. So Option 2 from
> my initial post in this
> In sqlg I close the connection pool to the db immediately. No waiting around
for transactions to complete.
It is my sense that this approach is what most Graph implementations do.
You Graph.close() then everything else that was spawned from Graph reacts
to the close however it will. It is up to
No I don't know. Their GraphDatabaseService.shutdown() javadoc says,
"Shuts down Neo4j. After this method has been invoked, it's invalid to
invoke any methods in the Neo4j API and all references to this instance
of GraphDatabaseService should be discarded."
That sorta means that they will clean u
A few more:
- Don't keep the old GropupStep at all, and have the new GroupStep "concat"
the second and third 'by' traversals if they exist.
- Leave the GroupStep as-is, and add the mapValues step for whoever wants a
better implemantation:
g.V().group().by(keyTraversal).mapValues(valueTraversal).
No
Pieter, do you know how Neo4j handles ResourceIterator with respect to
closing a Graph. If I'm iteratng ResourceIterator and another thread calls
Graph.close() what happens?
On Wed, Oct 7, 2015 at 7:35 AM, pieter-gmail
wrote:
> Hi,
>
> The resource that concerns me most is GraphTraversal as tha
My point is that group().by('key').by('value/reduce') seems kind of weird
anyway. The equivalent sql would be "select 'value/reduce' ... group by
'key' ".
A few alternative options:
g.V().group().by(keyTraversal).mapValues(valueTraversal) //As Marko pointed
out this doesn't address the old GroupSt
[
https://issues.apache.org/jira/browse/TINKERPOP3-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette updated TINKERPOP3-869:
Affects Version/s: 3.0.1-incubating
> Adding a UtilityOpProcessor for gremlin-se
Hi,
The resource that concerns me most is GraphTraversal as that is almost
always a resource to the underlying db and is created very very often. I
reckon GraphTraversal should also implement AutoCloseable. Further, it
can be auto closed when fully iterated/traversed, for transactional
graphs on c
I'm going to resurrect this old-ish thread as we didn't really draw to any
particular conclusion and new releases are looming. Just to save folks
from having to re-read the thread itself, the basic summary is that we want
to make it easy for implementers and users to consume our new releases. We
Well - now that you've proven that what you've done works for
gremlin-scala, i suppose it's worth calling attention to the ticket and
your branch separately. Your changes shouldn't be terribly controversial
though - it's a near transparent change for everyone judging by your
changes to TinkerGraph
[
https://issues.apache.org/jira/browse/TINKERPOP3-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946460#comment-14946460
]
Dylan Millikin edited comment on TINKERPOP3-869 at 10/7/15 7:48 AM:
[
https://issues.apache.org/jira/browse/TINKERPOP3-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946460#comment-14946460
]
Dylan Millikin commented on TINKERPOP3-869:
---
Thinking out loud but there mig
I've posted a proposal to JIRA. Feel free to weigh in either there or in
this thread:
https://issues.apache.org/jira/browse/TINKERPOP3-869
On Tue, Oct 6, 2015 at 5:51 PM, Dylan Millikin
wrote:
> Will do.
>
> On Tue, Oct 6, 2015 at 5:51 PM, Stephen Mallette
> wrote:
>
>> yeah - i think that Utii
Dylan Millikin created TINKERPOP3-869:
-
Summary: Adding a UtilityOpProcessor for gremlin-server
Key: TINKERPOP3-869
URL: https://issues.apache.org/jira/browse/TINKERPOP3-869
Project: TinkerPop 3
91 matches
Mail list logo
