You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Yin Huai (JIRA)" <ji...@apache.org> on 2015/04/15 02:08:58 UTC

[jira] [Resolved] (SPARK-2597) Improve the code related to Table Scan

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

Yin Huai resolved SPARK-2597.
-----------------------------
    Resolution: Unresolved

Seems this one is outdated. I am resolving it for now.

> Improve the code related to Table Scan
> --------------------------------------
>
>                 Key: SPARK-2597
>                 URL: https://issues.apache.org/jira/browse/SPARK-2597
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Yin Huai
>            Assignee: Yin Huai
>
> There are a several issues with the current code related to Table Scan.
> 1. HadoopTableReader and HiveTableScan are used together to deal with Hive tables. It is not clear why we do the Hive-specific work in two different places.
> 2. HadoopTableReader creates a RDD for every Hive partition and then Union these RDDs. Is it the right way to handle partitioned tables? 
> 3. Right now, we ship initializeLocalJobConfFunc to every task to set some local properties. Can we avoid it?
> I think it will be good to improve the code related to Table Scan. Also, it is important to make sure we do not introduce performance issues with the proposed changes.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org