[SPARK-19573] Make NaN/null handling consistent in approxQuantile

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.0
• Fix Version/s: 2.2.0
• Component/s: SQL
• Target Version/s: 2.2.0
• Assignee: Ruifeng Zheng
• Reporter: Ruifeng Zheng
• Created: 13/Feb/17 06:22
• Updated: 27/Jul/17 18:23
• Resolved: 21/Mar/17 01:27

Description

As discussed in https://github.com/apache/spark/pull/16776, this jira is used to track the following issue:
Multi-column version of approxQuantile drop the rows containing any NaN/null, the results are not consistent with outputs of the single-version.

Issue Links

• duplicates: SPARK-21550 approxQuantiles throws "next on empty iterator" on empty data
• is duplicated by: SPARK-19339 StatFunctions.multipleApproxQuantiles can give NoSuchElementException: next on empty iterator
• is required by: SPARK-19339 StatFunctions.multipleApproxQuantiles can give NoSuchElementException: next on empty iterator
• links to: [Github] Pull Request #16971 (zhengruifeng)