You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@carbondata.apache.org by "Ravindra Pesala (JIRA)" <ji...@apache.org> on 2017/04/05 10:40:41 UTC

[jira] [Updated] (CARBONDATA-307) Support executor side scan using CarbonInputFormat

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

Ravindra Pesala updated CARBONDATA-307:
---------------------------------------
    Fix Version/s:     (was: 1.1.0-incubating)

> Support executor side scan using CarbonInputFormat
> --------------------------------------------------
>
>                 Key: CARBONDATA-307
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-307
>             Project: CarbonData
>          Issue Type: Improvement
>          Components: spark-integration
>    Affects Versions: 0.1.0-incubating
>            Reporter: Jacky Li
>
> Currently, there are two read path in carbon-spark module: 
> 1. CarbonContext => CarbonDatasourceRelation => CarbonScanRDD => QueryExecutor
> In this case, CarbonScanRDD uses CarbonInputFormat to get the split, and use QueryExecutor for scan.
> 2. SqlContext => CarbonDatasourceHadoopRelation => CarbonHadoopFSRDD => CarbonInputFormat(CarbonRecordReader) => QueryExecutor
> In this case, CarbonHadoopFSRDD uses CarbonInputFormat to do both get split and scan
> Because of this, there are unnecessary duplicate code, they need to be unified.
> The target approach should be:
> sqlContext/carbonContext => CarbonDatasourceHadoopRelation => CarbonScanRDD =>  CarbonInputFormat(CarbonRecordReader) => QueryExecutor



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)