spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Apache Spark (JIRA)" <>
Subject [jira] [Assigned] (SPARK-21781) Modify DataSourceScanExec to use concrete ColumnVector type.
Date Tue, 29 Aug 2017 08:21:01 GMT


Apache Spark reassigned SPARK-21781:

    Assignee: Apache Spark

> Modify DataSourceScanExec to use concrete ColumnVector type.
> ------------------------------------------------------------
>                 Key: SPARK-21781
>                 URL:
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 2.3.0
>            Reporter: Takuya Ueshin
>            Assignee: Apache Spark
> As mentioned at, when
we have more {{ColumnVector}} implementations, it might (or might not) have huge performance
implications because it might disable inlining, or force virtual dispatches.
> As for read path, one of the major paths is the one generated by {{ColumnBatchScan}}.
Currently it refers {{ColumnVector}} so the penalty will be bigger as we have more classes,
but we can know the concrete type from its usage, e.g. vectorized Parquet reader uses {{OnHeapColumnVector}}.
We can use the concrete type in the generated code directly to avoid the penalty.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message