[
https://issues.apache.org/jira/browse/SPARK-23596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16509137#comment-16509137
]
Liang-Chi Hsieh edited comment on SPARK-23596 at 6/12/18 3:55 AM:
------------------------------------------------------------------
One concern I have right now is that by testing the interpreted code paths too,
we will double current test time or more. Otherwise, we can only choose to test
the interpreted code paths for just few test suites such as DatasetSuite,
DataFrameSuite...
[~hvanhovell] What do you think?
was (Author: viirya):
One concern I have right now is that by testing the interpreted code paths too,
we will double current test time or more. Otherwise, we can only choose to test
the interpreted code paths for just few test suites such as DatasetSuite,
DataFrameSuite...
[~hvanhovell] What do you think?
> Modify Dataset test harness to include interpreted execution
> ------------------------------------------------------------
>
> Key: SPARK-23596
> URL: https://issues.apache.org/jira/browse/SPARK-23596
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 2.3.0
> Reporter: Herman van Hovell
> Priority: Major
>
> We should modify the Dataset test harness to also test the interpreted code
> paths. This task can be started as soon as a significant subset of the object
> related Expressions provides an interpreted fallback.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
