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

Jeremy Hanna commented on TINKERPOP-1007:
-----------------------------------------

I'm wondering if we want to go through the exercise of parsing the data file 
and adding data to the graph rather than supplying a kryo file for a couple of 
reasons:
1) it will help them get familiar with loading their own data programmatically
2) when gzipping the data in kryo format, it's still 17MB

I could go through the basics and possibly link to a full file that works to 
parse it in according to how we want to query it in the tutorial later.

Do you have any strong preferences either way on this point?

> Gremlin at the Movies Tutorial (SQL-Style in Gremlin)
> -----------------------------------------------------
>
>                 Key: TINKERPOP-1007
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1007
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 3.1.0-incubating
>            Reporter: Marko A. Rodriguez
>            Assignee: Jeremy Hanna
>             Fix For: 3.1.1-incubating
>
>
> We need more tutorials. [~spmallette]'s "Getting Started" tutorial is great, 
> but  (as acknowledged by Russell Jurney) we now need to meet the needs of 
> intermediate users as well.
> I think we should do another "30 Minute" tutorial called "Gremlin at the 
> Movies" and use the MovieLens dataset. 
> http://grouplens.org/datasets/movielens/ (seems we can legally do this -- 
> http://files.grouplens.org/datasets/movielens/ml-1m-README.txt).
> In this tutorial we provide a {{gryo}} file and the user will learn:
> * Reducing barriers like {{count}}, {{max}}, {{sum}}, etc.
> * {{select}} and its use with {{by}}-projections.
> * {{match}} and its use with {{where}}, {{select}}, etc.
> I think we present the queries in a very "SQL fashion" so people see that 
> Gremlin can be written using the popular/known SQL constructs of select, 
> where, group, by, etc.
> Thus, "graph data" but "table feel."
> Get information from:
> http://www.slideshare.net/slidarko/the-gremlin-traversal-language?related=1



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

Reply via email to