testing On Sat, Jan 9, 2016 at 11:06 AM Junki Kim (JIRA) < dev@s2graph.incubator.apache.org> wrote:
> > [ > https://issues.apache.org/jira/browse/S2GRAPH-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Junki Kim updated S2GRAPH-1: > ---------------------------- > Description: > 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 ( like byte array encoding/decoding ) > - Support idempotent feature like already supported by S2Graph's > - Design saving schema for edge(IndexEdge, SnapshotEdge) / vertex > - Support query builder for S2Graph’s getEdges syntax > - etc. > > > I want to discuss about this and make sure TODO list as task issues to > complete this. Any feedback is OK and welcome :) > > P.S. > I couldn't fill some information for this issue, like afftected version, > fix version, component, etc. Please help me fill out these mandatory fields. > And this issue is umbrella issue for real subsequent tasks, so I want to > make this epic issue. Can anyone help me out for this? I'm newbie for > creating apache jira issue :) > > was: > h2. Background > > Currently, S2Graph concentrates on to support full features ( edge > operation / vertex operation ) with HBase. And it also orchestrates with > HBase’s great feature like scale out / fault tolerant / highly availability > / etc. . However it is very hard to operate and maintain HBase cluster and > Hadoop cluster too, if there is no engineer to stably support to manage > clusters. Some companies have another key/value storages to serve their > services may want to use their existed key/value storage environments. Then > we’d better support another key/value storage as a S2Graph’s persistence > storage, because S2Graph already has great feature can support multiple > storage engines. > > First of all, I think most of companies have cache layers using Redis or > Memcache. So We’d better start with one of those storages to support > another key/value storage engine, and Redis is suitable for this because > Redis supports HA and fault tolerant features and many companies already > use Redis as a cache or key/value storage. > > 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 ( like byte array encoding/decoding ) > - Support idempotent feature like already supported by S2Graph's > - Design saving schema for edge(IndexEdge, SnapshotEdge) / vertex > - Support query builder for S2Graph’s getEdges syntax > - etc. > > > I want to discuss about this and make sure TODO list as task issues to > complete this. Any feedback is OK and welcome :) > > P.S. > I couldn't fill some information for this issue, like afftected version, > fix version, component, etc. Please help me fill out these mandatory fields. > And this issue is umbrella issue for real subsequent tasks, so I want to > make this epic issue. Can anyone help me out for this? I'm newbie for > creating apache jira issue :) > > > > 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 > > 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 ( like byte array encoding/decoding ) > > - Support idempotent feature like already supported by S2Graph's > > - Design saving schema for edge(IndexEdge, SnapshotEdge) / vertex > > - Support query builder for S2Graph’s getEdges syntax > > - etc. > > I want to discuss about this and make sure TODO list as task issues to > complete this. Any feedback is OK and welcome :) > > P.S. > > I couldn't fill some information for this issue, like afftected version, > fix version, component, etc. Please help me fill out these mandatory fields. > > And this issue is umbrella issue for real subsequent tasks, so I want to > make this epic issue. Can anyone help me out for this? I'm newbie for > creating apache jira issue :) > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) >