You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Peter Lee (JIRA)" <ji...@apache.org> on 2016/09/17 07:36:20 UTC
[jira] [Updated] (SPARK-17571) AssertOnQuery.condition should be
consistent in requiring Boolean return type
[ https://issues.apache.org/jira/browse/SPARK-17571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Lee updated SPARK-17571:
------------------------------
Description: AssertOnQuery has two apply constructor: one that accepts a closure that returns boolean, and another that accepts a closure that returns Unit. This is actually very confusing because developers could mistakenly think that AssertOnQuery always require a boolean return type and verifies the return result, when indeed the value of the last statement is ignored in one of the constructors.
> AssertOnQuery.condition should be consistent in requiring Boolean return type
> -----------------------------------------------------------------------------
>
> Key: SPARK-17571
> URL: https://issues.apache.org/jira/browse/SPARK-17571
> Project: Spark
> Issue Type: Bug
> Components: SQL, Streaming
> Reporter: Peter Lee
>
> AssertOnQuery has two apply constructor: one that accepts a closure that returns boolean, and another that accepts a closure that returns Unit. This is actually very confusing because developers could mistakenly think that AssertOnQuery always require a boolean return type and verifies the return result, when indeed the value of the last statement is ignored in one of the constructors.
--
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