[jira] [Commented] (CARBONDATA-284) Abstracting Index and Segment interface

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (CARBONDATA-284) Abstracting Index and Segment interface

Akash R Nilugal (Jira)

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

ASF GitHub Bot commented on CARBONDATA-284:
-------------------------------------------

GitHub user ravipesala opened a pull request:

    https://github.com/apache/incubator-carbondata/pull/297

    [CARBONDATA-284]Fixed compilation and checkstyle issues of PR 208

   

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

    $ git pull https://github.com/ravipesala/incubator-carbondata pr-208-error-branch

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

    https://github.com/apache/incubator-carbondata/pull/297.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 #297
   
----
commit 988ccd8ea5084ddf1d837a3f257dd0b388ecad1a
Author: ravipesala <[hidden email]>
Date:   2016-11-04T19:56:26Z

    Fixed compilation and checkstyle issues of PR 208

----


> Abstracting Index and Segment interface
> ---------------------------------------
>
>                 Key: CARBONDATA-284
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-284
>             Project: CarbonData
>          Issue Type: Improvement
>          Components: hadoop-integration
>    Affects Versions: 0.1.0-incubating
>            Reporter: Jacky Li
>             Fix For: 0.3.0-incubating
>
>
> This issue is intended to abstract developer API and user API to achieve following goals:
> Goal 1: User can choose the place to store Index data, it can be stored in
> processing framework's memory space (like in spark driver memory) or in
> another service outside of the processing framework (like using a
> independent database service, which can be shared across client)
> Goal 2: Developer can add more index of his choice to CarbonData files.
> Besides B+ tree on multi-dimensional key which current CarbonData supports,
> developers are free to add other indexing technology to make certain
> workload faster. These new indices should be added in a pluggable way.
> This Jira has been discussed in maillist:
> http://apache-carbondata-mailing-list-archive.1130556.n5.nabble.com/Abstracting-CarbonData-s-Index-Interface-td1587.html



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