The unsigned date specifically says, "The purpose of this type is to map to existing HBase data that was serialized using this HBase utility method." When you stored these values, did you use that method? According to the docs, "If that is not the case, use the regular signed type instead."
I'm not an expert on those data types, but I hope that helps. William Watson Software Engineer (904) 705-7056 PCS On Thu, Apr 16, 2015 at 7:08 AM, Matthew Johnson <matt.john...@algomi.com> wrote: > Hi all, > > > > I have a bunch of millisecond timestamps stored in HBase as Long values. I > have a Phoenix view that reads these values as an UNSIGNED_DATE. Now that > the clocks have gone forwards, the Phoenix driver has automatically applied > the timezone change and as a result all of my Long values are being > converted an hour off. Is there a way to set the timezone in Phoenix so > that it will read the longs to dates as GMT+0000 (since this is what the > millisecond values represent). > > > > Or, should I create a new view and create it to return an UNSIGNED_LONG, > and then use the ‘to_date’ function and pass in a timezone? This is less > convenient as it would mean using the function everywhere where we have > queries, but is an option. > > > > Thanks, > > Matt > > >
