from:"Hyunsung Jo"

Re: Podling Report Reminder - February 2019

2019-02-05 Thread Hyunsung Jo

Hey Do Young,

Thanks for putting the report together.

Cheers,
Jo
On Tue, 5 Feb 2019 at 4:06 AM, DO YUNG YOON  wrote:

> Thanks for quick response Woonsan.
>
> I updated wiki(https://wiki.apache.org/incubator/February2019) as
> you suggested.
>
> Here is the copy of updates(same as wiki).
>
>
> S2Graph
>
> S2Graph is a distributed and scalable OLTP graph database built on Apache
> HBase to support fast traversal of extremely large graphs.
>
> S2Graph has been incubating since 2015-11-29.
>
> Three most important issues to address in the move towards graduation:
>
>   1. Make the third release.
>   2. Attract more users and contributors.
>   3. Build the developer community in both size and diversity.
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
> of?
>
>   None
>
> How has the community developed since the last report?
>
>   * Adding two committer.
>   * One more mentor has joined.
>   * There were some questions and answers from the community about the
> deployment of
> S2Graph.
>
> How has the project developed since the last report?
>
>   * We are overhauling documentation(S2GRAPH-246)
> - Integrate gitbook into the project.
>   * New HTTP interface integration(S2GRAPH-248)
>
> How would you assess the podling's maturity?
> Please feel free to add your own commentary.
>
>   [ ] Initial setup
>   [ ] Working towards first release
>   [X] Community building
>   [ ] Nearing graduation
>   [ ] Other:
>
> Date of last release:
>
>   2017-08-26
>
> When were the last committers or PPMC members elected?
>
> * 2018-12: Jong Wook Kim
> * 2018-12: Hyunsung Jo
>
> Have your mentors been helpful and responsive or are things falling
> through the cracks? In the latter case, please list any open issues
> that need to be addressed.
>
> * Our mentor is very helpful and responsive.
>
> Signed-off-by:
>
>   [ ](s2graph) Sergio Fernández
>  Comments:
>   [ ](s2graph) Woonsan Ko
>  Comments:
>
> On Tue, Feb 5, 2019 at 9:59 AM Woonsan Ko  wrote:
>
> > Hi Do Yung,
> >
> > Thanks for the draft and sharing it here.
> >
> > On Mon, Feb 4, 2019 at 6:41 PM DO YUNG YOON  wrote:
> > >
> > > Hi folks. Here is the draft of Feb Report.
> > > Please review and give feedback and I will update it on wiki tonight.
> > >
> > >
> > > S2Graph
> > >
> > > S2Graph is a distributed and scalable OLTP graph database built on
> Apache
> > > HBase to support fast traversal of extremely large graphs.
> > >
> > > S2Graph has been incubating since 2015-11-29.
> > >
> > > Three most important issues to address in the move towards graduation:
> > >
> > >   1. Make a third release.
> > >   2. Attract more users and contributors.
> > >   3. Build the developer community in both size and diversity.
> > >
> > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to
> > beaware
> > > of?
> > >
> > >   None
> > >
> > > How has the community developed since the last report?
> > >   * Adding two committer.
> > >   * One more mentor has joined.
> > >   * There were some questions from the community about the deployment
> of
> > > S2Graph.
> >
> > ... questions and answers ... ;-)
> >
> > >
> > > How has the project developed since the last report?
> > >
> > >   * We are overhauling documentation(S2GRAPH-246)
> > > - Integrate gitbook into project.
> > >   * New HTTP interface integration(S2GRAPH-248)
> > >
> > > How would you assess the podling's maturity?
> > > Please feel free to add your own commentary.
> > >
> > >   [ ] Initial setup
> > >   [ ] Working towards first release
> > >   [X] Community building
> > >   [ ] Nearing graduation
> > >   [ ] Other:
> > >
> > > Date of last release:
> > >
> > >   2017-08-26
> > >
> > > When were the last committers or PPMC members elected?
> >
> > Could you add the dates and names for the new committers here?
> > Find an example in the Tamaya podling report [1].
> >
> > [1] https://wiki.apache.org/incubator/February2019
> >
> > >
> > >   None
> >
> > Also, below this, could you add "Have your mentors been helpful and
> > responsive ..." question and answer as well? See Tamaya as an example.
> >
> > The other things look good to me.
> >
> >

Re: s2graph

2017-10-10 Thread Hyunsung Jo

Hi Ruchir,

You will be able to find the basic guidelines in the following links:
- https://github.com/apache/incubator-s2graph#quick-start
- https://steamshon.gitbooks.io/s2graph-book/content/getting_started.html

While some of the information might be dated you can always reach out to
the dev mail-list .

Regards,
Jo


On Mon, Oct 9, 2017 at 10:17 PM Ruchir Choudhry 
wrote:

> Need your help to get started with this project.
>
> Will appreciate if you can provide me a link or a doc
> for setup and some basic guideline,
>
>
> I will be happy to help you all along the project.
>
>
> Regards,
> Ruchir
>

[jira] [Commented] (S2GRAPH-133) Deprecating Vagrant environment.

2016-12-05 Thread Hyunsung Jo (JIRA)


[ 
https://issues.apache.org/jira/browse/S2GRAPH-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15722219#comment-15722219
 ] 

Hyunsung Jo commented on S2GRAPH-133:
-

Hi [~steamshon],

Sounds good.
Opened a separate issue S2GRAPH-143 on updating the documents regarding Docker 
environment.
The link you shared also seems outdated since Mac OS Docker no longer requires 
VirtualBox.

Jo

> Deprecating Vagrant environment.
> 
>
> Key: S2GRAPH-133
> URL: https://issues.apache.org/jira/browse/S2GRAPH-133
> Project: S2Graph
>  Issue Type: Improvement
>Reporter: Daewon Jeong
>        Assignee: Hyunsung Jo
>Priority: Minor
>
> Since the Vagrant environment was added, it is no longer being managed.
> Remove the Vagrant environment according to the results discussed in the link 
> below.
> https://lists.apache.org/thread.html/f375558a35f17c4962abb003513f613e3448bf28ea44054593d6e670@%3Cdev.s2graph.apache.org%3E



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

[jira] [Created] (S2GRAPH-143) Update Docker-related documents

2016-12-05 Thread Hyunsung Jo (JIRA)

Hyunsung Jo created S2GRAPH-143:
---

 Summary: Update Docker-related documents
 Key: S2GRAPH-143
 URL: https://issues.apache.org/jira/browse/S2GRAPH-143
 Project: S2Graph
  Issue Type: Task
Reporter: Hyunsung Jo
Assignee: Hyunsung Jo
Priority: Minor


1. Revise README.md to include guide on Docker environment.
2. Update [dev guide | 
https://github.com/apache/incubator-s2graph/tree/master/dev_support] since Mac 
OS Docker no longer requires VirtualBox.



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

[jira] [Commented] (S2GRAPH-128) Document new feature S2GRAPH-123 (Support different index on out/in direction)

2016-12-05 Thread Hyunsung Jo (JIRA)


[ 
https://issues.apache.org/jira/browse/S2GRAPH-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15721763#comment-15721763
 ] 

Hyunsung Jo commented on S2GRAPH-128:
-

The documentation has been added to the following location:
https://steamshon.gitbooks.io/s2graph-book/content/create_a_label.html

> Document new feature S2GRAPH-123 (Support different index on out/in direction)
> --
>
> Key: S2GRAPH-128
> URL: https://issues.apache.org/jira/browse/S2GRAPH-128
> Project: S2Graph
>  Issue Type: Task
>        Reporter: Hyunsung Jo
>        Assignee: Hyunsung Jo
>Priority: Trivial
>
> [~steamshon] Let me document the new feature S2GRAPH-123 based on the PR and 
> JIRA issue.



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

[jira] [Commented] (S2GRAPH-1) Add Redis storage(Key/Value storage) engine for S2Graph

2016-12-05 Thread Hyunsung Jo (JIRA)


[ 
https://issues.apache.org/jira/browse/S2GRAPH-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15721741#comment-15721741
 ] 

Hyunsung Jo commented on S2GRAPH-1:
---

Actually, could someone close this issue?
It seems like I have no rights.
I've created a clone.

> Add Redis storage(Key/Value storage) engine for S2Graph
> ---
>
> Key: S2GRAPH-1
> URL: https://issues.apache.org/jira/browse/S2GRAPH-1
> Project: S2Graph
>  Issue Type: Task
>Reporter: Junki Kim
>        Assignee: Hyunsung Jo
>  Labels: features
>
> h2. Background
> The purpose of S2Graph is to support all features of edge/vertex operations  
> with HBase. It is also to orchestrate with HBase’s key features such as scale 
> out / fault tolerant / highly available / etc. However, if there is no 
> engineer to support stably in managing Hadoop cluster, it is very difficult 
> to operate and maintain HBase and Hadoop clusters. Some companies, which 
> already have another key/value storages to serve their services, may want to 
> use S2Graph and also maintain their existing key/value storage environment. 
> With S2Graph’s persistent storage, we would have a better support in 
> operating another key/value storage. This is because S2Graph already has a 
> strong feature, which can support multiple storage engines.
> What is best key/value storage engine starting to support S2Graph?
> Can companies maintain their existing key/value storage engine and use 
> S2Graph at the same time? Yes, they can.
> Most of companies already have cache layers using Redis or Memcache. It is ok 
> for the companies to start with one of these storages to support another 
> key/value storage engine. It is because Redis is already suitable to support 
> HA and fault tolerant features. Therefore, they do not need to replace this 
> existing key/value storage engine.
> h2. Requirements
> - Support S2Graph storage engine’s interface
> -- Insert/Delete/Increment/etc.
> -- Query
> - Support serializer/deserializer to make edge/vertex data suit to key/value 
> storage’s schema ( e.g. byte array encoding/decoding )
> - Support idempotent feature (this is a similar feature to S2Graph)
> - Design saving schema for edge(IndexEdge, SnapshotEdge) / vertex
> - Support query builder for S2Graph’s getEdges syntax
> - etc.
> I would like to invite everyone to openly discuss about this. I will also 
> make a to-do list before I carry this issue in depth. Your feedback is 
> appreciated :)
> P.S.
> I couldn't fill some information about this issue, e.g. affected version, fix 
> version, component, etc. Please help me to fill out these mandatory fields. 
> In addition, this issue is umbrella issue for real subsequent tasks, so I 
> would like to make this epic issue. Can anyone help me out? I am new to 
> create apache jira issue :)



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

[jira] [Assigned] (S2GRAPH-1) Add Redis storage(Key/Value storage) engine for S2Graph

2016-12-05 Thread Hyunsung Jo (JIRA)


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

Hyunsung Jo reassigned S2GRAPH-1:
-

Assignee: Hyunsung Jo  (was: Junki Kim)

