Github user cloud-fan commented on a diff in the pull request:
    --- Diff: 
    @@ -25,55 +25,58 @@
     import org.apache.spark.sql.types.*;
     import org.apache.spark.unsafe.Platform;
     import org.apache.spark.unsafe.array.ByteArrayMethods;
    +import org.apache.spark.unsafe.bitset.BitSetMethods;
     import org.apache.spark.unsafe.hash.Murmur3_x86_32;
     import org.apache.spark.unsafe.types.CalendarInterval;
     import org.apache.spark.unsafe.types.UTF8String;
      * An Unsafe implementation of Array which is backed by raw memory instead 
of Java objects.
    - * Each tuple has three parts: [numElements] [offsets] [values]
    + * Each array has four parts:
    + *   [numElements][null bits][values or offset&length][variable length 
    - * The `numElements` is 4 bytes storing the number of elements of this 
    + * The `numElements` is 8 bytes storing the number of elements of this 
    - * In the `offsets` region, we store 4 bytes per element, represents the 
relative offset (w.r.t. the
    - * base address of the array) of this element in `values` region. We can 
get the length of this
    - * element by subtracting next offset.
    - * Note that offset can by negative which means this element is null.
    + * In the `null bits` region, we store 1 bit per element, represents 
whether a element has null
    + * Its total size is ceil(numElements / 8) bytes, and  it is aligned to 
8-byte boundaries.
    - * In the `values` region, we store the content of elements. As we can get 
length info, so elements
    - * can be variable-length.
    + * In the `values or offset&length` region, we store the content of 
elements. For fields that hold
    + * fixed-length primitive types, such as long, double, or int, we store 
the value directly
    --- End diff --
    we should also mention that fixed-length values portion is also word-aligned

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to