[GitHub] tinkerpop issue #618: TINKERPOP-915 Add combined handler for Http and Websoc...

[spmallette]

Github user spmallette commented on the issue:

https://github.com/apache/tinkerpop/pull/618
  
All tests pass with `docker/build.sh -t -n -i`

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-915) Gremlin Server supports REST and Websockets simultanteously

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TINKERPOP-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075632#comment-16075632
 ] 

ASF GitHub Bot commented on TINKERPOP-915:
--

Github user spmallette commented on the issue:

https://github.com/apache/tinkerpop/pull/618
  
All tests pass with `docker/build.sh -t -n -i`

VOTE +1


> Gremlin Server supports REST and Websockets simultanteously
> ---
>
> Key: TINKERPOP-915
> URL: https://issues.apache.org/jira/browse/TINKERPOP-915
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: server
>Affects Versions: 3.0.2-incubating
>Reporter: stephen mallette
>
> Develop a {{Channelizer}} that allows REST and Websockets to be configured at 
> the same time.  I've personally tried to do this on a couple of attempts 
> while following a Netty sample, but I've never been able to get it to work.  
> Perhaps folks like [~pluradj] or [~dmill] would like to give it a go some 
> day? :)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [DISCUSS] Remaining Items for 3.3.0

[Stephen Mallette]

There have been a number of pull requests lately that have removed
previously deprecated code for 3.3.0. While not deleting tons of code, it
is tidying up a bit which is good. I think we should try to remove just
about all deprecated code short of code deprecated for the Gremlin language
which would mean that old sack(), groupV3d0(), etc methods will still hang
around. I'm also hesitant to kill RemoteGraph as I'm not sure what we want
to do with that. It still feels like it might have utility. I would love to
get rid of our biggest deprecation offender in the TraversalEngine
 interface, but I"m not sure what that would entail (I'll consider that a
nice to have if we can get it done). As for the rest, I'll be creating
issue in JIRA tomorrow now that I have a list of everything else that can
go and then the pull requests can start flying...

On Fri, Jun 30, 2017 at 5:20 PM, Stephen Mallette 
wrote:

> Now that the Gryo 3.0 PR has been issued and is awaiting review, I've
> moved on to GraphSON 3.0 to hopefully resolve the following problems:
>
> https://issues.apache.org/jira/browse/TINKERPOP-1427
> https://issues.apache.org/jira/browse/TINKERPOP-1574
> https://issues.apache.org/jira/browse/TINKERPOP-1414
>
> Those three issues basically mean that GraphSON 3.0 will be the default
> for TinkerPop 3.3.0. There will be no such thing as "untyped" GraphSON
> anymore - that really doesn't make sense given the move toward
> bytecode/GLVs. That is further nice as it reduces a choice for users.
> Finally, this revised version of GraphSON will take care of "collections"
> that do not serialize well for Gremlin needs due to limitations of JSON
> itself. The best example of this deficiency is in maps where keys can't be
> anything but strings. In Gremlin it is a common pattern to do stuff like:
>
> g.V(1).out().groupCount()
>
> As it stands GLVs have no support for that result. Other than that, there
> are no big changes to GraphSON - it works pretty well and has improve
> dramatically in speed for 3.2.5 so it should be a good basis for GLVs to
> build from. That's about it - hoping to get all these items fixed up by end
> of next week and ready for a pull request.
>
>
>
> On Wed, Jun 28, 2017 at 8:23 AM, Stephen Mallette 
> wrote:
>
>> hahaha - i can't win. there was other work done on Gryo 3.0 a pretty long
>> time ago, that made it useful around Request/ResponseMessage serialization
>> in Gremlin Server. I'd long forgotten about that. I guess I will finish up
>> the work - the work just won't be harried by anything that had anything to
>> do with TINKERPOP-1592. It was almost there anyway I think.
>>
>> On Tue, Jun 27, 2017 at 3:02 PM, Stephen Mallette 
>> wrote:
>>
>>> You had me at the problem with multi-properties. withDetachment()
>>> doesn't seem to address that well and which makes this feel quite more
>>> hacky than when it started.
>>>
>>> I think not doing withDetachment() reduces the need and urgency to do
>>> Gryo 3.0. HaltedTraverserStrategy already works as does all the
>>> serialization that goes with it. The only issue that is messed up is that I
>>> need to "fix" TraversalMetrics serialization in Gryo 1.0, but we've never
>>> been super consistent about versioning Gryo anyway, so i wonder if that
>>> minor break matters on a version where we are allowing for breaks. I think
>>> i'll kill my efforts on Gryo 3.0 for now and save some code.
>>>
>>>
>>>
>>> On Tue, Jun 27, 2017 at 11:17 AM, Marko Rodriguez 
>>> wrote:
>>>
 Hi,

 In this email I will argue why TINKERPOP-1592 is a bad idea.

 GremlinServer does “too much.” In the future, the concept for
 GremlinServer for TinkerPop4 should be “network I/O to the Gremlin virtual
 machine.” That is it. So what is GremlinServer doing now that is bad?
 Currently GremlinServer is “detaching” elements from the graph and
 populating those elements with more data than the user requested. What do I
 mean?:

 g.V(1)

 Currently that returns a DetachedVertex which is vertex 1’s id, label,
 and all of its properties. Now here is the crazy part. What if there are 1M
 properties (e.g. timestamped multi-properties on sensor network vertices).
 Doh! However, what did the user ask for? They asked for v[1] and that is
 all they should get. This is known as ReferenceVertex. If they wanted some
 subset of the timestamped sensor network data, they should have done:

 g.V(1).properties(‘sensor’).has(‘timestamp’,gt(2017))

 Thus, we should only return the data people explicitly ask for in the
 traversal. The TINKERPOP-1592 ticket is a hack for DetachedVertex by
 allowing users to specify withDetachment(properties:[“not_sensor”]),
 but then it is not expressive enough. Ultimately, for generality, users
 will want to specify full traversals in their withDetachment()
 specification. Now 

