You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (Jira)" <ji...@apache.org> on 2020/11/11 03:29:00 UTC
[jira] [Commented] (SPARK-33417) Correct the behaviour of query
filters in TPCDSQueryBenchmark
[ https://issues.apache.org/jira/browse/SPARK-33417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17229685#comment-17229685 ]
Apache Spark commented on SPARK-33417:
--------------------------------------
User 'maropu' has created a pull request for this issue:
https://github.com/apache/spark/pull/30324
> Correct the behaviour of query filters in TPCDSQueryBenchmark
> --------------------------------------------------------------
>
> Key: SPARK-33417
> URL: https://issues.apache.org/jira/browse/SPARK-33417
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 2.4.8, 3.0.2, 3.1.0
> Reporter: Takeshi Yamamuro
> Priority: Minor
>
> This PR intends to fix the behaviour of query filters in TPCDSQueryBenchmark. We can use an option --query-filter for selecting TPCDS queries to run, e.g., --query-filter q6,q8,q13. But, the current master has a weird behaviour about the option. For example, if we pass --query-filter q6 so as to run the TPCDS q6 only, TPCDSQueryBenchmark runs q6 and q6-v2.7 because the filterQueries method does not respect the name suffix. So, there is no way now to run the TPCDS q6 only.
--
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