> Add Redis storage(Key/Value storage) engine for S2Graph
> ---
>
> Key: S2GRAPH-1
> URL: https://issues.apache.org/jira/browse/S2GRAPH-1
> Project: S2Graph
>  Issue Type: Task
>Reporter: Junki Kim
>        Assignee: Hyunsung Jo
>  Labels: features
>
> h2. Background
> The purpose of S2Graph is to support all features of edge/vertex operations  
> with HBase. It is also to orchestrate with HBase’s key features such as scale 
> out / fault tolerant / highly available / etc. However, if there is no 
> engineer to support stably in managing Hadoop cluster, it is very difficult 
> to operate and maintain HBase and Hadoop clusters. Some companies, which 
> already have another key/value storages to serve their services, may want to 
> use S2Graph and also maintain their existing key/value storage environment. 
> With S2Graph’s persistent storage, we would have a better support in 
> operating another key/value storage. This is because S2Graph already has a 
> strong feature, which can support multiple storage engines.
> What is best key/value storage engine starting to support S2Graph?
> Can companies maintain their existing key/value storage engine and use 
> S2Graph at the same time? Yes, they can.
> Most of companies already have cache layers using Redis or Memcache. It is ok 
> for the companies to start with one of these storages to support another 
> key/value storage engine. It is because Redis is already suitable to support 
> HA and fault tolerant features. Therefore, they do not need to replace this 
> existing key/value storage engine.
> h2. Requirements
> - Support S2Graph storage engine’s interface
> -- Insert/Delete/Increment/etc.
> -- Query
> - Support serializer/deserializer to make edge/vertex data suit to key/value 
> storage’s schema ( e.g. byte array encoding/decoding )
> - Support idempotent feature (this is a similar feature to S2Graph)
> - Design saving schema for edge(IndexEdge, SnapshotEdge) / vertex
> - Support query builder for S2Graph’s getEdges syntax
> - etc.
> I would like to invite everyone to openly discuss about this. I will also 
> make a to-do list before I carry this issue in depth. Your feedback is 
> appreciated :)
> P.S.
> I couldn't fill some information about this issue, e.g. affected version, fix 
> version, component, etc. Please help me to fill out these mandatory fields. 
> In addition, this issue is umbrella issue for real subsequent tasks, so I 
> would like to make this epic issue. Can anyone help me out? I am new to 
> create apache jira issue :)



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

[jira] [Commented] (S2GRAPH-1) Add Redis storage(Key/Value storage) engine for S2Graph

2016-12-05 Thread Hyunsung Jo (JIRA)


[ 
https://issues.apache.org/jira/browse/S2GRAPH-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15721726#comment-15721726
 ] 

Hyunsung Jo commented on S2GRAPH-1:
---

Hi [~steamshon],

Thanks for the feedback.
In that case let me close this issue and open a new one.
This issue is too old and code changes in the PR are rather outdated.

Jo


> Add Redis storage(Key/Value storage) engine for S2Graph
> ---
>
> Key: S2GRAPH-1
> URL: https://issues.apache.org/jira/browse/S2GRAPH-1
> Project: S2Graph
>  Issue Type: Task
>Reporter: Junki Kim
>Assignee: Junki Kim
>  Labels: features
>
> h2. Background
> The purpose of S2Graph is to support all features of edge/vertex operations  
> with HBase. It is also to orchestrate with HBase’s key features such as scale 
> out / fault tolerant / highly available / etc. However, if there is no 
> engineer to support stably in managing Hadoop cluster, it is very difficult 
> to operate and maintain HBase and Hadoop clusters. Some companies, which 
> already have another key/value storages to serve their services, may want to 
> use S2Graph and also maintain their existing key/value storage environment. 
> With S2Graph’s persistent storage, we would have a better support in 
> operating another key/value storage. This is because S2Graph already has a 
> strong feature, which can support multiple storage engines.
> What is best key/value storage engine starting to support S2Graph?
> Can companies maintain their existing key/value storage engine and use 
> S2Graph at the same time? Yes, they can.
> Most of companies already have cache layers using Redis or Memcache. It is ok 
> for the companies to start with one of these storages to support another 
> key/value storage engine. It is because Redis is already suitable to support 
> HA and fault tolerant features. Therefore, they do not need to replace this 
> existing key/value storage engine.
> h2. Requirements
> - Support S2Graph storage engine’s interface
> -- Insert/Delete/Increment/etc.
> -- Query
> - Support serializer/deserializer to make edge/vertex data suit to key/value 
> storage’s schema ( e.g. byte array encoding/decoding )
> - Support idempotent feature (this is a similar feature to S2Graph)
> - Design saving schema for edge(IndexEdge, SnapshotEdge) / vertex
> - Support query builder for S2Graph’s getEdges syntax
> - etc.
> I would like to invite everyone to openly discuss about this. I will also 
> make a to-do list before I carry this issue in depth. Your feedback is 
> appreciated :)
> P.S.
> I couldn't fill some information about this issue, e.g. affected version, fix 
> version, component, etc. Please help me to fill out these mandatory fields. 
> In addition, this issue is umbrella issue for real subsequent tasks, so I 
> would like to make this epic issue. Can anyone help me out? I am new to 
> create apache jira issue :)



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

[jira] [Commented] (S2GRAPH-133) Deprecating Vagrant environment.

2016-12-05 Thread Hyunsung Jo (JIRA)


[ 
https://issues.apache.org/jira/browse/S2GRAPH-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15721712#comment-15721712
 ] 

Hyunsung Jo commented on S2GRAPH-133:
-

(/) remove from code: https://github.com/apache/incubator-s2graph/pull/106
(/) remove from gitbook

> Deprecating Vagrant environment.
> 
>
> Key: S2GRAPH-133
> URL: https://issues.apache.org/jira/browse/S2GRAPH-133
> Project: S2Graph
>  Issue Type: Improvement
>Reporter: Daewon Jeong
>        Assignee: Hyunsung Jo
>Priority: Minor
>
> Since the Vagrant environment was added, it is no longer being managed.
> Remove the Vagrant environment according to the results discussed in the link 
> below.
> https://lists.apache.org/thread.html/f375558a35f17c4962abb003513f613e3448bf28ea44054593d6e670@%3Cdev.s2graph.apache.org%3E



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

Re: [jira] [Commented] (S2GRAPH-108) Support continuous integration test

2016-11-30 Thread Hyunsung Jo

+1
Thank you, Injun!

On Wed, Nov 30, 2016 at 3:52 PM ASF GitHub Bot (JIRA) 
wrote:

>
> [
> https://issues.apache.org/jira/browse/S2GRAPH-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15707776#comment-15707776
> ]
>
> ASF GitHub Bot commented on S2GRAPH-108:
> 
>
> GitHub user ijsong opened a pull request:
>
> https://github.com/apache/incubator-s2graph/pull/102
>
> [S2GRAPH-108] Support continuous integration test
>
> Add travis
>
> You can merge this pull request into a Git repository by running:
>
> $ git pull https://github.com/ijsong/incubator-s2graph S2GRAPH-108
>
> Alternatively you can review and apply these changes as the patch at:
>
> https://github.com/apache/incubator-s2graph/pull/102.patch
>
> To close this pull request, make a commit to your master/trunk branch
> with (at least) the following in the commit message:
>
> This closes #102
>
> 
> commit 7022a1e860b518bd81378b9582a607402f2d9979
> Author: Injun Song 
> Date:   2016-11-30T03:13:31Z
>
> travis setting
>
> commit a7fbb1f32f438bddfb81264958d962cc82740a35
> Author: Injun Song 
> Date:   2016-11-30T03:15:28Z
>
> fix
>
> commit bc3e3b9f3d4d3462cbe38a91ba4a6e9f3af1c059
> Author: Injun Song 
> Date:   2016-11-30T05:26:13Z
>
> add services
>
> commit 124e92a6e81252a26b3ed6955adbdee1b06a5c8a
> Author: Injun Song 
> Date:   2016-11-30T05:46:21Z
>
> change scala version
>
> commit 95bd2ec1d85c764a441944280fe102f76413bce9
> Author: Injun Song 
> Date:   2016-11-30T05:58:39Z
>
> script for download/run hbase
>
> commit be023808daab199c5c48aace63f201b806fe687d
> Author: Injun Song 
> Date:   2016-11-30T06:21:08Z
>
> fix: scala version
>
> commit 5103b3a9df52926f28e87c76d15dd6e7d6341514
> Author: Injun Song 
> Date:   2016-11-30T06:29:51Z
>
> Add travis status image to README.md
>
> commit 13d3b4d7fc942b2805e34e8cdebc1698af63fb4f
> Author: Injun Song 
> Date:   2016-11-30T06:47:15Z
>
> turn of verbose output of untar hbase
>
> commit 345c83c904a6d3201b576b6e018fcecacbe5fb2f
> Author: Injun Song 
> Date:   2016-11-30T06:48:29Z
>
> Merge branch 'S2GRAPH-108' of
> https://github.com/ijsong/incubator-s2graph into S2GRAPH-108
>
> 
>
>
> > Support continuous integration test
> > ---
> >
> > Key: S2GRAPH-108
> > URL: https://issues.apache.org/jira/browse/S2GRAPH-108
> > Project: S2Graph
> >  Issue Type: Test
> >Reporter: Injun Song
> >
> > We can build/test periodically by using CI, for example Travis-CI (
> https://travis-ci.org/) and Appveyor (https://www.appveyor.com/).
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>

Re: [DISCUSS] Support Apache TinkerPop and Gremlin

2016-11-27 Thread Hyunsung Jo

Hi All,
>From the three options that Hongki suggested, using S2Graph serviceName and
columnName as TinkerPop3 Vertex Label seems like the most intuitive. So +1
on that.

Regards,
Jo

On Fri, Nov 25, 2016 at 12:50 PM hongki kim  wrote:

> I concluded my thoughts briefly, and I agree that the details are lacking.
> Let me write a little more detail.
>
>
>  - The Vertex attribute allows individual filtering but is inconvenient
> I enter the code to encourage this props is not natural, I think.
> Serialize / Deserialize will cost more.
> The following example is an individual filtering of the ServiceName and
> ColumnName I think.
> Ex) g.V (). Has ( "serviceName", "gogo")
>
> => I think that Vertex Property uses java.util.Map, and the string
> "serviceName" and "columName" should always be serialized together. Of
> course, you can also use "_s" or "_c". And I worry that it will be used as
> a reserved Property Key with only s2graph.
>
>
> - If you put a serviceColumn in the id, it will be cumbersome to compare
> The id value itself or to the operation like "summary".
>
>
> => My English skills were not very good, so I guess it was not accurate.
> What I was concerned about was that when I set up several vertex ids, I was
> worried that gremlin would list them with the following expression:
> Ex) g.V(new S2VertexId (1,"gogo", "userid"), new S2VertexId (2,"gogo",
> "userid") )
>
> Also, I was wondering if the following operation would work in the summary
> part. The idea is that the S2VertexId object needs to return the actual id.
> Ex) g.V().id().sum() #tp3
>   g.V().id().id().sum()  # s2graph (with S2VertexId)
>
>
>
> Thanks for reading
>
>
>
>
>
> 2016-11-24 22:57 GMT+09:00 DO YUNG YOON :
>
> > Hi 김홍기 and Welcome to the S2Graph.
> >
> > It seems that you already know internal model that S2Graph is using but
> let
> > me explain it for others who are not familiar with it to discuss issue 3
> in
> > more detail.
> >
> > Instead of convert user provided Id into internal unique numeric Id,
> > S2Graph simply composite service and column metadata with user provided
> Id
> > to guarantee global unique Id.
> > Here are some important notation.
> >
> > 1. Service - the top level abstraction
> >   - A convenient logical grouping of related entities
> >   - Similar to the database abstraction that most relational databases
> > support.
> >
> > 2. Column - belongs to a service.
> >   - A set of homogeneous vertices such as users, news articles or tags.
> >   - Every vertex has a user-provided unique ID that allows the efficient
> > lookup.
> >   - A service typically contains multiple columns.
> >
> > 3. Label - schema for edge
> >   - A set of homogeneous edges such as friendships, views, or clicks.
> >   - Relation between two columns as well as a recursive association
> within
> > one column.
> >   - The two columns connected with a label may not necessarily be in the
> > same service, allowing us to store and query data that spans over
> multiple
> > services.
> >
> >
> > From your suggestion, here is what I thought.
> >
> > 1. Put the ServiceName and columnName in the vertex property
> > ex) graph.addVertex(T.Id, 1, "serviceName". "gogo", columnName , "user")
> >
> > 2. Replace tp3 id with S2graph VertexId (ServiceName, columnName, id)
> > ex) graph.addVertex(T.Id, new S2VertexId(1, "gogo", "user"))
> >
> > 3. Use Vertex Label
> > ex) graph.addVertex(T.label, "gogo::user", T.id, 1 )
> >
> > First of all, I think if we ignore Service and Column on vertex, then
> there
> > is no way to guarantee the global uniqueness of id 1. If my service has
> > user id 1 and your service has user id 1, then there is no way to
> > distinguish
> > same 1 without Service and Column, so I think ignoring them is not an
> > option for us.
> >
> > I am +1 on Use Vertex Label to map S2Graph's Service, Column notation
> into
> > tp3 in general and forcing user to provide vertex label on vertex.
> >
> > Concatenate serviceName and columnName with "::" does not looks like best
> > for me, but it should be fine, since client users will never need to
> > separate serviceName and columnName from given string. existing users of
> > Tinkerpop should be familiar with vertex label notation so I think it is
> > best option.
> >
> > Also I think being more explicit also make sense, so option 2 seems ok
> for
> > me too. users can be notified by thrown exception if they not provide
> > S2VertexId type for T.id value, but this is not as familiar as
> vertexLabel.
> >
> > By the way, I don't quite understand the reasons you mentioned below, so
> > can you please elaborate them one more time?
> >
> > - Using the vertex property allows individual filtering but is
> inconvenient
> > to input, and the code that forces this props is unnatural and I think it
> > will cost more in Serialize / Deserialize
> > - If you put a serviceColumn in the id, it will be cumbersome to compare
> > the id value

