[jira] [Created] (KUDU-1594) Rename TIMESTAMP type to avoid confusion with other timestamp types

["Todd Lipcon (JIRA)" <ji...@apache.org>]

Todd Lipcon created KUDU-1594:
---------------------------------

             Summary: Rename TIMESTAMP type to avoid confusion with other timestamp types
                 Key: KUDU-1594
                 URL: https://issues.apache.org/jira/browse/KUDU-1594
             Project: Kudu
          Issue Type: Improvement
            Reporter: Todd Lipcon
            Assignee: Todd Lipcon
            Priority: Critical


Kudu aims to be part of the Hadoop ecosystem, and other tools in the Hadoop ecosystem store timestamps differently than Kudu. For example:
- Parquet has TIMESTAMP_MILLIS which is milliseconds since the Unix epoch.
- Impala internally stores a {64-bit nanoseconds since midnight, 32-bit Julian day number}, and when storing in Parquet, uses Parquet's INT96 type to store this.
- Hive internally uses a 32-bit seconds-since-Unix-epoch, plus an optional nanoseconds component

To avoid adding to the confusion, we should name our time more explicitly (eg UNIX_MICROTIMESTAMP or UNIXTIME_MICROS or somesuch)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)