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/08/10 18:07:46 UTC

[jira] [Resolved] (SPARK-9743) Scanning a HadoopFsRelation shouldn't requrire refreshing

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

Yin Huai resolved SPARK-9743.
-----------------------------
       Resolution: Fixed
    Fix Version/s: 1.5.0

Issue resolved by pull request 8035
[https://github.com/apache/spark/pull/8035]

> Scanning a HadoopFsRelation shouldn't requrire refreshing
> ---------------------------------------------------------
>
>                 Key: SPARK-9743
>                 URL: https://issues.apache.org/jira/browse/SPARK-9743
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 1.5.0
>            Reporter: Cheng Lian
>            Assignee: Cheng Lian
>            Priority: Blocker
>             Fix For: 1.5.0
>
>
> PR #7969 added {{HadoopFsRelation.refresh()}} calls in {{DataSourceStrategy}} to make test case {{InsertSuite.save directly to the path of a JSON table}} pass. However, this forces every {{HadoopFsRelation}} table scan to do a refreshing, which can be super expensive for tables with large number of partitions.



--
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