[jira] [Updated] (TINKERPOP-1706) Remove deprecated ScriptEngineCache and related dead code

[stephen mallette (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TINKERPOP-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stephen mallette updated TINKERPOP-1706:

Description: {{ScriptEngineCache}} was essentially moved in 3.2.4 - the old 
one can be removed. Includes removal of {{CoreGremlinPlugin#INSTANCE}} which is 
now more consistently referred to as {{instance()}} and the old constructor for 
{{GremlinJythonScriptEngine}}  (was: {{ScriptEngineCache}} was essentially 
moved in 3.2.4 - the old one can be removed.)

> Remove deprecated ScriptEngineCache and related dead code
> -
>
> Key: TINKERPOP-1706
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1706
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: groovy
>Affects Versions: 3.2.5
>Reporter: stephen mallette
>Assignee: stephen mallette
>  Labels: breaking
>
> {{ScriptEngineCache}} was essentially moved in 3.2.4 - the old one can be 
> removed. Includes removal of {{CoreGremlinPlugin#INSTANCE}} which is now more 
> consistently referred to as {{instance()}} and the old constructor for 
> {{GremlinJythonScriptEngine}}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (TINKERPOP-1713) Remove deprecated fields in AbstractEvalOpProcessor

[stephen mallette (JIRA)]

stephen mallette created TINKERPOP-1713:
---

 Summary: Remove deprecated fields in AbstractEvalOpProcessor
 Key: TINKERPOP-1713
 URL: https://issues.apache.org/jira/browse/TINKERPOP-1713
 Project: TinkerPop
  Issue Type: Improvement
  Components: server
Affects Versions: 3.3.0
Reporter: stephen mallette
Assignee: stephen mallette
Priority: Minor
 Fix For: 3.3.0


These fields are generally no longer in use and have been deprecated for a long 
time.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] tinkerpop issue #644: TINKERPOP-1552 Gremlin.Net

[spmallette]

Github user spmallette commented on the issue:

https://github.com/apache/tinkerpop/pull/644
  
Made some adjustments:

1. Bumped to `dotnet-dev-1.0.4`
2. Fixed the enums so they are on separate lines

I left `.gitignore` as gremlin-python also pollutes that space atm and I 
wasn't too worried about it. I guess we can tweak that up whenever if it's 
bugging anyone. Any votes from committers now?


---
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-1682) by-modulator optimization strategy

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TINKERPOP-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074984#comment-16074984
 ] 

ASF GitHub Bot commented on TINKERPOP-1682:
---

Github user okram commented on the issue:

https://github.com/apache/tinkerpop/pull/621
  
VOTE +1


> by-modulator optimization strategy
> --
>
> Key: TINKERPOP-1682
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1682
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: process
>Affects Versions: 3.2.4
>Reporter: Daniel Kuppitz
>Assignee: Daniel Kuppitz
>
> The can be a significant difference in performance depending on whether you 
> use {{by(id)}} or {{by(id())}}:
> {noformat}
> gremlin> g.V().out().in().path().by(id()).profile()
> ==>Traversal Metrics
> Step   Count  
> Traversers   Time (ms)% Dur
> =
> TinkerGraphStep(vertex,[]) 6  
>  6  12.13758.03
> VertexStep(OUT,vertex) 6  
>  6   1.345 6.43
> VertexStep(IN,vertex) 12  
> 12   0.861 4.12
> PathStep([[IdStep, ProfileStep]]) 12  
> 12   6.57031.42
>   IdStep  36  
> 36   0.452
> >TOTAL -  
>  -  20.916-
> gremlin> g.V().out().in().path().by(id).profile()
> ==>Traversal Metrics
> Step   Count  
> Traversers   Time (ms)% Dur
> =
> TinkerGraphStep(vertex,[]) 6  
>  6   0.87611.54
> VertexStep(OUT,vertex) 6  
>  6   0.714 9.40
> VertexStep(IN,vertex) 12  
> 12   3.29943.43
> PathStep([id])12  
> 12   2.70635.63
> >TOTAL -  
>  -   7.596-
> {noformat}
> We should have a strategy that rewrites these simple patterns. This affects 
> {{id()}}, {{label()}}, {{key()}}, {{value()}}, but also 
> {{by(values("name"))}}, which can be rewritten as {{by("name")}}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] tinkerpop issue #621: TINKERPOP-1682 by-modulator optimization strategy

[okram]

Github user okram commented on the issue:

https://github.com/apache/tinkerpop/pull/621
  
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-1651) Remove deprecated gremlin.sh init syntax

[stephen mallette (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TINKERPOP-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stephen mallette closed TINKERPOP-1651.
---
   Resolution: Done
 Assignee: stephen mallette
Fix Version/s: 3.3.0

Done as part of TINKERPOP-1603

> Remove deprecated gremlin.sh init syntax
> 
>
> Key: TINKERPOP-1651
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1651
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: console
>Affects Versions: 3.2.4
>Reporter: stephen mallette
>Assignee: stephen mallette
>Priority: Minor
>  Labels: breaking
> Fix For: 3.3.0
>
>
> The old method for initializing the gremlin-console needs to be removed:
> {code}
> bn/gremlin.sh init.groovy
> {code}
> The new method that has been in play for a while now is:
> {code}
> bn/gremlin.sh -i init.groovy
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TINKERPOP-1275) Remove deprecated max setting for :remote

[stephen mallette (JIRA)]

[ 
https://issues.apache.org/jira/browse/TINKERPOP-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074974#comment-16074974
 ] 

stephen mallette commented on TINKERPOP-1275:
-

Done as part of TINKERPOP-1603

> Remove deprecated max setting for :remote
> -
>
> Key: TINKERPOP-1275
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1275
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: console
>Affects Versions: 3.1.3, 3.2.1
>Reporter: stephen mallette
>Assignee: stephen mallette
>Priority: Minor
>  Labels: breaking
> Fix For: 3.3.0
>
>
> The "max" value should be removed as an option from the `:remote` command in 
> `DriverRemoteAcceptor`.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (TINKERPOP-1028) Remove deprecated ConnectionPoolSettings session settings

[stephen mallette (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TINKERPOP-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stephen mallette closed TINKERPOP-1028.
---
   Resolution: Done
 Assignee: stephen mallette
Fix Version/s: 3.3.0

> Remove deprecated ConnectionPoolSettings session settings
> -
>
> Key: TINKERPOP-1028
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1028
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: driver
>Affects Versions: 3.1.1-incubating
>Reporter: stephen mallette
>Assignee: stephen mallette
>Priority: Minor
>  Labels: breaking
> Fix For: 3.3.0
>
>
> This setting should never have been used publicly so it should be easy to 
> remove without breaking folks.  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (TINKERPOP-1481) Remove deprecated reconnectInitialDelay in Java driver

[stephen mallette (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TINKERPOP-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stephen mallette closed TINKERPOP-1481.
---
Resolution: Done
  Assignee: stephen mallette

> Remove deprecated reconnectInitialDelay in Java driver
> --
>
> Key: TINKERPOP-1481
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1481
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: driver
>Affects Versions: 3.2.2
>Reporter: stephen mallette
>Assignee: stephen mallette
>Priority: Minor
>  Labels: breaking
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (TINKERPOP-1481) Remove deprecated reconnectInitialDelay in Java driver

[stephen mallette (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TINKERPOP-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stephen mallette closed TINKERPOP-1481.
---
   Resolution: Done
Fix Version/s: 3.3.0

> Remove deprecated reconnectInitialDelay in Java driver
> --
>
> Key: TINKERPOP-1481
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1481
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: driver
>Affects Versions: 3.2.2
>Reporter: stephen mallette
>Assignee: stephen mallette
>Priority: Minor
>  Labels: breaking
> Fix For: 3.3.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (TINKERPOP-1603) Remove support for SASL byte array in protocol

[stephen mallette (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TINKERPOP-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stephen mallette closed TINKERPOP-1603.
---
Resolution: Done

> Remove support for SASL byte array in protocol
> --
>
> Key: TINKERPOP-1603
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1603
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: driver, server
>Affects Versions: 3.2.3
>Reporter: stephen mallette
>Assignee: stephen mallette
>Priority: Minor
>  Labels: breaking
> Fix For: 3.3.0
>
>
> Support for sending SASL arguments as a byte array has been deprecated in 
> 3.2.4 with TINKERPOP-1600. Remove that aspect of the protocol.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TINKERPOP-1603) Remove support for SASL byte array in protocol

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TINKERPOP-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074968#comment-16074968
 ] 

ASF GitHub Bot commented on TINKERPOP-1603:
---

Github user asfgit closed the pull request at:

https://github.com/apache/tinkerpop/pull/646


> Remove support for SASL byte array in protocol
> --
>
> Key: TINKERPOP-1603
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1603
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: driver, server
>Affects Versions: 3.2.3
>Reporter: stephen mallette
>Assignee: stephen mallette
>Priority: Minor
>  Labels: breaking
> Fix For: 3.3.0
>
>
> Support for sending SASL arguments as a byte array has been deprecated in 
> 3.2.4 with TINKERPOP-1600. Remove that aspect of the protocol.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Reopened] (TINKERPOP-1481) Remove deprecated reconnectInitialDelay in Java driver

[stephen mallette (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TINKERPOP-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stephen mallette reopened TINKERPOP-1481:
-

> Remove deprecated reconnectInitialDelay in Java driver
> --
>
> Key: TINKERPOP-1481
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1481
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: driver
>Affects Versions: 3.2.2
>Reporter: stephen mallette
>Assignee: stephen mallette
>Priority: Minor
>  Labels: breaking
> Fix For: 3.3.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] tinkerpop pull request #646: TINKERPOP-1603 Remove deprecated code

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/tinkerpop/pull/646


---
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: [TinkerPop] Re: Docker images: gremlin-server and gremlin-console

[Stephen Mallette]

Nice Josh - thanks for the update on that. Please keep us informed.

On Wed, Jul 5, 2017 at 10:59 AM, Josh Perryman  wrote:

> I worked on this a little over the holiday weekend. I've got a
> gremlin-console image based on OpenJDK:8 and one that uses the Alpine
> version. They allow you to specify the TinkerPop version as a command line
> argument and support anything that's available on
> https://archive.apache.org/dist/tinkerpop/.
>
> That was trivial, and not really of high value. I'm working on
> gremlin-server images now. My goal is to have server images which allow you
> to specify:
>
>   + Version (if on https://archive.apache.org/dist/tinkerpop/)
>   + Data set (any one included in the distribution)
>   + Access protocol (WebSocket or REST)
>
> The idea is that you can just start the image and have a local running
> gremlin-server in any version, with some data loaded. This could also be
> the basis for a gremlin-server microservice. I also want to have one that
> has both console & server which is more suitable for training.
>
> But I don't think that I'll have time to work through all of that for some
> weeks, perhaps late July, or more likely in August. When I get these to a
> usable point with legible instructions, I'll follow up with this thread on
> coordinating with Apache and getting the Dockerfiles hosted properly.
>
> *Josh Perryman*
>
> mobile: (713) 569-6533
> Twitter  / *LinkedIn*
>
> On Mon, Jun 19, 2017 at 3:06 PM, Stephen Mallette 
> wrote:
>
> > I really don't know Docker too well so I can't really drive this one. I'm
> > not sure I understand if what Apache is offering us is suitable for the
> > needs TinkerPop has wrt Docker. Any volunteers willing to pick this up
> and
> > drive this discussion forward?
> >
> >
> >
> > On Tue, Jun 13, 2017 at 4:26 PM, Stephen Mallette 
> > wrote:
> >
> > > With help from Humbedooh aka Daniel Gruno, I've got in contact with
> folks
> > > at Apache Infrastructure regarding projects putting stuff on Docker
> Hub.
> > > Here was the basic reply:
> > >
> > > > We do support the use of Docker Hub under the ASF banner:
> > > > https://hub.docker.com/u/apache/
> > > > The policy for releases on there is still being worked out, but at
> > > > this moment if you have a dockerfile/ repo we can add that to our org
> > > > for automated building.
> > > > Just file a ticket on the INFRA JIRA
> > > > https://issues.apache.org/jira/secure/RapidBoard.jspa?rapi
> > > dView=25=INFRA
> > > > and we can add that repo to the org.
> > >
> > > Is that helpful for what we're talking about here? Are there other
> > > questions to ask?
> > >
> > >
> > >
> > > On Thu, Jun 8, 2017 at 2:36 AM, Florian Hockmann <
> f...@florian-hockmann.de
> > >
> > > wrote:
> > >
> > >> I think official images would be a very good idea as there exist
> > >> currently a lot of images, especially for Gremlin Server. Users
> > typically
> > >> search for the official image or just take the image with the most
> > pulls.
> > >> Images published directly by TinkerPop would get the most attention so
> > >> users don't end up with some image that isn't actively maintained.
> > >>
> > >> Another advantage of integrating the images in TinkerPop would
> probably
> > >> be that the deployment could be integrated into TinkerPop's usual
> > release
> > >> cycle. So new images can be published directly for each new version.
> > >>
> > >> Am Dienstag, 6. Juni 2017 18:39:09 UTC+2 schrieb Stephen Mallette:
> > >>>
> > >>> Would it be interesting to anyone for TinkerPop to have an official
> > >>> docker image?
> > >>>
> > >>> On Tue, Jun 6, 2017 at 12:22 PM, Benjamin Ricaud <
> benjami...@gmail.com
> > >
> > >>> wrote:
> > >>>
> >  Thanks Jean-Baptiste,
> > 
> >  I have also done a container for the gremlin-server 3.2.4,
> configured
> >  to be used with gremlin-python:
> >  https://hub.docker.com/r/bricaud/gremlin-server/
> > 
> >  I noticed that you do not need the IP trick for the server to be
> >  accessed. If you set
> >  host: 0
> >  in your gremlin-conf.yaml, (and open the port with -p 8182:8182) you
> >  can access the server.
> >  (see my conf files on the github repo).
> > 
> >  Best,
> >  Benjamin
> > 
> >  Le jeudi 1 juin 2017 00:37:07 UTC+2, Jean-Baptiste Musso a écrit :
> > >
> > > Dear TinkerPop,
> > >
> > > I published a couple automatically built Docker images for
> > > gremlin-server and gremlin-console (current image tags: latest,
> > 3.2.4, 3.2
> > > and 3):
> > >
> > > https://hub.docker.com/r/jbmusso/gremlin-server/
> > > https://hub.docker.com/r/jbmusso/gremlin-console/
> > >
> > > I built these because I needed to quickly start different
> > > configurations of gremlin-server when developing the
> > gremlin-javascript
> > > client.
> > > Source repository: 

Re: [TinkerPop] Re: Docker images: gremlin-server and gremlin-console

[Josh Perryman]

I worked on this a little over the holiday weekend. I've got a
gremlin-console image based on OpenJDK:8 and one that uses the Alpine
version. They allow you to specify the TinkerPop version as a command line
argument and support anything that's available on
https://archive.apache.org/dist/tinkerpop/.

That was trivial, and not really of high value. I'm working on
gremlin-server images now. My goal is to have server images which allow you
to specify:

  + Version (if on https://archive.apache.org/dist/tinkerpop/)
  + Data set (any one included in the distribution)
  + Access protocol (WebSocket or REST)

The idea is that you can just start the image and have a local running
gremlin-server in any version, with some data loaded. This could also be
the basis for a gremlin-server microservice. I also want to have one that
has both console & server which is more suitable for training.

But I don't think that I'll have time to work through all of that for some
weeks, perhaps late July, or more likely in August. When I get these to a
usable point with legible instructions, I'll follow up with this thread on
coordinating with Apache and getting the Dockerfiles hosted properly.

*Josh Perryman*

mobile: (713) 569-6533
Twitter  / *LinkedIn*

On Mon, Jun 19, 2017 at 3:06 PM, Stephen Mallette 
wrote:

> I really don't know Docker too well so I can't really drive this one. I'm
> not sure I understand if what Apache is offering us is suitable for the
> needs TinkerPop has wrt Docker. Any volunteers willing to pick this up and
> drive this discussion forward?
>
>
>
> On Tue, Jun 13, 2017 at 4:26 PM, Stephen Mallette 
> wrote:
>
> > With help from Humbedooh aka Daniel Gruno, I've got in contact with folks
> > at Apache Infrastructure regarding projects putting stuff on Docker Hub.
> > Here was the basic reply:
> >
> > > We do support the use of Docker Hub under the ASF banner:
> > > https://hub.docker.com/u/apache/
> > > The policy for releases on there is still being worked out, but at
> > > this moment if you have a dockerfile/ repo we can add that to our org
> > > for automated building.
> > > Just file a ticket on the INFRA JIRA
> > > https://issues.apache.org/jira/secure/RapidBoard.jspa?rapi
> > dView=25=INFRA
> > > and we can add that repo to the org.
> >
> > Is that helpful for what we're talking about here? Are there other
> > questions to ask?
> >
> >
> >
> > On Thu, Jun 8, 2017 at 2:36 AM, Florian Hockmann  >
> > wrote:
> >
> >> I think official images would be a very good idea as there exist
> >> currently a lot of images, especially for Gremlin Server. Users
> typically
> >> search for the official image or just take the image with the most
> pulls.
> >> Images published directly by TinkerPop would get the most attention so
> >> users don't end up with some image that isn't actively maintained.
> >>
> >> Another advantage of integrating the images in TinkerPop would probably
> >> be that the deployment could be integrated into TinkerPop's usual
> release
> >> cycle. So new images can be published directly for each new version.
> >>
> >> Am Dienstag, 6. Juni 2017 18:39:09 UTC+2 schrieb Stephen Mallette:
> >>>
> >>> Would it be interesting to anyone for TinkerPop to have an official
> >>> docker image?
> >>>
> >>> On Tue, Jun 6, 2017 at 12:22 PM, Benjamin Ricaud  >
> >>> wrote:
> >>>
>  Thanks Jean-Baptiste,
> 
>  I have also done a container for the gremlin-server 3.2.4, configured
>  to be used with gremlin-python:
>  https://hub.docker.com/r/bricaud/gremlin-server/
> 
>  I noticed that you do not need the IP trick for the server to be
>  accessed. If you set
>  host: 0
>  in your gremlin-conf.yaml, (and open the port with -p 8182:8182) you
>  can access the server.
>  (see my conf files on the github repo).
> 
>  Best,
>  Benjamin
> 
>  Le jeudi 1 juin 2017 00:37:07 UTC+2, Jean-Baptiste Musso a écrit :
> >
> > Dear TinkerPop,
> >
> > I published a couple automatically built Docker images for
> > gremlin-server and gremlin-console (current image tags: latest,
> 3.2.4, 3.2
> > and 3):
> >
> > https://hub.docker.com/r/jbmusso/gremlin-server/
> > https://hub.docker.com/r/jbmusso/gremlin-console/
> >
> > I built these because I needed to quickly start different
> > configurations of gremlin-server when developing the
> gremlin-javascript
> > client.
> > Source repository: https://github.com/jbmusso/docker-tinkerpop
> >
> >
> > Start gremlin-server with:
> >
> > docker run -p 8182:8182 jbmusso/gremlin-server:3.2.4
> >
> >
> > Defaults to conf/gremlin-server.yaml within that container, or pass
> > another .yaml file:
> >
> > docker run -p 8182:8182 jbmusso/gremlin-server:3.2.4
> > conf/gremlin-server-modern.yaml
> >
> 

[jira] [Closed] (TINKERPOP-1708) Add a "Note on Scopes" document

[Marko A. Rodriguez (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TINKERPOP-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marko A. Rodriguez closed TINKERPOP-1708.
-
   Resolution: Fixed
Fix Version/s: 3.2.6

> Add a "Note on Scopes" document
> ---
>
> Key: TINKERPOP-1708
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1708
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: documentation
>Affects Versions: 3.2.5
>Reporter: Marko A. Rodriguez
>Assignee: Marko A. Rodriguez
> Fix For: 3.2.6
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] tinkerpop pull request #647: TINKERPOP-1708: Add a "Note on Scopes" document

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/tinkerpop/pull/647


---
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-1710) Add a note on tree() by-modulation and uniqueness of tree branches.

[Marko A. Rodriguez (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TINKERPOP-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marko A. Rodriguez closed TINKERPOP-1710.
-
   Resolution: Fixed
Fix Version/s: 3.2.6

> Add a note on tree() by-modulation and uniqueness of tree branches.
> ---
>
> Key: TINKERPOP-1710
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1710
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: documentation
>Affects Versions: 3.2.5
>Reporter: Marko A. Rodriguez
>Assignee: Marko A. Rodriguez
> Fix For: 3.2.6
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TINKERPOP-1710) Add a note on tree() by-modulation and uniqueness of tree branches.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TINKERPOP-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074883#comment-16074883
 ] 

ASF GitHub Bot commented on TINKERPOP-1710:
---

Github user asfgit closed the pull request at:

https://github.com/apache/tinkerpop/pull/648


> Add a note on tree() by-modulation and uniqueness of tree branches.
> ---
>
> Key: TINKERPOP-1710
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1710
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: documentation
>Affects Versions: 3.2.5
>Reporter: Marko A. Rodriguez
>Assignee: Marko A. Rodriguez
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] tinkerpop pull request #648: TINKERPOP-1710: Add a note on tree() by-modulat...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/tinkerpop/pull/648


---
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-1710) Add a note on tree() by-modulation and uniqueness of tree branches.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TINKERPOP-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074852#comment-16074852
 ] 

ASF GitHub Bot commented on TINKERPOP-1710:
---

Github user spmallette commented on the issue:

https://github.com/apache/tinkerpop/pull/648
  
VOTE +1


> Add a note on tree() by-modulation and uniqueness of tree branches.
> ---
>
> Key: TINKERPOP-1710
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1710
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: documentation
>Affects Versions: 3.2.5
>Reporter: Marko A. Rodriguez
>Assignee: Marko A. Rodriguez
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] tinkerpop issue #648: TINKERPOP-1710: Add a note on tree() by-modulation and...

[spmallette]

Github user spmallette commented on the issue:

https://github.com/apache/tinkerpop/pull/648
  
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-1708) Add a "Note on Scopes" document

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TINKERPOP-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074835#comment-16074835
 ] 

ASF GitHub Bot commented on TINKERPOP-1708:
---

Github user dkuppitz commented on the issue:

https://github.com/apache/tinkerpop/pull/647
  
VOTE: +1


> Add a "Note on Scopes" document
> ---
>
> Key: TINKERPOP-1708
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1708
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: documentation
>Affects Versions: 3.2.5
>Reporter: Marko A. Rodriguez
>Assignee: Marko A. Rodriguez
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] tinkerpop issue #647: TINKERPOP-1708: Add a "Note on Scopes" document

[dkuppitz]

Github user dkuppitz commented on the issue:

https://github.com/apache/tinkerpop/pull/647
  
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-1708) Add a "Note on Scopes" document

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TINKERPOP-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074752#comment-16074752
 ] 

ASF GitHub Bot commented on TINKERPOP-1708:
---

Github user okram commented on the issue:

https://github.com/apache/tinkerpop/pull/647
  
Fixed both of @dkuppitz's recommended tweaks.


> Add a "Note on Scopes" document
> ---
>
> Key: TINKERPOP-1708
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1708
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: documentation
>Affects Versions: 3.2.5
>Reporter: Marko A. Rodriguez
>Assignee: Marko A. Rodriguez
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] tinkerpop issue #647: TINKERPOP-1708: Add a "Note on Scopes" document