[jira] [Commented] (S2GRAPH-128) Document new feature S2GRAPH-123 (Support different index on out/in direction)

2016-11-16 Thread Hyunsung Jo (JIRA)


[ 
https://issues.apache.org/jira/browse/S2GRAPH-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15671194#comment-15671194
 ] 

Hyunsung Jo commented on S2GRAPH-128:
-

Here is  the first draft. Let me know what you think.
{noformat}
 Directional Indices and Sampling (Optional) 
An S2Graph label can be indexed on different properties on different directions 
as well as apply different methods of sampling in order to avoid hot regions.
A common use case for this feature is when indexing user clicks. It is quite 
common for a small number of articles to get most of the clicks (usually the 
most popular or featured). In such cases, it would be helpful to be able to 
drop a predefined proportion of in-direction `index edges`.
Available index directions are `in`, `out`, and `both`.
While each property-direction pair can select from `drop`, `sample`, and 
`hash_sample` as its sampling method. Please note that `sample` method is used 
for random sampling while `hash_sample` is for quota sampling. `sample` and 
`hash_sample` methods require a `rate` option as a sampling rate while 
`hash_sample` requires an additional option field of `totalModular` to set the 
quota. Whether or not the degree of an index will be stored is determined by a 
`degree` option. 
```
"indices": [
  {
"name": "_PK",
"propNames": [
  "_timestamp"
], 
"direction": "out" // [both/in/out, default both], 
"options": {
  "method": "hash_sample" // [drop, sample, hash_sample],
  "totalModular": 100, 
  "rate": 0.1, 
  "degree": true
}
  }
]
```
{noformat}

> Document new feature S2GRAPH-123 (Support different index on out/in direction)
> --
>
> Key: S2GRAPH-128
> URL: https://issues.apache.org/jira/browse/S2GRAPH-128
> Project: S2Graph
>  Issue Type: Task
>Reporter: Hyunsung Jo
>Assignee: Hyunsung Jo
>Priority: Trivial
>
> [~steamshon] Let me document the new feature S2GRAPH-123 based on the PR and 
> JIRA issue.



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

[jira] [Created] (S2GRAPH-128) Document new feature S2GRAPH-123 (Support different index on out/in direction)

2016-11-16 Thread Hyunsung Jo (JIRA)

Hyunsung Jo created S2GRAPH-128:
---

 Summary: Document new feature S2GRAPH-123 (Support different index 
on out/in direction)
 Key: S2GRAPH-128
 URL: https://issues.apache.org/jira/browse/S2GRAPH-128
 Project: S2Graph
  Issue Type: Task
Reporter: Hyunsung Jo
Assignee: Hyunsung Jo
Priority: Trivial


[~steamshon] Let me document the new feature S2GRAPH-123 based on the PR and 
JIRA issue.



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

Re: [DISCUSS] decide actual contents on our web site.

2016-11-09 Thread Hyunsung Jo

Hey all,
Perhaps the website could have an announcement/ news section so that worthy
information (releases, conferences, or meetups) can be shared with the
community.
(preferably twitter-integrated so that featured news can be managed from
one place)

Regards,
Jo

On Sat, Nov 5, 2016 at 12:03 PM Hwansung Yu  wrote:

> I totally agree your opinion.
> Making our web site is as important as making S2Graph.
> I think it is enough that you mentioned above.
> I can contribute easily to create download page and release note.
>
> Who could contribute to other things in list?
>
> On Wed, Nov 2, 2016 at 10:37 AM, DO YUNG YOON  wrote:
>
> > Hi folks.
> >
> > We have not discussed the contents of our website yet, and I think it is
> > time to discuss it in details.
> >
> > Following is my suggestions and please feel free to comment on them.
> >
> > 1. create download pages and put release note there.
> > 2. Separate `Use` and `Learn`.
> > 2.1 `Use`
> > - Overview: introduction to model.
> > - Quickstart: getting started manual.
> > - Examples: more examples can help user to undestand usecases.
> > 2.2 `Learn`
> > - Basic Concept: Snapshot/Index Edge, Index, Query, Bulk Loader, Super
> > Node, Consistency, Storage Backend, etc.
> > - Resources: Presentation materials
> > 3. Contribute
> >   - Contribution Guide: how to get involved.
> > - Work In Progress: list up starter tasks, feature branches so any new
> > contributor can easily contribute.
> > - Mailling Lists
> > - Source Repository
> > - Issue Tracking
> >
> > 4. Project
> >   - Meetings
> > - F.A.Q
> > I am sure above suggestion is very arguable, but I just want to begin
> this
> > discussion because I think it is important.
> > Please give any feedback and hopefully want others to get involve to make
> > our site better shape.
> >
> > Thanks.
> > DOYUNG YOON
> >
>

Re: [DISCUSS] milestone for next release.

2016-11-03 Thread Hyunsung Jo

Hi Doyung,

There was a recent PR in Zeppelin to integrate with Neo4j. (
https://github.com/apache/zeppelin/pull/1582)
Something like this for S2Graph might interest both the dev + user
community.
Although, technically it would be a code contribution to Zeppelin rather
than S2Graph.

Regards,
Jo
On Fri, Nov 4, 2016 at 1:52 AM DO YUNG YOON  wrote:

> Hi all.
>
> I think it is time for us to build consensus on milestone for next release.
> Let me suggest few to start this discussion.
>
> 1. Basic implementation for Tinkerpop3.
>
> Many people already asked if they can use S2Graph with tinkerpop. I have
> played around at https://issues.apache.org/jira/browse/S2GRAPH-72 issue,
> but never polished it yet. I am thinking about provide java client that
> implement tinkerpop3 interface by call s2graph core, because java has much
> wide range of users and it also can be used by scala users too.
>
> Also I have realized that we can take advantage of tinkerpop's
> OLAP(Hadoop-Gremlin) ability by providing layer translating GraphIO between
> S2Graph's format to Tinkerpop's format.
>
> Also I think existing userbase for gremlin-console, gremlin-server can take
> benefits from this and we may hopefully increase our reach to more broad
> audience.
>
> 2. Various Storage Backend.
>
> We have tested if our interface is pluggable for storage backend by playing
> around RocksDBStorage. I think it is time for us actually provide more
> storage backend plugins so users who do not use HBase can also be benefit
> from S2Graph.
>
> Many startup users who contact me asked if they can use S2Graph with mysql,
> postgresql, and redis. Actually, we have implemented RedisStorage
> once(S2GRAPH-1), but never merged PR. Since then, our interface has been
> changed so we need to make sure this awesome PR included into our codebase.
>
> I think working on storage backend plugin is great way to interact with
> code base, so I encourage others(especially committers) to try out this.
>
> I am thinking of followings.
> - Any system that JDBC can talk to.
> - postgresl
> - mysql
> - etc...
> - Cassandra(for big graph).
> - Redis(S2GRAPH-1, for small graph).
> - etc...
>
> Personally I think this is most important discussion for now since anyone
> interested in S2Graph can see where we are heading and hopefully encourage
> more developers to participate in S2Graph.
>
> Please feel free to give any feedback and comment and hope to discuss this
> further with all.
>
> Thanks
> DOYUNG YOON
>

Re: question about conistencyLevel - weak

2016-07-12 Thread Hyunsung Jo

Hi eureka386,

Please try option "duplicate": "raw" as shown in the following request:

curl -XPOST localhost:9000/graphs/getEdges -H 'Content-Type:
Application/json' -d '
{
"srcVertices": [{"serviceName": "KakaoFavorites", "columnName":
"userName", "id":"101"}],
"steps": [
  {"step": [{"label": "s2graph_label_test_weak", "direction": "out",
"offset": 0, "limit": 100, "duplicate": "raw"}]}
]
} '

You can find the specs here:
https://steamshon.gitbooks.io/s2graph-book/content/query_param_level_option.html
https://steamshon.gitbooks.io/s2graph-book/content/getedges.html

Regards,
Jo




On Wed, Jul 13, 2016 at 11:18 AM eureka386  wrote:

> Hi again.
>
> I have another question about weak consistencyLevel.
> according to the manual, s2graph has tow types of consistency
> level:strong, weak
> I want to get several edges between two vertices, so, I set a weak
> consistency level.
> after setting, I tried to get edges, but it returned only one edge like
> ‘strong’ level.
>
> What is wrong with my query?
>
>
>
> here is my setting and queries.
>
> 
>
> 1. create a service
>
> curl -XPOST localhost:9000/graphs/createService -H 'Content-Type:
> Application/json' -d '
> {"serviceName": "KakaoFavorites", "compressionAlgorithm" : "gz"}
> ‘
>
>
> 2. create a level
>
> curl -XPOST localhost:9000/graphs/createLabel -H 'Content-Type:
> Application/json' -d '
> {
>   "label": "s2graph_label_test_weak",
>   "srcServiceName": "KakaoFavorites",
>   "srcColumnName": "userName",
>   "srcColumnType": "string",
>   "tgtServiceName": "KakaoFavorites",
>   "tgtColumnName": "userName",
>   "tgtColumnType": "string",
>   "isDirected": "true",
>   "indices": [],
>   "props": [
>   {"name": "time", "defaultValue": 0, "dataType": "long"}
>   ],
>   "consistencyLevel": "weak"
> }
> ‘
>
>
> 3. insert edges with meta data
>
> curl -XPOST localhost:9000/graphs/edges/insert -H 'Content-Type:
> Application/json' -d'
> [
> {"timestamp": 1, "from": 101, "to": 10, "label":
> "s2graph_label_test_weak", "props": {"time": 0}},
> {"timestamp": 2, "from": 101, "to": 10, "label":
> "s2graph_label_test_weak", "props": {"time": -10}},
> {"timestamp": 3, "from": 101, "to": 10, "label":
> "s2graph_label_test_weak", "props": {"time": -30}}
> ]
> '
>
>
>
> 4. query id “101” and direction “out”
>
> curl -XPOST localhost:9000/graphs/getEdges -H 'Content-Type:
> Application/json' -d '
> {
> "srcVertices": [{"serviceName": "KakaoFavorites", "columnName":
> "userName", "id":"101"}],
> "steps": [
>   {"step": [{"label": "s2graph_label_test_weak", "direction": "out",
> "offset": 0, "limit": 100}]}
> ]
> }
> ‘
>
>
> 5. it returns like this
>
> ===
> [true,true,true]vagrant@vagrant-ubuntu-trusty-64:~$
> vagrant@vagrant-ubuntu-trusty-64:~$
> vagrant@vagrant-ubuntu-trusty-64:~$ curl -XPOST
> localhost:9000/graphs/getEdges -H 'Content-Type: Application/json' -d '
> > {
> > "srcVertices": [{"serviceName": "KakaoFavorites", "columnName":
> "userName", "id":"101"}],
> > "steps": [
> >   {"step": [{"label": "s2graph_label_test_weak", "direction": "out",
> "offset": 0, "limit": 100}]}
> > ]
> > }
> > '
>
>
> {"size":1,"degrees":[{"from":"101","label":"s2graph_label_test_weak","direction":"out","_degree":3}],"results":[{"cacheRemain":-636,"timestamp":3,"score":1.0,"label":"s2graph_label_test_weak","direction":"out","to":"10","_timestamp":3,"from":"101","props":{"_timestamp":3,"_count":-1,"time":-30}}]}
>
> ===
>
>
>
>

Re: Guide for Newbie

2016-07-05 Thread Hyunsung Jo

Hi Chiwan,

Did you have any updates on S2GRAPH-12?
Lately from S2Graph user community, there have been several requests
concerning this feature, so I think we should bump up the priority of the
issue.
Not sure how this usually works, but 1) if you had any difficulties with
the issue feel free to ask for some pointers or 2) you could simply
re-assign the ticket to someone else.
Your thoughts?

