Mailing-List: contact reviews-help@spark.apache.org; run by ezmlm
Precedence: bulk
From: HyukjinKwon <git@git.apache.org>
To: reviews@spark.apache.org
Reply-To: reviews@spark.apache.org
References: <git-pr-15432-spark@git.apache.org>
In-Reply-To: <git-pr-15432-spark@git.apache.org>
Subject: [GitHub] spark issue #15432: [SPARK-17854][SQL] rand/randn allows null/long as input ...
Content-Type: text/plain
Message-Id: <20161013041023.9C4BFE0381@git1-us-west.apache.org>
Date: Thu, 13 Oct 2016 04:10:23 +0000 (UTC)
archived-at: Thu, 13 Oct 2016 04:10:27 -0000

Github user HyukjinKwon commented on the issue:

    https://github.com/apache/spark/pull/15432
  
    Strictly, the JIRA describes handling `null` and we might not have to generalize the cases further.
    
    > it will failed when do select rand(null)
    
    Also, I would like to add the edge cases here but I'd like to avoid PR is being hold. 
    
    As not all the things have a standard to follow, we can define the behaviour here. I don't have access to Oracle and DB2. Do you think Hive, PostgreSQL and MySQL examples are not enough?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org