[okram]

Github user okram commented on the issue:

https://github.com/apache/tinkerpop/pull/647
  
Fixed both of @dkuppitz's recommended tweaks.


---
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-1169) Remove deprecated TraversalScriptFunction and TraversalScriptHelper

[Marko A. Rodriguez (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TINKERPOP-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marko A. Rodriguez closed TINKERPOP-1169.
-
   Resolution: Fixed
 Assignee: Marko A. Rodriguez
Fix Version/s: 3.3.0

> Remove deprecated TraversalScriptFunction and TraversalScriptHelper
> ---
>
> Key: TINKERPOP-1169
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1169
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: process
>Affects Versions: 3.2.0-incubating
>Reporter: Marko A. Rodriguez
>Assignee: Marko A. Rodriguez
>Priority: Minor
>  Labels: breaking
> Fix For: 3.3.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TINKERPOP-1603) Remove support for SASL byte array in protocol

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TINKERPOP-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074733#comment-16074733
 ] 

ASF GitHub Bot commented on TINKERPOP-1603:
---

Github user okram commented on the issue:

https://github.com/apache/tinkerpop/pull/646
  
VOTE +1


> Remove support for SASL byte array in protocol
> --
>
> Key: TINKERPOP-1603
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1603
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: driver, server
>Affects Versions: 3.2.3
>Reporter: stephen mallette
>Assignee: stephen mallette
>Priority: Minor
>  Labels: breaking
> Fix For: 3.3.0
>
>
> Support for sending SASL arguments as a byte array has been deprecated in 
> 3.2.4 with TINKERPOP-1600. Remove that aspect of the protocol.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] tinkerpop issue #646: TINKERPOP-1603 Remove deprecated code