Jo



On Wed, Feb 24, 2016 at 10:25 AM Chiwan Park <chiwanp...@apache.org> wrote:

> Hi Jo,
>
> Thanks for kindly guidance. I’ll look into the issue (S2GRAPH-12).
>
> Regards,
> Chiwan Park
>
> > On Feb 24, 2016, at 9:15 AM, Hyunsung Jo <hyunsung...@gmail.com> wrote:
> >
> > Hi Chiwan,
> >
> > Welcome to S2Graph!
> > At the moment, most of the entry level issues seem to be already assigned
> > or resolved.
> > However, this one seems like something that might interest you:
> >
> https://issues.apache.org/jira/browse/S2GRAPH-12?jql=project%20%3D%20S2GRAPH
> > I've added a detailed spec based on what has been discussed so far, so
> take
> > a look and see if you like it.
> > If you do, maybe we can ask someone to assign the ticket to you.
> >
> > Regards,
> > Jo
> >
> >
> > On Tue, Feb 23, 2016 at 11:39 AM Chiwan Park <chiwanp...@apache.org>
> wrote:
> >
> >> Hello everyone,
> >>
> >> I’m Chiwan Park, a graduate student in Data Mining Lab. at Seoul
> National
> >> University [1] and a committer of Apache Flink [2]. I'm interested in
> >> S2Graph because it is related to my research topic.
> >>
> >> I’m actively looking for starter or newbie issues to work on, but would
> >> appreciate some suggestions from the community. If you would like to
> point
> >> something which I can work on, please feel free to give me your
> feedback.
> >>
> >> Thank you all in advance, I look forward to join the community as a
> active
> >> contributor.
> >>
> >> Regards,
> >> Chiwan Park
> >>
> >> [1]: http://datalab.snu.ac.kr
> >> [2]: http://flink.apache.org
>
>

Re: Tutorial within tens of minutes.

2016-06-23 Thread Hyunsung Jo

Min-Seok,
Sounds like a great idea.
A tutorial will help S2Graph reach more users.
I'd love to help.

Thanks,
Jo

On Thu, Jun 23, 2016 at 10:30 AM Min-Seok Kim  wrote:

> Hi, folks!
>
> I'm going to write a tutorial(with dataset) like:
>  - neo4j: https://neo4j.com/blog/analyzing-panama-papers-neo4j/
>  - orientDB: http://orientdb.com/orientdb-game-of-graphs/
>  - dgraph: https://dgraph.io/
>
> This tutorial will aim that newbies are getting familiar with S2Grpah
> within tens of minutes
> to provide simple installation(using Docker?), core instructions with
> dataset, and visualization.
>
> Any comment please.
>
> thanks,
>
> Minseok
>

Re: [jira] [Commented] (S2GRAPH-82) Merge DeferCache and FutureCache.

2016-05-30 Thread Hyunsung Jo

Doyung,

I think it's a good idea to provide a common interface for DeferCache and
FutureCache.
This will reduce redundancy.
+1

Jo

On Sat, May 28, 2016 at 3:07 PM ASF GitHub Bot (JIRA) 
wrote:

>
> [
> https://issues.apache.org/jira/browse/S2GRAPH-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15305200#comment-15305200
> ]
>
> ASF GitHub Bot commented on S2GRAPH-82:
> ---
>
> GitHub user SteamShon opened a pull request:
>
> https://github.com/apache/incubator-s2graph/pull/54
>
> [S2GRAPH-82] Merge DeferCache and FutureCache.
>
> This is work done by @daewon. I am just trying to merge.
>
> This PR is merge two classes FutureCache/DeferCache into one using
> type class.
>
> You can merge this pull request into a Git repository by running:
>
> $ git pull https://github.com/SteamShon/incubator-s2graph S2GRAPH-82
>
> Alternatively you can review and apply these changes as the patch at:
>
> https://github.com/apache/incubator-s2graph/pull/54.patch
>
> To close this pull request, make a commit to your master/trunk branch
> with (at least) the following in the commit message:
>
> This closes #54
>
> 
> commit 4e08d43911d9e8e19c605c018e2240633d019bde
> Author: daewon 
> Date:   2016-04-19T09:00:21Z
>
> [S2GRAPH-82] Merge DeferCache and FutureCache.
>
> 
>
>
> > Merge DeferCache and FutureCache.
> > -
> >
> > Key: S2GRAPH-82
> > URL: https://issues.apache.org/jira/browse/S2GRAPH-82
> > Project: S2Graph
> >  Issue Type: Improvement
> >Reporter: DOYUNG YOON
> >Assignee: Daewon Jeong
> >   Original Estimate: 168h
> >  Remaining Estimate: 168h
> >
> > Currently, under org.apache.s2graph.core.utils package, {{DeferCache}}
> and {{FutureCache}} has exactly same behavior except for their Types on
> Value to store.
> > It would be better if we can merge these two class. The problem is that
> there is no common interface between asynchbase's {{Deferr}} and scala's
> {{Future}}.
> > I was talk with [~daewon] and here is what we are suggesting, use type
> class.
> > {noformat}
> > trait CanDefer[A, M[_], C[_]] {
> >   def promise: M[A]
> >   def future(defer: M[A]): C[A]
> >   def success(defer: M[A], value: A): Unit
> >   def onSuccess[U](defer: C[A])(pf: PartialFunction[A, U])(implicit ec:
> ExecutionContext)
> > }
> > {noformat}
> > and change DeferCache interface as follow.
> > {noformat}
> > * M[_] : container type that will be stored in local cache. ex) Promise,
> Defer.
> > * C[_]: container type that will be returned to client of this class.
> Ex) Future, Defer.
> > * A: actual element type that will be stored in M[_]  and C[_].
> > class DeferCache[A, M[_], C[_]](config: Config)(implicit ec:
> ExecutionContext, canDefer: CanDefer[A, M, C])
> > {noformat}
> > First, define some type class CanDefer that has all common interfaces
> used in current DeferCache/FutureCache implementation.
> > Secondly, provide implicit value for both of Defer and Future.
> > Third, change implimentation to use common type class.
> > This is what we have sofar, but any better idea would be appreciated.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>

Re: [jira] [Created] (S2GRAPH-83) Update document according to refactoring.

2016-05-30 Thread Hyunsung Jo

+1

On Sat, May 28, 2016 at 3:33 PM DOYUNG YOON (JIRA)  wrote:

> DOYUNG YOON created S2GRAPH-83:
> --
>
>  Summary: Update document according to refactoring.
>  Key: S2GRAPH-83
>  URL: https://issues.apache.org/jira/browse/S2GRAPH-83
>  Project: S2Graph
>   Issue Type: Sub-task
> Reporter: DOYUNG YOON
> Assignee: DOYUNG YOON
>
>
> After S2GRAPH-68, some changes on our write-write conflict resolving logic
> is inevitable.
> Once we resolve S2GRAPH-68, we should update document to address theses
> changes.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>

Re: Website for s2graph.

2016-05-11 Thread Hyunsung Jo

One thing: Was the vote on the logo concluded?

Jo

On Tue, May 10, 2016 at 10:43 PM Jun Ki Kim <wishop...@gmail.com> wrote:

