Github user cloud-fan commented on a diff in the pull request:

    https://github.com/apache/spark/pull/20750#discussion_r174586279
  
    --- Diff: 
sql/catalyst/src/main/java/org/apache/spark/sql/catalyst/expressions/codegen/UnsafeWriter.java
 ---
    @@ -0,0 +1,43 @@
    +/*
    + * 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.catalyst.expressions.codegen;
    +
    +import org.apache.spark.sql.types.Decimal;
    +import org.apache.spark.unsafe.types.CalendarInterval;
    +import org.apache.spark.unsafe.types.UTF8String;
    +
    +/**
    + * Base class for writing Unsafe* structures.
    + */
    +public abstract class UnsafeWriter {
    +  public abstract void setNullByte(int ordinal);
    --- End diff --
    
    This looks pretty weird. At the first glance I'm wondering why we don't 
have `setBoolean/Float/Double`, then I realized we don't need to, because we 
just need a way to set null for 1/2/4/8 bytes.
    
    maybe it's better to name them `setNull1/2/4/8Bytes`, and ask the 
`UnsafeArrayWriter` to follow


---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to