[okram]

Github user okram commented on the issue:

https://github.com/apache/tinkerpop/pull/646
  
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-1169) Remove deprecated TraversalScriptFunction and TraversalScriptHelper

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TINKERPOP-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074731#comment-16074731
 ] 

ASF GitHub Bot commented on TINKERPOP-1169:
---

Github user asfgit closed the pull request at:

https://github.com/apache/tinkerpop/pull/651


> Remove deprecated TraversalScriptFunction and TraversalScriptHelper
> ---
>
> Key: TINKERPOP-1169
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1169
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: process
>Affects Versions: 3.2.0-incubating
>Reporter: Marko A. Rodriguez
>Priority: Minor
>  Labels: breaking
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] tinkerpop pull request #651: TINKERPOP-1169: Remove deprecated TraversalScri...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/tinkerpop/pull/651


---
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 #650: TINKERPOP-1171: Remove deprecated TraversalSour...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/tinkerpop/pull/650


---
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-1427) GraphSON 3.0 needs collection types and consistent number typing.

[stephen mallette (JIRA)]

[ 
https://issues.apache.org/jira/browse/TINKERPOP-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074708#comment-16074708
 ] 

stephen mallette commented on TINKERPOP-1427:
-

Not sure if anyone cares, but I may break off the aspect of this ticket that 
deals with numbering. It's a bit outside of the scope of what I'd like 
evaluated in a PR for the "collection stuff". Plus the number issue seems like 
it it is a problem generally held across TinkerPop and not something specific 
to GraphSON. 

