Re: tinkerpop.com redirect?

2016-06-20 Thread Hadrian Zbarcea 

Done [1]. Thx.

Hadrian

[1] https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-12145

On 06/20/2016 11:40 AM, David Nalley wrote:

File an infra Jira ticket.

https://infrahelp.apache.org


On Mon, Jun 20, 2016 at 9:46 AM, Marko Rodriguez  wrote:

Hi,

How can we make tinkerpop.com redirect to tinkerpop.apache.org instead of 
tinkerpop.incubator.apache.org?

Thanks,
Marko.

http://markorodriguez.com

Re: tinkerpop.com redirect?

2016-06-20 Thread David Nalley 
File an infra Jira ticket.

https://infrahelp.apache.org


On Mon, Jun 20, 2016 at 9:46 AM, Marko Rodriguez  wrote:
> Hi,
>
> How can we make tinkerpop.com redirect to tinkerpop.apache.org instead of 
> tinkerpop.incubator.apache.org?
>
> Thanks,
> Marko.
>
> http://markorodriguez.com
>
>
>

[GitHub] tinkerpop issue #343: restructured gremlin-python package

2016-06-20 Thread okram 
Github user okram commented on the issue:

https://github.com/apache/tinkerpop/pull/343
  
This just changed to here:


https://github.com/apache/tinkerpop/blob/TINKERPOP-1278/gremlin-variant/src/test/java/org/apache/tinkerpop/gremlin/python/JythonScriptEngineSetup.java#L36-L59


---
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 #337: TINKERPOP-1332: Improve .explain() Dialogue

2016-06-20 Thread dkuppitz 
Github user dkuppitz commented on the issue:

https://github.com/apache/tinkerpop/pull/337
  
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] [Created] (TINKERPOP-1346) Create custom ReferenceXXX GryoSerializers

2016-06-20 Thread Marko A. Rodriguez (JIRA) 
Marko A. Rodriguez created TINKERPOP-1346:
-

 Summary: Create custom ReferenceXXX GryoSerializers
 Key: TINKERPOP-1346
 URL: https://issues.apache.org/jira/browse/TINKERPOP-1346
 Project: TinkerPop
  Issue Type: Improvement
  Components: io, structure
Affects Versions: 3.2.0-incubating
Reporter: Marko A. Rodriguez
 Fix For: 3.3.0


Right now, to send a {{ReferenceEdge}} message, we serialize the form as:

{code}
KryoClassInteger[ReferenceEdge] + KryoClassObject[Edge ID] + 
KryoClassInteger[ReferenceVertex] + KryoClassObject[Vertex ID] + 
KryoClassInteger[ReferenceVertex] + KryoClassObject[Vertex ID]
{code}

Assuming {{Long}} Element ids, the math says:

{code}
48 bytes = 4 bytes + (4 bytes + 8 bytes [long]) + 4 bytes + (4 bytes + 8 bytes 
[long]) + 4 bytes + (4 bytes + 8 bytes [long])
{code}

We could get this smaller by not relying on Kryo's {{FieldSerializer}}.

{code}
KryoClassInteger[ReferenceEdge] + KryoClassInteger[VertexIDClass] + 
KryoClassObject[Edge ID] + KryoObject[Vertex ID] + KryoObject[Vertex ID]
{code}

The math says:

{code}
36 bytes = 4 bytes + 4 bytes + (4 bytes + 8 bytes [long]) + 8 bytes [long] + 8 
bytes [long]
{code}
{code}

