cloud-fan commented on a change in pull request #33955: URL: https://github.com/apache/spark/pull/33955#discussion_r706177022
########## File path: sql/catalyst/src/main/scala/org/apache/spark/sql/util/SQLOpenHashSet.scala ########## @@ -0,0 +1,66 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under one or more + * contributor license agreements. See the NOTICE file distributed with + * this work for additional information regarding copyright ownership. + * The ASF licenses this file to You under the Apache License, Version 2.0 + * (the "License"); you may not use this file except in compliance with + * the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ + +package org.apache.spark.sql.util + +import scala.reflect._ + +import org.apache.spark.annotation.Private +import org.apache.spark.util.collection.OpenHashSet + +/** + * A wrap of [[OpenHashSet]] that can handle null, Double.NaN and Float.NaN. + */ +@Private +class SQLOpenHashSet[@specialized(Long, Int, Double, Float) T: ClassTag]( + initialCapacity: Int, + loadFactor: Double) { + + def this(initialCapacity: Int) = this(initialCapacity, 0.7) + + def this() = this(64) + + private val hashSet = new OpenHashSet[T](initialCapacity, loadFactor) + + private var containsNull = false + private var containsDoubleNaN = false + private var containsFloatNaN = false Review comment: Maybe we should do the null/nan check at the caller side ``` class SQLOpenHashSet ... { def add(k: T) def addNull() def addNaN() } // caller side if (row.isNullAt...) { set.addNull() } else { ... if (java.lang.Double.isNaN(value)) { set.addNaN() } } ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
