Login  Register

[jira] [Updated] (CARBONDATA-312) Unify two datasource: CarbonDatasourceHadoopRelation and CarbonDatasourceRelation

Posted by Akash R Nilugal (Jira) on Oct 13, 2016; 4:16am
URL: http://apache-carbondata-dev-mailing-list-archive.168.s1.nabble.com/jira-Updated-CARBONDATA-312-Unify-two-datasource-CarbonDatasourceHadoopRelation-and-CarbonDatasourcen-tp1854.html


     [ https://issues.apache.org/jira/browse/CARBONDATA-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jacky Li updated CARBONDATA-312:
--------------------------------
    Description:
Take CarbonDatasourceHadoopRelation as the target datasource definition, after that, CarbonContext can use standard Datasource strategy

In this Issue, change CarbonDatasourceHadoopRelation to use CarbonScanRDD in buildScan function.

  was:
Take CarbonDatasourceHadoopRelation as the target datasource definition, after that, CarbonContext can use standard Datasource strategy

In this Issue, following change is required:
1. Move the dictionary stratey out of CarbonTableScan, make a separate strategy for it.
2. CarbonDatasourceHadoopRelation should use CarbonScanRDD in buildScan function.
3. Change CarbonSource to use CarbonDatasourceHadoopRelation only, remove extension of BaseRelation, extend from HadoopFsRelation only.


> Unify two datasource: CarbonDatasourceHadoopRelation and CarbonDatasourceRelation
> ---------------------------------------------------------------------------------
>
>                 Key: CARBONDATA-312
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-312
>             Project: CarbonData
>          Issue Type: Sub-task
>          Components: spark-integration
>            Reporter: Jacky Li
>             Fix For: 0.2.0-incubating
>
>
> Take CarbonDatasourceHadoopRelation as the target datasource definition, after that, CarbonContext can use standard Datasource strategy
> In this Issue, change CarbonDatasourceHadoopRelation to use CarbonScanRDD in buildScan function.



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