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

ASF GitHub Bot commented on S2GRAPH-12:
---------------------------------------

GitHub user HyunsungJo opened a pull request:

    https://github.com/apache/incubator-s2graph/pull/79

    [S2GRAPH-12] Add Label Name Swap Feature

    - add route and functions for label name swap
    - updateLabelName to support transactions
    - add test cases
    - minor error message changes

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/HyunsungJo/incubator-s2graph S2GRAPH-12

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-s2graph/pull/79.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 #79
    
----
commit 76348704f898fe13e624452ac590738e8868091d
Author: jojo <jojo.m...@daumkakao.com>
Date:   2016-09-12T09:24:05Z

    [S2GRAPH-12] Add Label Name Swap Feature
    
    - add route and functions for label name swap
    - add test cases
    - minor error message changes

----


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

Reply via email to