Github user mn-mikke commented on a diff in the pull request:

    https://github.com/apache/spark/pull/22110#discussion_r210493260
  
    --- Diff: 
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/util/TypeUtils.scala 
---
    @@ -73,4 +73,14 @@ object TypeUtils {
         }
         x.length - y.length
       }
    +
    +  /**
    +   * Returns true if elements of the data type could be used as items of a 
hash set or as keys
    +   * of a hash map.
    +   */
    +  def typeCanBeHashed(dataType: DataType): Boolean = dataType match {
    --- End diff --
    
    I will change it :)
    
    Just one question to ```hashCode```. If ```case classes``` are used, 
```equals``` and ```hashCode``` are generated by compiler. But if we define 
```equals``` manually, shouldn't also hold ```a.equals(b) == true``` => 
```a.hashCode == b.hashCode```?


---

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

Reply via email to