impala-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthew Jacobs (Code Review)" <>
Subject [Impala-ASF-CR] IMPALA-5338: Fix Kudu timestamp column default values
Date Wed, 24 May 2017 22:59:29 GMT
Matthew Jacobs has posted comments on this change.

Change subject: IMPALA-5338: Fix Kudu timestamp column default values

Patch Set 1:

(1 comment)

Responding to Marcel's higher level comment first, I'll address the code comments assuming
we don't change approaches.
Commit Message:

Line 19: will be a BIGINT if the column type is TIMESTAMP. It is only
> what if you stored the default as a timestamp literal instead (and then con
The problem is that then the catalog would need to do the conversion from TimestampValue to
unixtime micros. That would get hairy because the conversion function exists as a UDF, and
it'd be really weird for the catalog to start calling UDFs. It could be exposed explicitly
over JNI but that's also not ideal.

This approach does involve some special casing, but I think at least we can be clear about
when the conversion happens and what is stored on the KuduColumn class.

To view, visit
To unsubscribe, visit

Gerrit-MessageType: comment
Gerrit-Change-Id: I655910fb4805bb204a999627fa9f68e43ea8aaf2
Gerrit-PatchSet: 1
Gerrit-Project: Impala-ASF
Gerrit-Branch: master
Gerrit-Owner: Matthew Jacobs <>
Gerrit-Reviewer: Alex Behm <>
Gerrit-Reviewer: Dimitris Tsirogiannis <>
Gerrit-Reviewer: Marcel Kornacker <>
Gerrit-Reviewer: Matthew Jacobs <>
Gerrit-Reviewer: Thomas Tauber-Marshall <>
Gerrit-HasComments: Yes

View raw message