drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bitblender <...@git.apache.org>
Subject [GitHub] drill pull request #697: DRILL-5097: Using store.parquet.reader.int96_as_tim...
Date Mon, 02 Jan 2017 23:47:21 GMT
Github user bitblender commented on a diff in the pull request:

    --- Diff: exec/java-exec/src/main/java/org/apache/drill/exec/store/parquet/columnreaders/NullableFixedByteAlignedReaders.java
    @@ -132,6 +137,9 @@ protected void readField(long recordsToReadInThisPass) {
               valueVec.getMutator().setSafe(valuesReadInCurrentPass + i, getDateTimeValueFromBinary(binaryTimeStampValue));
    +      // The nanos precision is cut to millis. Therefore the length of single timestamp
value is 8 bytes(s)
    +      // instead of 12 byte(s).
    +      dataTypeLengthInBits = timestampLengthInBits;
    --- End diff --
    Just trying to understand this better: Is it OK to set the length to 64 bits even if PARQUET_READER_INT96_AS_TIMESTAMP
is set to false?

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 infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message