[
https://issues.apache.org/jira/browse/CARBONDATA-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15556630#comment-15556630 ]
ASF GitHub Bot commented on CARBONDATA-284:
-------------------------------------------
Github user JihongMA commented on a diff in the pull request:
https://github.com/apache/incubator-carbondata/pull/208#discussion_r82487219
--- Diff: hadoop/src/main/java/org/apache/carbondata/hadoop/api/CarbonInputFormatBase.java ---
@@ -0,0 +1,69 @@
+/*
--- End diff --
should we consolidate the interface as following,
CarbonInputFormatBase
--> CarbonInputFormat
--> CarbonColumnarInputFormat
--> CarbonRowInputFormat
or even further merging CarbonInputFormat into CarbonInputFormatBase
> 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.2.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)
Locked