> Great job guys!
> Especially thanks to Hwansung and Sergio.
>
> We finally have our Web Site!
>
>
> Best regards.
>
> 2016년 5월 11일 (수) 오후 2:31, Luke Han <luke...@gmail.com>님이 작성:
>
> > Congratulations, nice website:)
> >
> >
> > Best Regards!
> > -
> >
> > Luke Han
> >
> > On Tue, May 10, 2016 at 10:11 PM, Hwansung Yu <deejayf...@gmail.com>
> > wrote:
> >
> > > Thank you for Sergio!!!
> > >
> > > Finally, we got the site.
> > >
> > > In the future we need to participate.
> > >
> > >
> > > Best Regards.
> > >
> > > On Wed, May 11, 2016 at 3:11 AM, Hyunsung Jo <hyunsung...@gmail.com>
> > > wrote:
> > >
> > > > Congratulations S2Graph!
> > > > Thank you Hwansung and Sergio!
> > > > On 2016년 5월 10일 (화) at 오전 10:54 Sergio Fernández <wik...@apache.org>
> > > > wrote:
> > > >
> > > > > site is now online https://s2graph.incubator.apache.org/ :-)
> > > > >
> > > > >
> > > > >
> > > > > On Tue, May 10, 2016 at 12:48 AM, Hyunsung Jo <
> hyunsung...@gmail.com
> > >
> > > > > wrote:
> > > > >
> > > > > > Thanks, Sergio!
> > > > > >
> > > > > > On Mon, May 9, 2016 at 7:42 AM Sergio Fernández <
> wik...@apache.org
> > >
> > > > > wrote:
> > > > > >
> > > > > > > OK, so far:
> > > > > > >
> > > > > > > * copied content into
> > > > > > >
> > http://svn.apache.org/repos/asf/incubator/s2graph/site/index.html
> > > > > > > (r1742960)
> > > > > > > * filed a cms request to use svnpubsub (r987805)
> > > > > > >
> > > > > > > In the meantime I try to figure out the permission issue, you
> > > should
> > > > > > reads
> > > > > > > the guidelines for a podling site. For instance you miss the
> > > > incubator
> > > > > > > disclaimer among some other things.
> > > > > > >
> > > > > > >
> > > > > > > On Mon, May 9, 2016 at 7:25 AM, Sergio Fernández <
> > > wik...@apache.org>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > OK, I'll take a look to the permissions issue.
> > > > > > > >
> > > > > > > > In the meantime check the different options provided by ASF
> to
> > > > > publish
> > > > > > > > project sites (aka Apache CMS
> > http://www.apache.org/dev/cms.html
> > > )
> > > > > and
> > > > > > > > decide what option you want to pick for the project.
> > > > > > > >
> > > > > > > > On Sun, May 8, 2016 at 7:57 PM, Hwansung Yu <
> > > deejayf...@gmail.com>
> > > > > > > wrote:
> > > > > > > >
> > > > > > > >> Thank you for help.
> > > > > > > >>
> > > > > > > >> But I have no permission.
> > > > > > > >>
> > > > > > > >> I created simple static website.
> > > > > > > >>
> > > > > > > >> Source code located at
> https://github.com/djfwan/s2graph-site
> > .
> > > > > > > >>
> > > > > > > >> I want publish s2graph website.
> > > > > > > >>
> > > > > > > >> How could I publish site?
> > > > > > > >>
> > > > > > > >>
> > > > > > > >> Best Regards
> > > > > > > >>
> > > > > > > >>
> > > > > > > >>
> > > > > > > >> On Sun, May 8, 2016 at 1:10 AM, Sergio Fernández <
> > > > wik...@apache.org
> > > > > >
> > > > > > > >> wrote:
> > > > > > > >>
> > > > > > > >> > From INFRA-11806:
> > > > > > > >> >
> >

Slides for Apache Big Data North America

2016-05-10 Thread Hyunsung Jo

Hi all,
Doyoung is scheduled to give a talk at Apache Big Data North America
(2016.05.12 Vancouver, BC).
Here are the slides so feel free to pitch in any ideas:
https://docs.google.com/presentation/d/1RqAvEChtQV0JwAut8EwKNFALqsBiQcuweboX-fD1YsQ/edit?usp=sharing

Thanks,
Jo

Re: Website for s2graph.

2016-05-10 Thread Hyunsung Jo

Thanks, Sergio!

On Mon, May 9, 2016 at 7:42 AM Sergio Fernández <wik...@apache.org> wrote:

> OK, so far:
>
> * copied content into
> http://svn.apache.org/repos/asf/incubator/s2graph/site/index.html
> (r1742960)
> * filed a cms request to use svnpubsub (r987805)
>
> In the meantime I try to figure out the permission issue, you should reads
> the guidelines for a podling site. For instance you miss the incubator
> disclaimer among some other things.
>
>
> On Mon, May 9, 2016 at 7:25 AM, Sergio Fernández <wik...@apache.org>
> wrote:
>
> > OK, I'll take a look to the permissions issue.
> >
> > In the meantime check the different options provided by ASF to publish
> > project sites (aka Apache CMS http://www.apache.org/dev/cms.html) and
> > decide what option you want to pick for the project.
> >
> > On Sun, May 8, 2016 at 7:57 PM, Hwansung Yu <deejayf...@gmail.com>
> wrote:
> >
> >> Thank you for help.
> >>
> >> But I have no permission.
> >>
> >> I created simple static website.
> >>
> >> Source code located at https://github.com/djfwan/s2graph-site.
> >>
> >> I want publish s2graph website.
> >>
> >> How could I publish site?
> >>
> >>
> >> Best Regards
> >>
> >>
> >>
> >> On Sun, May 8, 2016 at 1:10 AM, Sergio Fernández <wik...@apache.org>
> >> wrote:
> >>
> >> > From INFRA-11806:
> >> >
> >> > I created https://svn.apache.org/repos/asf/incubator/s2graph/site/ in
> >> > r1742723: https://svn.apache.org/r1742723
> >> >
> >> > Please, check if you have the necessary karma to commit there; If not,
> >> I'd
> >> > need to check the group.
> >> >
> >> >
> >> > On Tue, May 3, 2016 at 7:10 PM, Hwansung Yu <deejayf...@gmail.com>
> >> wrote:
> >> >
> >> > > Thank you for your help.
> >> > >
> >> > > I created JIRA issue.
> >> > >
> >> > > https://issues.apache.org/jira/browse/INFRA-11806
> >> > >
> >> > >
> >> > > Regards.
> >> > >
> >> > > On Wed, May 4, 2016 at 10:58 AM, Hyunsung Jo <hyunsung...@gmail.com
> >
> >> > > wrote:
> >> > >
> >> > > > Hwansung,
> >> > > >
> >> > > > Please take a look at the following JIRA:
> >> > > > https://issues.apache.org/jira/browse/INFRA-8972
> >> > > >
> >> > > > It seems like we should
> >> > > > 1. request for a SVN directory
> >> > > > 2. check in the source code to the SVN repo
> >> > > > 3. request for deployment via
> >> https://infra.apache.org/officers/webreq
> >> > > > (only
> >> > > > officers and members seem to have access for this)
> >> > > >
> >> > > > So why don't you go ahead and open a JIRA request for creation of
> >> SVN
> >> > > > directory http://svn.apache.org/repos/asf/incubator/s2graph/site/
> ?
> >> > > >
> >> > > > Regards,
> >> > > >
> >> > > > Jo
> >> > > >
> >> > > >
> >> > > > On Wed, May 4, 2016 at 10:26 AM Hwansung Yu <deejayf...@gmail.com
> >
> >> > > wrote:
> >> > > >
> >> > > > > I want create website for s2graph.
> >> > > > >
> >> > > > > According to the guide(http://www.apache.org/dev/infra-contact
> ),
> >> I
> >> > > > should
> >> > > > > upload code to svn and request to webreq(
> >> > > > > https://infra.apache.org/officers/webreq).
> >> > > > >
> >> > > > > However I have no access.
> >> > > > >
> >> > > > > Webreq is opened to only officer and commiter.
> >> > > > >
> >> > > > > So, I need help about belows.
> >> > > > >
> >> > > > > 1. How can I create svn repo?
> >> > > > > 2. Please, reqeust to webreq.
> >> > > > >
> >> > > > > Best regrards.
> >> > > > >
> >> > > >
> >> > >
> >> >
> >> >
> >> >
> >> > --
> >> > Sergio Fernández
> >> > Partner Technology Manager
> >> > Redlink GmbH
> >> > m: +43 6602747925
> >> > e: sergio.fernan...@redlink.co
> >> > w: http://redlink.co
> >> >
> >>
> >
> >
> >
> > --
> > Sergio Fernández
> > Partner Technology Manager
> > Redlink GmbH
> > m: +43 6602747925
> > e: sergio.fernan...@redlink.co
> > w: http://redlink.co
> >
> > --
> > <http://redlink.co/>
> > <http://redlink.co/>
> > Sergio Fernández
> > Partner Technology Manager
> > Redlink GmbH
> > m: +43 6602747925
> > e:  <http://redlink.co/>sergio.fernan...@redlink.co
> > w: http://redlink.co
> >
>

Re: [Discussion] first release plan.

2016-05-08 Thread Hyunsung Jo

Doyoung,
I'm sure you're the right person for RM.
Looking forward to see the first release.

Jo

On Sun, May 8, 2016 at 8:36 AM DO YUNG YOON  wrote:

> Seems like there is no volunteer for RM yet. then I would like to volunteer
> as RM.
> I would not be the right person for RM since I have no experiences, but I
> am willing to follow process and learn it.
> If everyone agree, then I will go ahead reading
> https://cwiki.apache.org/confluence/display/SQOOP/How+to+Release+Sqoop2
> and
> do what needs to be done.
>
> What do you guys think?
>
> On Mon, May 2, 2016 at 8:29 AM DO YUNG YOON  wrote:
>
> > Thanks for guide, Venkatesh and Sergio.
> > I will definitely read through it to understand the general processes.
> >
> > So first thing to decide, Any volunteer as RM for this release?
> >
> >
> >
> >
> >
> > On Fri, Apr 29, 2016 at 1:43 AM Sergio Fernández 
> > wrote:
> >
> >> Good to finally hear about that :-)
> >>
> >> Be patient, the first incubating release is quite hard regarding many
> >> legal
> >> details. But focus on the technical scope, we'll support you with the
> >> rest.
> >>
> >> On Thu, Apr 28, 2016 at 5:05 PM, DO YUNG YOON  wrote:
> >>
> >> > Hi folks.
> >> >
> >> > We have not discussed how and when we are going to release our first
> >> > version.
> >> > I think we should discuss on scope of first release and list up issues
> >> that
> >> > need to be resolved.
> >> > Not sure how to start, but just wanted to open up thread so we can
> share
> >> > our opinion on release plan.
> >> >
> >>
> >>
> >>
> >> --
> >> Sergio Fernández
> >> Partner Technology Manager
> >> Redlink GmbH
> >> m: +43 6602747925
> >> e: sergio.fernan...@redlink.co
> >> w: http://redlink.co
> >>
> >
>

Re: Provide storage which use HBase's native client(not Asynchbase).

2016-04-20 Thread Hyunsung Jo

It seems like Elasticsearch had similar problems:
https://www.elastic.co/blog/to-shade-or-not-to-shade

On Wed, Apr 20, 2016 at 10:36 AM Jong Wook Kim  wrote:

> As per Guava version conflict, we should be able to shade the dependency
> to another package, maybe with the whole asynchbase together. Guava
> versions have been the PITA for many other projects too, and usually got
> avoided this way.
>
> If we can avoid the Asynchbase+Guava issue by shading them and the only
> interesting reason left to switch is the benchmark, it might not worth
> going back to the blocking API as it will require a whole new threading
> design.
>
> Sincerely,
> Jong Wook
>
>
> Sent from my iPhone
>
> > On Apr 19, 2016, at 9:01 PM, DO YUNG YOON  wrote:
> >
> > Hi All.
> >
> > Since implementing storage becomes easier(I believe), I think it is good
> to
> > have HBaseStroage which use HBase's native client.
> > The reason I brought up this is following.
> >
> > 1. in some environment, especially specific Hadoop and Spark cluster
> > distribution,
> > s2core have guava version conflict which comes from asynchbase.
> >  - Many cases it is necessary to process stream of edges and write into
> > HBase directly on streaming processing.
> >  - Currently, there is no way to specify version to avoid above problem.
> > With Native HBaseClient, users will be select right version for there
> > environment.
> > 2. It would be fun to run benchmark on these two client.
> >
> > any feedback would be appreciated.
> >
> > Best Regards.
> > DOYUNG YOON
>

[jira] [Commented] (S2GRAPH-1) Add Redis storage(Key/Value storage) engine for S2Graph

2016-04-08 Thread Hyunsung Jo (JIRA)


[ 
https://issues.apache.org/jira/browse/S2GRAPH-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15232029#comment-15232029
 ] 

Hyunsung Jo commented on S2GRAPH-1:
---

The [Redis data model document | 
https://docs.google.com/presentation/d/1iAWApMInn4Ae8Y5P7D8Xkj9rjh_qJXObQHEVAMdqc9A/edit#slide=id.gf6049552c_0_0]
 is updated with the latest design changes.
 
Some of the key changes include:
* Snapshot Edge is stored as key value (opposed to sorted set) since it will 
not have multiple values.
* An Index Edge value consists of a Qualifier, non-indexed properties, and the 
length of Qualifier.
  - In HBase, A Qualifier of an Index Edge includes information such as index 
prop. values, target vertex ids, and op. codes. Since Redis is not a 
column-oriented storage, the same information is prepended to the value with an 
additional timestamp for default timestamp ordering. For lack of a better term, 
we call it Qualifier :).
  - Length of the Qualifier is appended at the end of the value.
  - Edge degree is handled by ZCARD.
* Vertex Edge updates are managed with an index field at the end of the value. 

We also have a couple of issues that should be discussed: 
* Table not supported: Originally, we considered keeping a virtual Table 
information in the key since Redis Cluster does not support multiple tables. 
However, performance issues when dropping all records in a table was a concern 
so decided not worry about Tables too much during POC stage.
* ```incrementCounts``` is not yet implemented: This operation is used 
exclusively by S2Counter. With the current Redis data model, incrementCounts 
seemed like too much complication. But, I think we can overcome this by 
utilizing the original S2Counter design which also used Redis.

> Add Redis storage(Key/Value storage) engine for S2Graph
> ---
>
> Key: S2GRAPH-1
> URL: https://issues.apache.org/jira/browse/S2GRAPH-1
> Project: S2Graph
>  Issue Type: Task
>Reporter: Junki Kim
>Assignee: Junki Kim
>  Labels: features
>
> h2. Background
> The purpose of S2Graph is to support all features of edge/vertex operations  
> with HBase. It is also to orchestrate with HBase’s key features such as scale 
> out / fault tolerant / highly available / etc. However, if there is no 
> engineer to support stably in managing Hadoop cluster, it is very difficult 
> to operate and maintain HBase and Hadoop clusters. Some companies, which 
> already have another key/value storages to serve their services, may want to 
> use S2Graph and also maintain their existing key/value storage environment. 
> With S2Graph’s persistent storage, we would have a better support in 
> operating another key/value storage. This is because S2Graph already has a 
> strong feature, which can support multiple storage engines.
> What is best key/value storage engine starting to support S2Graph?
> Can companies maintain their existing key/value storage engine and use 
> S2Graph at the same time? Yes, they can.
> Most of companies already have cache layers using Redis or Memcache. It is ok 
> for the companies to start with one of these storages to support another 
> key/value storage engine. It is because Redis is already suitable to support 
> HA and fault tolerant features. Therefore, they do not need to replace this 
> existing key/value storage engine.
> h2. Requirements
> - Support S2Graph storage engine’s interface
> -- Insert/Delete/Increment/etc.
> -- Query
> - Support serializer/deserializer to make edge/vertex data suit to key/value 
> storage’s schema ( e.g. byte array encoding/decoding )
> - Support idempotent feature (this is a similar feature to S2Graph)
> - Design saving schema for edge(IndexEdge, SnapshotEdge) / vertex
> - Support query builder for S2Graph’s getEdges syntax
> - etc.
> I would like to invite everyone to openly discuss about this. I will also 
> make a to-do list before I carry this issue in depth. Your feedback is 
> appreciated :)
> P.S.
> I couldn't fill some information about this issue, e.g. affected version, fix 
> version, component, etc. Please help me to fill out these mandatory fields. 
> In addition, this issue is umbrella issue for real subsequent tasks, so I 
> would like to make this epic issue. Can anyone help me out? I am new to 
> create apache jira issue :)



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

