You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Dongjoon Hyun (Jira)" <ji...@apache.org> on 2020/01/12 21:20:00 UTC

[jira] [Resolved] (SPARK-30409) Use `NoOp` datasource in SQL benchmarks

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

Dongjoon Hyun resolved SPARK-30409.
-----------------------------------
    Fix Version/s: 3.0.0
       Resolution: Fixed

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

> Use `NoOp` datasource in SQL benchmarks
> ---------------------------------------
>
>                 Key: SPARK-30409
>                 URL: https://issues.apache.org/jira/browse/SPARK-30409
>             Project: Spark
>          Issue Type: Test
>          Components: SQL
>    Affects Versions: 2.4.4
>            Reporter: Maxim Gekk
>            Assignee: Maxim Gekk
>            Priority: Major
>             Fix For: 3.0.0
>
>
> Currently, SQL benchmarks use `count()`, `collect()` and `foreach(_ => ())` actions. The actions have additional overhead. For example, `collect()` converts column values to external type values and pull data on the driver. Need to unify benchmark and the `NoOp` datasource except the benchmarks for `count()` or `collect()`



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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