spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Lee (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SPARK-17571) AssertOnQuery.condition should be consistent in requiring Boolean return type
Date Sat, 17 Sep 2016 07:36:20 GMT

     [ 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


Mime
View raw message