Similar techniques would apply to {{ReferenceVertexProperty}} and 
{{ReferenceProperty}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (TINKERPOP-1346) Create custom ReferenceXXX GryoSerializers

2016-06-20 Thread Marko A. Rodriguez (JIRA) 

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

Marko A. Rodriguez updated TINKERPOP-1346:
--
Description: 
Right now, to send a {{ReferenceEdge}} message, we serialize the form as:

{code}
KryoClassInteger[ReferenceEdge] + KryoClassObject[Edge ID] + 
KryoClassInteger[ReferenceVertex] + KryoClassObject[Vertex ID] + 
KryoClassInteger[ReferenceVertex] + KryoClassObject[Vertex ID]
{code}

Assuming {{Long}} Element ids, the math says:

{code}
48 bytes = 4 bytes + (4 bytes + 8 bytes [long]) + 4 bytes + (4 bytes + 8 bytes 
[long]) + 4 bytes + (4 bytes + 8 bytes [long])
{code}

We could get this smaller by not relying on Kryo's {{FieldSerializer}}.

{code}
KryoClassInteger[ReferenceEdge] + KryoClassInteger[VertexIDClass] + 
KryoClassObject[Edge ID] + KryoObject[Vertex ID] + KryoObject[Vertex ID]
{code}

The math says:

{code}
36 bytes = 4 bytes + 4 bytes + (4 bytes + 8 bytes [long]) + 8 bytes [long] + 8 
bytes [long]
{code}

Similar techniques would apply to {{ReferenceVertexProperty}} and 
{{ReferenceProperty}}.

  was:
Right now, to send a {{ReferenceEdge}} message, we serialize the form as:

{code}
KryoClassInteger[ReferenceEdge] + KryoClassObject[Edge ID] + 
KryoClassInteger[ReferenceVertex] + KryoClassObject[Vertex ID] + 
KryoClassInteger[ReferenceVertex] + KryoClassObject[Vertex ID]
{code}

Assuming {{Long}} Element ids, the math says:

{code}
48 bytes = 4 bytes + (4 bytes + 8 bytes [long]) + 4 bytes + (4 bytes + 8 bytes 
[long]) + 4 bytes + (4 bytes + 8 bytes [long])
{code}

We could get this smaller by not relying on Kryo's {{FieldSerializer}}.

{code}
KryoClassInteger[ReferenceEdge] + KryoClassInteger[VertexIDClass] + 
KryoClassObject[Edge ID] + KryoObject[Vertex ID] + KryoObject[Vertex ID]
{code}

The math says:

{code}
36 bytes = 4 bytes + 4 bytes + (4 bytes + 8 bytes [long]) + 8 bytes [long] + 8 
bytes [long]
{code}
{code}

Similar techniques would apply to {{ReferenceVertexProperty}} and 
{{ReferenceProperty}}.


> Create custom ReferenceXXX GryoSerializers
> --
>
> Key: TINKERPOP-1346
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1346
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: io, structure
>Affects Versions: 3.2.0-incubating
>Reporter: Marko A. Rodriguez
>  Labels: breaking
> Fix For: 3.3.0
>
>
> Right now, to send a {{ReferenceEdge}} message, we serialize the form as:
> {code}
> KryoClassInteger[ReferenceEdge] + KryoClassObject[Edge ID] + 
> KryoClassInteger[ReferenceVertex] + KryoClassObject[Vertex ID] + 
> KryoClassInteger[ReferenceVertex] + KryoClassObject[Vertex ID]
> {code}
> Assuming {{Long}} Element ids, the math says:
> {code}
> 48 bytes = 4 bytes + (4 bytes + 8 bytes [long]) + 4 bytes + (4 bytes + 8 
> bytes [long]) + 4 bytes + (4 bytes + 8 bytes [long])
> {code}
> We could get this smaller by not relying on Kryo's {{FieldSerializer}}.
> {code}
> KryoClassInteger[ReferenceEdge] + KryoClassInteger[VertexIDClass] + 
> KryoClassObject[Edge ID] + KryoObject[Vertex ID] + KryoObject[Vertex ID]
> {code}
> The math says:
> {code}
> 36 bytes = 4 bytes + 4 bytes + (4 bytes + 8 bytes [long]) + 8 bytes [long] + 
> 8 bytes [long]
> {code}
> Similar techniques would apply to {{ReferenceVertexProperty}} and 
> {{ReferenceProperty}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (TINKERPOP-1278) Implement Gremlin-Python and general purpose language variant test infrastructure

2016-06-20 Thread ASF GitHub Bot (JIRA) 

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

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

Github user okram commented on the issue:

https://github.com/apache/tinkerpop/pull/343
  
This is how the Python modules are loaded into Jython.


https://github.com/apache/tinkerpop/blob/TINKERPOP-1278/gremlin-variant/src/test/java/org/apache/tinkerpop/gremlin/python/PythonProvider.java#L39-L62

Recommendations to make it more "package like" ?


> Implement Gremlin-Python and general purpose language variant test 
> infrastructure
> -
>
> Key: TINKERPOP-1278
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1278
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: language-variant
>Affects Versions: 3.2.0-incubating
>Reporter: Marko A. Rodriguez
>Assignee: Marko A. Rodriguez
>
> As discussed on dev@...
> Apache TinkerPop should provide, out-of-the-box, at least 3 Gremlin language 
> variants. It would be cool if these were:
> * Python (Mark Henderson)
> * PHP ([~PommeVerte])
> * Ruby (?[~okram])
> I think each of these should be generated using the reflection-model 
> presented in 
> http://tinkerpop.apache.org/docs/3.2.1-SNAPSHOT/tutorials/gremlin-language-variants/.
>  Moreover, on every {{mvn clean install}}, the code for these variants is 
> generated.
> Given the desire to separate language variants from language drivers, I think 
> that a language driver for each variant above should be "plugable." Moreover, 
> we should provide one driver implementation for each -- simple GremlinServer 
> REST.
> {code}
> gremlin-variants/
>   gremlin-ruby/
> gremlin_ruby.rb
> gremlin_ruby_rest_driver.rb
>   gremlin-php/
> Gremlin_PHP.php
> Gremlin_PHP_REST_Driver.php
>   gremlin-python/
> gremlin-python.py
> gremlin-python-rest-driver.py
> {code}
> Next, each variant implementation should be testable. This is PAINFUL if we 
> have to implement each {{g_V_out_repeatXasXaXX}} test case in 
> {{ProcessXXXSuite}}. Perhaps some RegEx transducer magic could be used to 
> convert all those tests from Gremlin-Java to the respective host language? 
> However, even if we do that, we still have the problem of how to test the 
> returned results. 
> I think what we should test the returned results using the JVM. For instance, 
> JRuby, Jython, JPHP (does it exist?). If we do this, we will save ourselves a 
> massive headache. All we have to do is create a {{GraphProvider}} that uses 
> {{TinkerGraph}} and whose {{TraversalSource}} is some sort of wrapper around 
> reflection-generated Ruby (e.g.).
> {code}
> g.V.out_e("knows") // returns a Ruby iterator
> {code}
> That Ruby iterator should be converted to a Java iterator and then the 
> {{ProcessXXXSuite}} can verify the results.
> With this, most everything is reflectively constructed.
> {code}
> gremlin_ruby.rb // generated via Java reflection
> gremlin_ruby_rest_driver.rb // manually coded
> match_test.rb   // generated via RegEx transducer
> has_test.rb // generated via RegEx transducer
> ...
> RubyGraphProvider.java// manually coded
> RubyProcessStandardSuite.java // manually coded
> RubyProcessComputerSuite.java // manually coded
> {code}
> Thus, the testing data flow would be:
> {code}
> MatchTest.Traversals.java --transducer-> match_test.rb
> match-test.rb --REST--> GremlinServer
> GremlinServer --GraphSON-->match-test.rb
> GraphSON --JRuby/GraphSONReader-->Java objects
> Java objects --JRuby-->MatchTest.java 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] tinkerpop issue #343: restructured gremlin-python package

2016-06-20 Thread okram 
Github user okram commented on the issue:

https://github.com/apache/tinkerpop/pull/343
  
This is how the Python modules are loaded into Jython.


https://github.com/apache/tinkerpop/blob/TINKERPOP-1278/gremlin-variant/src/test/java/org/apache/tinkerpop/gremlin/python/PythonProvider.java#L39-L62

Recommendations to make it more "package like" ?


---
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.
---

tinkerpop.com redirect?

2016-06-20 Thread Marko Rodriguez 
Hi,

How can we make tinkerpop.com redirect to tinkerpop.apache.org instead of 
tinkerpop.incubator.apache.org?

Thanks,
Marko. 

http://markorodriguez.com