[jira] [Commented] (S2GRAPH-62) Reinforce tests to cover multiple schema versions.

2016-04-08 Thread Hyunsung Jo (JIRA)


[ 
https://issues.apache.org/jira/browse/S2GRAPH-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231958#comment-15231958
 ] 

Hyunsung Jo commented on S2GRAPH-62:


I've noticed that StrongLabelDelete test is not passing with v1 schema.
I assumed that this was by design and had the test skip v1.
Please let me know if this is an issue.

> Reinforce tests to cover multiple schema versions.
> --
>
> Key: S2GRAPH-62
> URL: https://issues.apache.org/jira/browse/S2GRAPH-62
> Project: S2Graph
>  Issue Type: Test
>        Reporter: Hyunsung Jo
>Priority: Minor
>
> The latest version of S2Graph has four schema versions (v1 through v4). Yet, 
> most of the current test cases only cover one or two versions (usually v2 or 
> v3). Each test case should run against all versions that support the feature 
> being tested.



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

Re: [jira] [Commented] (S2GRAPH-61) Update README.md to have Apache mailing list

2016-03-22 Thread Hyunsung Jo

Updated GitBook, too.
On 2016년 3월 23일 (수) at 오후 12:24 ASF GitHub Bot (JIRA) <j...@apache.org>
wrote:

>
> [
> https://issues.apache.org/jira/browse/S2GRAPH-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15207825#comment-15207825
> ]
>
> ASF GitHub Bot commented on S2GRAPH-61:
> ---
>
> Github user SteamShon commented on the pull request:
>
>
> https://github.com/apache/incubator-s2graph/pull/44#issuecomment-200149105
>
> :+1:
>
>
> > Update README.md to have Apache mailing list
> > 
> >
> > Key: S2GRAPH-61
> > URL: https://issues.apache.org/jira/browse/S2GRAPH-61
> >         Project: S2Graph
> >  Issue Type: Task
> >Reporter: Hyunsung Jo
> >Assignee: DOYUNG YOON
> >
> > Current README.md has a link to the outdated mailing list.
> > This should be updated to the new Apache mailing list.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>

Re: mailing list subscription

2016-03-22 Thread Hyunsung Jo

Hi Jong Wook,

Welcome to S2Graph!
I've created a JIRA regarding the outdated mailing list info:
https://issues.apache.org/jira/browse/S2GRAPH-61

Regards,
Jo


On Tue, Mar 22, 2016 at 10:02 PM Jong Wook Kim  wrote:

> Hi,
>
> I managed to add myself to this mailing list.
>
> I found no instructions anywhere saying how I can join the list, i.e.
> sending an email to {channel}-subscr...@s2graph.incubator.apache.org. I
> could subscribe only because I knew how I did for other apache projects.
>
> README.md in the official repo <
> https://github.com/apache/incubator-s2graph> has a link to google groups
> which now looks obsolete. I guess the README.md should be updated to have
> the instruction to subscribe to this list and the users list.
>
>
> Jong Wook

[jira] [Created] (S2GRAPH-61) Update README.md to have Apache mailing list

2016-03-22 Thread Hyunsung Jo (JIRA)

Hyunsung Jo created S2GRAPH-61:
--

 Summary: Update README.md to have Apache mailing list
 Key: S2GRAPH-61
 URL: https://issues.apache.org/jira/browse/S2GRAPH-61
 Project: S2Graph
  Issue Type: Task
Reporter: Hyunsung Jo


Current README.md has a link to the outdated mailing list.
This should be updated to the new Apache mailing list.



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

Re: concerned about s2graph community

2016-03-19 Thread Hyunsung Jo

