[
https://issues.apache.org/jira/browse/S2GRAPH-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15061455#comment-15061455
]
Junki Kim edited comment on S2GRAPH-1 at 1/23/16 1:27 AM:
----------------------------------------------------------
Thank you for your interest!
I totally agree with your suggestion seperating phase, e.g. start from single
instance or fixed size cluster.
I think we should discuss about sub tasks in detail with creating discussion or
investigation ticket.
Could you create issue as your survey suggestion for project? And then we can
continue to work on ideas and specific action items! Or I can create one if you
are busy. :)
was (Author: wishoping):
Thank you for your interest!
I totally agree with your suggestion seperating phase, e.g. start from single
instance or fixed size cluster.
I think we should discuss about sub tasks in detail with creating discussion or
investigation ticket.
Can you create issue as your survey suggestion for project? And then we can
continue creating another ideas and specific action items! Or if you don't
mind, I will create one. :)
> 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)