I did think TINKERPOP-1523 offered an interesting position on that number stuff 
fwiw. [~rdale] not sure if that appeals to you or not.

> GraphSON 3.0 needs collection types and consistent number typing.
> -
>
> Key: TINKERPOP-1427
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1427
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: io
>Affects Versions: 3.2.1
>Reporter: Marko A. Rodriguez
>Assignee: stephen mallette
>
> Before 3.3.0, we need to get the story around collections straight. Currently 
> we are relying on JSON collections to represent our collections, but this 
> isn't always sound -- e.g. JSON maps can only have string keys.
> Thus, we need:
> {code}
> g:Map
> g:List
> g:Set
> {code}
> Note that all of these would just be JSON lists:
> {code}
> {@type:"g:Map", @value:[key1,value1,key2,value2,key3,value3,...]}
> {@type:"g:List", @value:[value1, value2, value3,...]}
> {@type:"g:Set", @value:[value1, value2, value3,...]}
> {code}
> ---
> Next, these data structures are exactly what play into {{aggregateTo}} in 
> sideEffects for {{RemoteConnection}}. Thus, we should use these types and, as 
> well, get rid of {{none}} as the aggregate would be a real type like 
> {{g:Int32}}.
> Also, I think we should abandon this hybrid physical machine naming 
> convention and programming language type convention.
> {code}
> g:Int32 -> g:Integer
> g:Int64 -> g:Long
> g:Double -> g:Double (no change)
> g:Float -> g:Float (no change)
> {code}
> If we want to be consistent either do the above or do the below, though I 
> think the above is cleaner.
> {code}
> g:Int32 -> g:Int32
> g:Int64 -> g:Int64
> g:Float -> g:Float32
> g:Double -> g:Float64
> {code}
> Again, using programming lexicon vs. physical machine lexicon is best and 
> thus, just gut "int32" and "int64."



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (TINKERPOP-1427) GraphSON 3.0 needs collection types and consistent number typing.