I understand where the concerns are coming from and frankly have to admit
that Kakao members of the community are guilty as charged : (
I can think of a few reasons of why the project is not up to par regarding
working in the Apache Way:
  - committers having little development experience in ASF projects
  - committers sharing the same office
  - language barrier is an actual thing, too!
However, none the above reasons can be an excuse if S2Graph wants to become
a successful Apache project.
I can only speak for myself, but I'm confident that the committers are keen
believers in the Apache Way and solving this problem is a matter of more
care and practice.
Thank you for your kind advise, Sergio and Luke.

Regards,
Jo

On Fri, Mar 18, 2016 at 8:14 AM Luke Han  wrote:

> Same feeling I have too, there's few discussions for others to participant
> and exchange ideas.
>
> Our experience from Apache Kylin, the core dev team was in same office, is
> to bring such stuff to mailing list as much as possible. f2f discuss is a
> great way but at least should raise some thread to let community know the
> next step, the plan and architect/tech changes, so that everybody could
> join. Then you could see the community is more active today with many new
> contributors/committers and users.
>
> Please let me know if I could help more.
>
> Thanks.
>
>
> Best Regards!
> -
>
> Luke Han
>
> On Thu, Mar 17, 2016 at 11:36 PM, Sergio Fernández 
> wrote:
>
> > Hi,
> >
> > I've been thinking for a while about this issue... because my current
> > feeling in that the community has not really landed in ASF. Yes, you are
> > creating issues, pull requests, commiting code, etc. But there is no much
> > discussion in the mailing list. For instance, checking the mail archives
> of
> > dev@s2graph.a.o
> > http://markmail.org/search/?q=list%3Aorg.apache.s2graph.dev it's
> > clear something is happening behind the scenes. I can't find any other
> > reason how I can be the second most active person (excluding jira and
> > github bots) in this mailing list.
> >
> > So that leads me to think that you still meet face-to-face on regular
> > basis, you privately agree on the next steps and then you behave as you
> did
> > before as a company, but just on public coding infrastructure. And that's
> > not supposed to happen in the Apache Way, where decisions are taken in
> the
> > community. Actually there is a common say in Apache: "If it didn't happen
> > on a mailing list, it didn't happen".
> >
> > I may be wrong, and I hope to be wrong, but that's my current feeling.
> So,
> > my advice as mentor, and actually it's one of the points I stressed when
> > the project entered incubation, is that you have to focus to grow your
> > community outside Kakao. For instance, I miss the discussion about the
> > first release. Such kind of thing, you know.
> >
> > Cheers,
> >
> > --
> > Sergio Fernández
> > Partner Technology Manager
> > Redlink GmbH
> > m: +43 6602747925
> > e: sergio.fernan...@redlink.co
> > w: http://redlink.co
> >
>

Re: questions about Data Model

2016-02-23 Thread Hyunsung Jo

Hello Weiqing Xu,

Welcome to S2Graph!
Thank you for your interest in the project.

1.  Label can connection serviceColumns from two different services. We
store the edge as (service, label, source vertex id, target vertex id).
which service is here when label connecting different service ?
=>
You can specify preferred service name when creating the label. The default
is to use target service.
For details, please refer to
https://steamshon.gitbooks.io/s2graph-book/content/create_a_label.html


2. Since I am Scala is new for me . I am still reading  the code now. But I
am really want to know does the S2Graph store all the data of a
ServiceColumn to one HBase Table or different  data into different table.
For example Vertex data in a table and edge data into anther table.
=>
- Service columns (or vertices) are stored in the table that belongs to its
service which is given at service creation:

curl -XPOST localhost:9000/graphs/createService -H 'Content-Type:
Application/json' -d '
{"serviceName": "KakaoFavorites", "compressionAlgorithm" : "gz",
"hTableName": "KakaoFavorites-dev"}
'


- Labels are either stored in its service table or a separate table given
as a parameter "hTableName" at creation:

curl -XPOST localhost:9000/graphs/createLabel -H 'Content-Type:
Application/json' -d '
{
 "label": "friends",
 "srcServiceName": "KakaoFavorites",
 "srcColumnName": "userName",
 "srcColumnType": "string",
 "tgtServiceName": "KakaoFavorites",
 "tgtColumnName": "userName",
 "tgtColumnType": "string",
 "isDirected": "false",
 "indices": [],
 "props": [],
 "hTableName": "someTableName"
}
'

Hope this helps.

Regards,
Jo






On Tue, Feb 23, 2016 at 12:11 AM Weiqing Xu  wrote:

> Hi All,
>
> I have some question about the DataModel when I read the GitBook. Since I
> am new to S2Graph so some question maybe my misunderstandings.
>
> 1.  Label can connection serviceColumns from two different services. We
> store the edge as (service, label, source vertex id, target vertex id).
> which service is here when label connecting different service ?
>
> 2. Since I am Scala is new for me . I am still reading  the code now. But
> I am really want to know does the S2Graph store all the data of a
> ServiceColumn to one HBase Table or different  data into different table.
> For example Vertex data in a table and edge data into anther table.
>
> Best Regards,
> Weiqing Xu

Re: Guide for Newbie

2016-02-23 Thread Hyunsung Jo

Hi Chiwan,

Welcome to S2Graph!
At the moment, most of the entry level issues seem to be already assigned
or resolved.
However, this one seems like something that might interest you:
https://issues.apache.org/jira/browse/S2GRAPH-12?jql=project%20%3D%20S2GRAPH
I've added a detailed spec based on what has been discussed so far, so take
a look and see if you like it.
If you do, maybe we can ask someone to assign the ticket to you.

Regards,
Jo

On Tue, Feb 23, 2016 at 11:39 AM Chiwan Park  wrote:

> Hello everyone,
>
> I’m Chiwan Park, a graduate student in Data Mining Lab. at Seoul National
> University [1] and a committer of Apache Flink [2]. I'm interested in
> S2Graph because it is related to my research topic.
>
> I’m actively looking for starter or newbie issues to work on, but would
> appreciate some suggestions from the community. If you would like to point
> something which I can work on, please feel free to give me your feedback.
>
> Thank you all in advance, I look forward to join the community as a active
> contributor.
>
> Regards,
> Chiwan Park
>
> [1]: http://datalab.snu.ac.kr
> [2]: http://flink.apache.org

[jira] [Commented] (S2GRAPH-12) Add Label Name Swap Feature

2016-02-23 Thread Hyunsung Jo (JIRA)


[ 
https://issues.apache.org/jira/browse/S2GRAPH-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15159926#comment-15159926
 ] 

Hyunsung Jo commented on S2GRAPH-12:


*Create service*
{noformat}
curl -XPOST localhost:9000/graphs/createService -H 'Content-Type: 
Application/json' -d '
{"serviceName": "KakaoFavorites", "compressionAlgorithm" : "gz", "hTableName": 
"KakaoFavorites-dev"}
'

curl -XGET localhost:9000/graphs/getService/KakaoFavorites
{noformat}

*Create label*
{noformat}
curl -XPOST localhost:9000/graphs/createLabel -H 'Content-Type: 
Application/json' -d '
{
 "label": "friends_old",
 "srcServiceName": "KakaoFavorites",
 "srcColumnName": "userName",
 "srcColumnType": "string",
 "tgtServiceName": "KakaoFavorites",
 "tgtColumnName": "userName",
 "tgtColumnType": "string",
 "isDirected": "false",
 "indices": [],
 "props": []
}
'
{noformat}

*Insert data to label*
{noformat}
curl -XPOST localhost:9000/graphs/edges/insert -H 'Content-Type: 
Application/json' -d '
{"from":"Cookie 
Monster","to":"Oscar","label":"friends_old","props":{},"timestamp":1}
'
{noformat}

*Create new label*
{noformat}
curl -XPOST localhost:9000/graphs/createLabel -H 'Content-Type: 
Application/json' -d '
{
 "label": "friends_new",
 "srcServiceName": "KakaoFavorites",
 "srcColumnName": "userName",
 "srcColumnType": "string",
 "tgtServiceName": "KakaoFavorites",
 "tgtColumnName": "userName",
 "tgtColumnType": "string",
 "isDirected": "false",
 "indices": [],
 "props": []
}
'
{noformat}

*Insert data to new label*
{noformat}
curl -XPOST localhost:9000/graphs/edges/insert -H 'Content-Type: 
Application/json' -d '
{"from":"Cookie Monster","to":"Elmo","label":"friends","props":{},"timestamp":2}
'
{noformat}

*Swap labels (This API is what we're trying to implement!)*
{noformat}
curl -XPOST localhost:9000/admin/swapLabel/friends_old/friends_new
{noformat}

*Access the new data "Cookie Monster - Elmo" from the original label*
{noformat}
curl -XPOST localhost:9000/graphs/checkEdges -H 'Content-Type: 
Application/json' -d '
[
{"label": "friends_old", "direction": "out", "from": "Cookie Monster", 
"to": "Oscar"}
]
'
{noformat}

> Add Label Name Swap Feature
> ---
>
> Key: S2GRAPH-12
> URL: https://issues.apache.org/jira/browse/S2GRAPH-12
> Project: S2Graph
>  Issue Type: New Feature
>Reporter: Hyunsung Jo
>  Labels: feature
>
> Operating live services on S2Graph, there are a few cases where interchanging 
> two label names could come in handy.
> For example, assume that a social graph is being served under the label name 
> _A_, and an updated graph has been loaded to _A'_.
> It would be nice if one can refer to the updated data of _A'_ while still 
> making requests to the same label name _A_ so that no client-side code change 
> is required.
> Obviously, this feature should have transaction support.



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

[jira] [Commented] (S2GRAPH-1) Add Redis storage(Key/Value storage) engine for S2Graph

2016-02-09 Thread Hyunsung Jo (JIRA)


[ 
https://issues.apache.org/jira/browse/S2GRAPH-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15138812#comment-15138812
 ] 

Hyunsung Jo commented on S2GRAPH-1:
---

[~wishoping]
Done!

> Add Redis storage(Key/Value storage) engine for S2Graph
> ---
>
> Key: S2GRAPH-1
> URL: https://issues.apache.org/jira/browse/S2GRAPH-1
> Project: S2Graph
>  Issue Type: Task
>Reporter: Junki Kim
>Assignee: Junki Kim
>  Labels: features
>
> h2. Background
> The purpose of S2Graph is to support all features of edge/vertex operations  
> with HBase. It is also to orchestrate with HBase’s key features such as scale 
> out / fault tolerant / highly available / etc. However, if there is no 
> engineer to support stably in managing Hadoop cluster, it is very difficult 
> to operate and maintain HBase and Hadoop clusters. Some companies, which 
> already have another key/value storages to serve their services, may want to 
> use S2Graph and also maintain their existing key/value storage environment. 
> With S2Graph’s persistent storage, we would have a better support in 
> operating another key/value storage. This is because S2Graph already has a 
> strong feature, which can support multiple storage engines.
> What is best key/value storage engine starting to support S2Graph?
> Can companies maintain their existing key/value storage engine and use 
> S2Graph at the same time? Yes, they can.
> Most of companies already have cache layers using Redis or Memcache. It is ok 
> for the companies to start with one of these storages to support another 
> key/value storage engine. It is because Redis is already suitable to support 
> HA and fault tolerant features. Therefore, they do not need to replace this 
> existing key/value storage engine.
> h2. Requirements
> - Support S2Graph storage engine’s interface
> -- Insert/Delete/Increment/etc.
> -- Query
> - Support serializer/deserializer to make edge/vertex data suit to key/value 
> storage’s schema ( e.g. byte array encoding/decoding )
> - Support idempotent feature (this is a similar feature to S2Graph)
> - Design saving schema for edge(IndexEdge, SnapshotEdge) / vertex
> - Support query builder for S2Graph’s getEdges syntax
> - etc.
> I would like to invite everyone to openly discuss about this. I will also 
> make a to-do list before I carry this issue in depth. Your feedback is 
> appreciated :)
> P.S.
> I couldn't fill some information about this issue, e.g. affected version, fix 
> version, component, etc. Please help me to fill out these mandatory fields. 
> In addition, this issue is umbrella issue for real subsequent tasks, so I 
> would like to make this epic issue. Can anyone help me out? I am new to 
> create apache jira issue :)



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

[jira] [Comment Edited] (S2GRAPH-1) Add Redis storage(Key/Value storage) engine for S2Graph

2016-02-08 Thread Hyunsung Jo (JIRA)


[ 
https://issues.apache.org/jira/browse/S2GRAPH-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15138087#comment-15138087
 ] 

Hyunsung Jo edited comment on S2GRAPH-1 at 2/9/16 12:09 AM:


Junki,
The latest PR in the redis branch contains a working version of {{delete}}.
I'll move on to the vertex {{insert}}.


was (Author: hyunsung.jo):
@wishoping,
The latest PR in the redis branch contains a working version of {{delete}}.
I'll move on to the vertex {{insert}}.

> Add Redis storage(Key/Value storage) engine for S2Graph
> ---
>
> Key: S2GRAPH-1
> URL: https://issues.apache.org/jira/browse/S2GRAPH-1
> Project: S2Graph
>  Issue Type: Task
>Reporter: Junki Kim
>Assignee: Junki Kim
>  Labels: features
>
> h2. Background
> The purpose of S2Graph is to support all features of edge/vertex operations  
> with HBase. It is also to orchestrate with HBase’s key features such as scale 
> out / fault tolerant / highly available / etc. However, if there is no 
> engineer to support stably in managing Hadoop cluster, it is very difficult 
> to operate and maintain HBase and Hadoop clusters. Some companies, which 
> already have another key/value storages to serve their services, may want to 
> use S2Graph and also maintain their existing key/value storage environment. 
> With S2Graph’s persistent storage, we would have a better support in 
> operating another key/value storage. This is because S2Graph already has a 
> strong feature, which can support multiple storage engines.
> What is best key/value storage engine starting to support S2Graph?
> Can companies maintain their existing key/value storage engine and use 
> S2Graph at the same time? Yes, they can.
> Most of companies already have cache layers using Redis or Memcache. It is ok 
> for the companies to start with one of these storages to support another 
> key/value storage engine. It is because Redis is already suitable to support 
> HA and fault tolerant features. Therefore, they do not need to replace this 
> existing key/value storage engine.
> h2. Requirements
> - Support S2Graph storage engine’s interface
> -- Insert/Delete/Increment/etc.
> -- Query
> - Support serializer/deserializer to make edge/vertex data suit to key/value 
> storage’s schema ( e.g. byte array encoding/decoding )
> - Support idempotent feature (this is a similar feature to S2Graph)
> - Design saving schema for edge(IndexEdge, SnapshotEdge) / vertex
> - Support query builder for S2Graph’s getEdges syntax
> - etc.
> I would like to invite everyone to openly discuss about this. I will also 
> make a to-do list before I carry this issue in depth. Your feedback is 
> appreciated :)
> P.S.
> I couldn't fill some information about this issue, e.g. affected version, fix 
> version, component, etc. Please help me to fill out these mandatory fields. 
> In addition, this issue is umbrella issue for real subsequent tasks, so I 
> would like to make this epic issue. Can anyone help me out? I am new to 
> create apache jira issue :)



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

