Hi James, Thanks for the quick response. I will test my stuff with changes that you suggested. I was just worried about rewriting Date Columns. This seems to be an easier fix. :)
Thanks, Anil Gupta On Tue, Apr 22, 2014 at 5:20 PM, James Taylor <[email protected]>wrote: > Hi Anil, > Please see http://phoenix.incubator.apache.org/upgrade_from_2_2.html for > how to upgrade from Phoenix 2.2.x to Apache Phoenix 3.0/4.0. Part of what > this will do is modify your table metadata to use the UNSIGNED_DATE, > UNSIGNED_TIME, and UNSIGNED_TIMESTAMP types instead of the now signed ones. > The reason this change was made is so that we can support negative time > values to increase the range of dates we can represent (PHOENIX-618). If > you have any explicit code references to the internal PDataType enum for > PDataType.DATE, PDataType.TIME, or PDataType.TIMESTAMP, these should be > updated as well to their UNSIGNED equivalent. > Thanks, > James > > > On Tue, Apr 22, 2014 at 5:12 PM, anil gupta <[email protected]> wrote: > > > Hi All, > > > > We have written data into our HBase tables using PDataType of > Phoenix2.0.2. > > We have custom MR loaders that use PDataType so that we can use Phoenix > for > > adhoc querying > > I am trying to migrate to Phoenix3.0.0, but all the Date type columns > > values are not coming out correctly. These are big tables(TB's of data) > and > > i would like to avoid making changes in my tables due to Phoenix upgrade > to > > 3.0.0. > > Is Phoenix3.0.0 not backward compatible with Phoenix2.0.2? Is there any > > easy fix for this(without rewriting Date Columns)? Also, i am curious to > > know what was broken in Date DataType in Phoenix2.0.2? > > > > -- > > Thanks & Regards, > > Anil Gupta > > > -- Thanks & Regards, Anil Gupta