[stephen mallette (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TINKERPOP-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stephen mallette reassigned TINKERPOP-1427:
---

Assignee: stephen mallette
  Labels:   (was: breaking)

I removed the "breaking" label as this change will go in for a new version of 
GraphSON so previous versions will be unaffected.

> GraphSON 3.0 needs collection types and consistent number typing.
> -
>
> Key: TINKERPOP-1427
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1427
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: io
>Affects Versions: 3.2.1
>Reporter: Marko A. Rodriguez
>Assignee: stephen mallette
>
> Before 3.3.0, we need to get the story around collections straight. Currently 
> we are relying on JSON collections to represent our collections, but this 
> isn't always sound -- e.g. JSON maps can only have string keys.
> Thus, we need:
> {code}
> g:Map
> g:List
> g:Set
> {code}
> Note that all of these would just be JSON lists:
> {code}
> {@type:"g:Map", @value:[key1,value1,key2,value2,key3,value3,...]}
> {@type:"g:List", @value:[value1, value2, value3,...]}
> {@type:"g:Set", @value:[value1, value2, value3,...]}
> {code}
> ---
> Next, these data structures are exactly what play into {{aggregateTo}} in 
> sideEffects for {{RemoteConnection}}. Thus, we should use these types and, as 
> well, get rid of {{none}} as the aggregate would be a real type like 
> {{g:Int32}}.
> Also, I think we should abandon this hybrid physical machine naming 
> convention and programming language type convention.
> {code}
> g:Int32 -> g:Integer
> g:Int64 -> g:Long
> g:Double -> g:Double (no change)
> g:Float -> g:Float (no change)
> {code}
> If we want to be consistent either do the above or do the below, though I 
> think the above is cleaner.
> {code}
> g:Int32 -> g:Int32
> g:Int64 -> g:Int64
> g:Float -> g:Float32
> g:Double -> g:Float64
> {code}
> Again, using programming lexicon vs. physical machine lexicon is best and 
> thus, just gut "int32" and "int64."



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] tinkerpop pull request #652: Minor tutorial fix

[volkovs]

Github user volkovs closed the pull request at:

https://github.com/apache/tinkerpop/pull/652


---
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] [Updated] (TINKERPOP-1427) GraphSON 3.0 needs collection types and consistent number typing.

