Github user cloud-fan commented on the issue:

    https://github.com/apache/spark/pull/23043
  
    Before rushing to a fix that replaces -0.0 to 0.0, I'd like to know how 
this bug happens.
    
    One possible reason might be, 0.0 and -0.0 have different binary format. 
Spark use unsafe API to write float/double, maybe we can investigate that first.


---

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

Reply via email to