Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Received-SPF: pass (nike.apache.org: domain of apivovarov@gmail.com designates
 209.85.217.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAKKt98Qev82f4fT+DhgoPctWkz0k45-AQ1otYa2Yaj1=JPy7iQ@mail.gmail.com>
References: 
 <CAKKt98Qev82f4fT+DhgoPctWkz0k45-AQ1otYa2Yaj1=JPy7iQ@mail.gmail.com>
From: Alexander Pivovarov <apivovarov@gmail.com>
Date: Tue, 31 Mar 2015 23:27:51 -0700
Message-ID: 
 <CAKKt98QWshysBKrzNxDULFZrOidKcGgcMLXgmS9a5umXk98Sqw@mail.gmail.com>
Subject: Re: TIMESTAMP to DATE conversion for negative unix time
To: "dev@hive.apache.org" <dev@hive.apache.org>
Content-Type: multipart/alternative; boundary=001a11340b14c546550512a3d19f

--001a11340b14c546550512a3d19f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

correction for the first example
select cast(cast('1966-01-01 00:00:01' as timestamp) as date);
1966-01-02


On Tue, Mar 31, 2015 at 11:26 PM, Alexander Pivovarov <apivovarov@gmail.com=
>
wrote:

> Hi Everyone
>
> I noticed interesting behaviour for timestamp to date hive type conversio=
n
> for negative unix time.
>
> For example:
>
> select cast(cast('1966-01-01 00:00:01' as timestamp) as date);
> 1966-02-02
>
> Should it work this way?
>
> Another example
> select last_day(cast('1966-01-31 00:00:01' as timestamp));
> OK
> 1966-02-28
>
>
> more details:
> Date: 1966-01-01 00:00:01
> unix time UTC: -126230399
>
> daysSinceEpoch=3D=E2=88=92126230399000 / 86400000 =3D -1460.999988
> int daysSinceEpoch =3D -1460
> DateWritable having daysSinceEpoch=3D-1460 is 1966-01-02
>
>
>
>
>
>

--001a11340b14c546550512a3d19f--