[stephen mallette (JIRA)]

 [ 
https://issues.apache.org/jira/browse/TINKERPOP-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stephen mallette updated TINKERPOP-1427:

Summary: GraphSON 3.0 needs collection types and consistent number typing.  
(was: GraphSON 2.0 needs collection types and consistent number typing.)

> GraphSON 3.0 needs collection types and consistent number typing.
> -
>
> Key: TINKERPOP-1427
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1427
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: io
>Affects Versions: 3.2.1
>Reporter: Marko A. Rodriguez
>  Labels: breaking
>
> Before 3.3.0, we need to get the story around collections straight. Currently 
> we are relying on JSON collections to represent our collections, but this 
> isn't always sound -- e.g. JSON maps can only have string keys.
> Thus, we need:
> {code}
> g:Map
> g:List
> g:Set
> {code}
> Note that all of these would just be JSON lists:
> {code}
> {@type:"g:Map", @value:[key1,value1,key2,value2,key3,value3,...]}
> {@type:"g:List", @value:[value1, value2, value3,...]}
> {@type:"g:Set", @value:[value1, value2, value3,...]}
> {code}
> ---
> Next, these data structures are exactly what play into {{aggregateTo}} in 
> sideEffects for {{RemoteConnection}}. Thus, we should use these types and, as 
> well, get rid of {{none}} as the aggregate would be a real type like 
> {{g:Int32}}.
> Also, I think we should abandon this hybrid physical machine naming 
> convention and programming language type convention.
> {code}
> g:Int32 -> g:Integer
> g:Int64 -> g:Long
> g:Double -> g:Double (no change)
> g:Float -> g:Float (no change)
> {code}
> If we want to be consistent either do the above or do the below, though I 
> think the above is cleaner.
> {code}
> g:Int32 -> g:Int32
> g:Int64 -> g:Int64
> g:Float -> g:Float32
> g:Double -> g:Float64
> {code}
> Again, using programming lexicon vs. physical machine lexicon is best and 
> thus, just gut "int32" and "int64."



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] tinkerpop issue #652: Minor tutorial fix