[jira] [Commented] (S2GRAPH-1) Add Redis storage(Key/Value storage) engine for S2Graph

2016-02-08 Thread Hyunsung Jo (JIRA)


[ 
https://issues.apache.org/jira/browse/S2GRAPH-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15138087#comment-15138087
 ] 

Hyunsung Jo commented on S2GRAPH-1:
---

@wishoping,
The latest PR in the redis branch contains a working version of {{delete}}.
I'll move on to the vertex {{insert}}.

> Add Redis storage(Key/Value storage) engine for S2Graph
> ---
>
> Key: S2GRAPH-1
> URL: https://issues.apache.org/jira/browse/S2GRAPH-1
> Project: S2Graph
>  Issue Type: Task
>Reporter: Junki Kim
>Assignee: Junki Kim
>  Labels: features
>
> h2. Background
> The purpose of S2Graph is to support all features of edge/vertex operations  
> with HBase. It is also to orchestrate with HBase’s key features such as scale 
> out / fault tolerant / highly available / etc. However, if there is no 
> engineer to support stably in managing Hadoop cluster, it is very difficult 
> to operate and maintain HBase and Hadoop clusters. Some companies, which 
> already have another key/value storages to serve their services, may want to 
> use S2Graph and also maintain their existing key/value storage environment. 
> With S2Graph’s persistent storage, we would have a better support in 
> operating another key/value storage. This is because S2Graph already has a 
> strong feature, which can support multiple storage engines.
> What is best key/value storage engine starting to support S2Graph?
> Can companies maintain their existing key/value storage engine and use 
> S2Graph at the same time? Yes, they can.
> Most of companies already have cache layers using Redis or Memcache. It is ok 
> for the companies to start with one of these storages to support another 
> key/value storage engine. It is because Redis is already suitable to support 
> HA and fault tolerant features. Therefore, they do not need to replace this 
> existing key/value storage engine.
> h2. Requirements
> - Support S2Graph storage engine’s interface
> -- Insert/Delete/Increment/etc.
> -- Query
> - Support serializer/deserializer to make edge/vertex data suit to key/value 
> storage’s schema ( e.g. byte array encoding/decoding )
> - Support idempotent feature (this is a similar feature to S2Graph)
> - Design saving schema for edge(IndexEdge, SnapshotEdge) / vertex
> - Support query builder for S2Graph’s getEdges syntax
> - etc.
> I would like to invite everyone to openly discuss about this. I will also 
> make a to-do list before I carry this issue in depth. Your feedback is 
> appreciated :)
> P.S.
> I couldn't fill some information about this issue, e.g. affected version, fix 
> version, component, etc. Please help me to fill out these mandatory fields. 
> In addition, this issue is umbrella issue for real subsequent tasks, so I 
> would like to make this epic issue. Can anyone help me out? I am new to 
> create apache jira issue :)



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

[jira] [Comment Edited] (S2GRAPH-1) Add Redis storage(Key/Value storage) engine for S2Graph

2016-02-08 Thread Hyunsung Jo (JIRA)


[ 
https://issues.apache.org/jira/browse/S2GRAPH-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15138087#comment-15138087
 ] 

Hyunsung Jo edited comment on S2GRAPH-1 at 2/9/16 12:09 AM:


Junki,
The latest PR in the redis branch contains a working version of {{delete}}.
I'll move on to vertex {{insert}}.


was (Author: hyunsung.jo):
Junki,
The latest PR in the redis branch contains a working version of {{delete}}.
I'll move on to the vertex {{insert}}.

> Add Redis storage(Key/Value storage) engine for S2Graph
> ---
>
> Key: S2GRAPH-1
> URL: https://issues.apache.org/jira/browse/S2GRAPH-1
> Project: S2Graph
>  Issue Type: Task
>Reporter: Junki Kim
>Assignee: Junki Kim
>  Labels: features
>
> h2. Background
> The purpose of S2Graph is to support all features of edge/vertex operations  
> with HBase. It is also to orchestrate with HBase’s key features such as scale 
> out / fault tolerant / highly available / etc. However, if there is no 
> engineer to support stably in managing Hadoop cluster, it is very difficult 
> to operate and maintain HBase and Hadoop clusters. Some companies, which 
> already have another key/value storages to serve their services, may want to 
> use S2Graph and also maintain their existing key/value storage environment. 
> With S2Graph’s persistent storage, we would have a better support in 
> operating another key/value storage. This is because S2Graph already has a 
> strong feature, which can support multiple storage engines.
> What is best key/value storage engine starting to support S2Graph?
> Can companies maintain their existing key/value storage engine and use 
> S2Graph at the same time? Yes, they can.
> Most of companies already have cache layers using Redis or Memcache. It is ok 
> for the companies to start with one of these storages to support another 
> key/value storage engine. It is because Redis is already suitable to support 
> HA and fault tolerant features. Therefore, they do not need to replace this 
> existing key/value storage engine.
> h2. Requirements
> - Support S2Graph storage engine’s interface
> -- Insert/Delete/Increment/etc.
> -- Query
> - Support serializer/deserializer to make edge/vertex data suit to key/value 
> storage’s schema ( e.g. byte array encoding/decoding )
> - Support idempotent feature (this is a similar feature to S2Graph)
> - Design saving schema for edge(IndexEdge, SnapshotEdge) / vertex
> - Support query builder for S2Graph’s getEdges syntax
> - etc.
> I would like to invite everyone to openly discuss about this. I will also 
> make a to-do list before I carry this issue in depth. Your feedback is 
> appreciated :)
> P.S.
> I couldn't fill some information about this issue, e.g. affected version, fix 
> version, component, etc. Please help me to fill out these mandatory fields. 
> In addition, this issue is umbrella issue for real subsequent tasks, so I 
> would like to make this epic issue. Can anyone help me out? I am new to 
> create apache jira issue :)



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

[jira] [Commented] (S2GRAPH-8) Update readme for project structure refactoring

2016-01-19 Thread Hyunsung Jo (JIRA)


[ 
https://issues.apache.org/jira/browse/S2GRAPH-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15106466#comment-15106466
 ] 

Hyunsung Jo commented on S2GRAPH-8:
---

[~steamshon]
Isn't this a duplicate of S2GRAPH-2?

> Update readme for project structure refactoring
> ---
>
> Key: S2GRAPH-8
> URL: https://issues.apache.org/jira/browse/S2GRAPH-8
> Project: S2Graph
>  Issue Type: Sub-task
>Reporter: DOYUNG YOON
>Assignee: Daewon Jeong
>Priority: Minor
>  Labels: document, refactoring
>   Original Estimate: 240h
>  Remaining Estimate: 240h
>
> readme should follow up project structure refactoring.
> for example, previously "sbt test" would run tests on rest server. after 
> refactoring this should be changed to specify project to run test(something 
> like "sbt 'project s2rest_xxx' test")



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

[jira] [Commented] (S2GRAPH-2) Update document and quick start environment to have recent set-up command changes

2016-01-19 Thread Hyunsung Jo (JIRA)


[ 
https://issues.apache.org/jira/browse/S2GRAPH-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15106465#comment-15106465
 ] 

Hyunsung Jo commented on S2GRAPH-2:
---

[~wishoping]

You are correct, no change required in {{schema.sql}}.
I meant that the [Getting 
Started|https://steamshon.gitbooks.io/s2graph-book/content/getting_started.html]
 document had to be updated in order to remove redundancy.
(It contained instructions on setting up MySQL user and access rights which is 
now part of the SQL script itself. Anyway, the document was updated a while 
ago, so no problems.)


> Update document and quick start environment to have recent set-up command 
> changes
> -
>
> Key: S2GRAPH-2
> URL: https://issues.apache.org/jira/browse/S2GRAPH-2
> Project: S2Graph
>  Issue Type: Task
>        Reporter: Hyunsung Jo
>Priority: Minor
>  Labels: documentation
>
> Due to refactoring, the start-up command for S2Graph has changed.
> bq. sbt run => activator 'project s2rest_play' run
> Apply this to documentation.
> Also, {{schema.sql}} now includes user and access rights.
> This part should be removed from the manual. 



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

Re: [jira] [Updated] (S2GRAPH-23) Abstract HBase specific options from Label meta table columns

2016-01-11 Thread Hyunsung Jo

this is a test.

On Mon, Jan 11, 2016 at 6:08 PM DOYUNG YOON (JIRA)  wrote:

>
>  [
> https://issues.apache.org/jira/browse/S2GRAPH-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> DOYUNG YOON updated S2GRAPH-23:
> ---
> Description:
> Currently Label(meta) has hbase_table_name, hbase_ttl,
> compression_algorithm configuration value as column in Label table.
> I think it is inevitable to store these configuration value, but current
> implementation is too hbase specific. for example, redis storage might not
> use hbase_table_name on label. I think it is better to store json
> dictionary containing configuration values as column on Label.
>
> Little bit of background of this issue is following.
> I was up to implement secure cluster support and realize it is hard to add
> extra configuration for HBase. I think Redis storage(S2GRAPH-1) has similar
> issues that it needs to store redis specific configuration per label.
>
>   was:
> Currently Label(meta) has hbase_table_name, hbase_ttl,
> compression_algorithm configuration value as column in Label table.
> I think it is inevitable to store these configuration value, but current
> implementation is too hbase specific. for example, redis storage might not
> use hbase_table_name on label. I think it is better to store json
> dictionary containing configuration values as column on Label.
>
>
>
> > Abstract HBase specific options from Label meta table columns
> > -
> >
> > Key: S2GRAPH-23
> > URL: https://issues.apache.org/jira/browse/S2GRAPH-23
> > Project: S2Graph
> >  Issue Type: Improvement
> >Reporter: DOYUNG YOON
> >Priority: Minor
> >  Labels: Configuration, refactoring
> >   Original Estimate: 168h
> >  Remaining Estimate: 168h
> >
> > Currently Label(meta) has hbase_table_name, hbase_ttl,
> compression_algorithm configuration value as column in Label table.
> > I think it is inevitable to store these configuration value, but current
> implementation is too hbase specific. for example, redis storage might not
> use hbase_table_name on label. I think it is better to store json
> dictionary containing configuration values as column on Label.
> > Little bit of background of this issue is following.
> > I was up to implement secure cluster support and realize it is hard to
> add extra configuration for HBase. I think Redis storage(S2GRAPH-1) has
> similar issues that it needs to store redis specific configuration per
> label.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>

41 matches

Mail list logo