Hi Stamatis, Thanks for your reply and +1. Anyway, I also guess there is no semantic reason not to support the type. I created a ticket and may try to work on it when I have a chance. https://issues.apache.org/jira/browse/HIVE-27587
Please let me know if anyone else knows any difficulties or historical reasons why we are not supporting it. Regards, Okumin On Wed, Aug 9, 2023 at 5:50 PM Stamatis Zampetakis <zabe...@gmail.com> wrote: > Hello Okumin, > > As you mentioned the TIME datatype is part of the SQL standard and it > is also supported by many popular DBMS so it definitely makes sense to > add it to Hive. > I guess it was not implemented already cause users were able to store > times using other existing types so it never became a must have. > > +1 on adding TIME data type support in Hive. > > Best, > Stamatis > > On Fri, Aug 4, 2023 at 12:19 PM Okumin <m...@okumin.com> wrote: > > > > Hi everyone, > > > > I happened to find some people struggling to store values of the TIME > type > > in a Hive table from another query engine. A viable option is to use > > Iceberg or another format instead of Hive native tables since Hive > doesn't > > directly support the type. I agree that it could be one of the right > > options in this era. > > > > On the other hand, I also think it is a valid request to support TIME > since > > it is one of the types defined in the SQL standard. I expect it is not a > > bad offer also for Hive users if they can process Iceberg's TIME as > Hive's > > TIME, not STRING or other alternatives. I'd like to hear if we have any > > reasons not to support it easily. > > > > I see there is a related ticket but looks like we have not developed TIME > > yet. > > https://issues.apache.org/jira/browse/HIVE-1269 > > > > Regards, > > Okumin >