[spmallette]

Github user spmallette commented on the issue:

https://github.com/apache/tinkerpop/pull/652
  
merged to all branches. can you please close this? 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.
---

[GitHub] tinkerpop pull request #654: Minor tutorial fix

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/tinkerpop/pull/654


---
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-1289) Remove deprecated ConnectiveP, AndP, and OrP constructors.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TINKERPOP-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074665#comment-16074665
 ] 

ASF GitHub Bot commented on TINKERPOP-1289:
---

Github user spmallette commented on the issue:

https://github.com/apache/tinkerpop/pull/649
  
VOTE +1


> Remove deprecated ConnectiveP, AndP, and OrP constructors.
> --
>
> Key: TINKERPOP-1289
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1289
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: process
>Affects Versions: 3.2.1
>Reporter: Marko A. Rodriguez
>  Labels: breaking
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TINKERPOP-1171) Remove deprecated TraversalSource.Builder

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TINKERPOP-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074662#comment-16074662
 ] 

ASF GitHub Bot commented on TINKERPOP-1171:
---

Github user spmallette commented on the issue:

https://github.com/apache/tinkerpop/pull/650
  
VOTE +1


> Remove deprecated TraversalSource.Builder
> -
>
> Key: TINKERPOP-1171
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1171
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: process
>Affects Versions: 3.2.0-incubating
>Reporter: Marko A. Rodriguez
>Priority: Minor
>  Labels: breaking
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TINKERPOP-1169) Remove deprecated TraversalScriptFunction and TraversalScriptHelper

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/TINKERPOP-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074661#comment-16074661
 ] 

ASF GitHub Bot commented on TINKERPOP-1169:
---

Github user spmallette commented on the issue:

https://github.com/apache/tinkerpop/pull/651
  
VOTE +1


> Remove deprecated TraversalScriptFunction and TraversalScriptHelper
> ---
>
> Key: TINKERPOP-1169
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1169
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: process
>Affects Versions: 3.2.0-incubating
>Reporter: Marko A. Rodriguez
>Priority: Minor
>  Labels: breaking
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] tinkerpop issue #650: TINKERPOP-1171: Remove deprecated TraversalSource.Buil...

[spmallette]

Github user spmallette commented on the issue:

https://github.com/apache/tinkerpop/pull/650
  
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 pull request #653: Tutorial fix

[volkovs]

Github user volkovs closed the pull request at:

https://github.com/apache/tinkerpop/pull/653


---
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 #652: Minor tutorial fix

[spmallette]

Github user spmallette commented on the issue:

https://github.com/apache/tinkerpop/pull/652
  
can you please-retarget your pull request to the tp31 branch - it should be 
fixed all the way back to 3.1.x - 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.
---