Poking at this, > select current_time(); +-------------------------------------+ | TIME '292278994-08-17 07:12:55.807' | +-------------------------------------+ | 292278994-08-17 07:12:55.807 | +-------------------------------------+ 1 row selected (79.6 seconds)
With a debugger attached, CurrentTime(long) is being invoked with Long.MAX_VALUE, presumably from HConstants.LATEST_TIMESTAMP via the StatementContext. On Mon, Jan 18, 2016 at 4:52 PM, James Taylor <[email protected]> wrote: > Ankit, > Would you mind posting a sample of the code you're using to get date value? > Are you using resultSet.getDate(1)? > Thanks, > James > > On Mon, Jan 18, 2016 at 4:49 PM, Nick Dimiduk <[email protected]> wrote: > > > Hi Ankit, > > > > This looks like a bug to me too. Do you mind filing a JIRA for this? > > > > Thanks, > > Nick > > > > On Fri, Jan 15, 2016 at 5:07 AM, Ankit Agarwal < > [email protected] > > > > > wrote: > > > > > Hi, > > > > > > I am trying Apache Phoenix with Hbase. When I run try to get current > time > > > using select current_time(), its giving me some weird value. > > > (292278994-08-17 07:12:55.807). Similarly for current_date() or now() > > > query. I am not able to understand what does this mean, and how to get > > the > > > current time (as we get from mysql now() function). Because of this I > am > > > unable to set the data type for view column as Date or Timestamp, as > its > > > doing some weird conversion. > > > > > > Can anyone help me figure out a solution for this. > > > > > > Thanks & Regards > > > > > > -- > > > > > > > > > *Ankit Agarwal* > > > *Software Development EngineerPh. No. +91-8095470278* > > > > > >
