Thanks in advance! Note that we will likely need a DatabaseAdapter for Phoenix, if only to be able to check the name. Ideally we should probably have a method on the adapter to get a clause that coerces a column to a Timestamp if need be (the generic one can be a no-op), I think right now we check the adapter's name to see if it has "Oracle" in it, and we may (temporarily) need to do the same for Phoenix.
Regards, Matt On Wed, Mar 14, 2018 at 2:52 PM, Juan Pablo Gardella <[email protected]> wrote: > Awesome, I will file a JIRA and do something similar for Phoenix. > > Thanks > > On Wed, 14 Mar 2018 at 15:50 Matt Burgess <[email protected]> wrote: >> >> Juan, >> >> We've had to do similar things for Oracle [1], so there is precedence, >> please feel free to create a JIRA to fix it, thanks! >> >> Regards, >> Matt >> >> [1] https://issues.apache.org/jira/browse/NIFI-2323 >> >> >> On Wed, Mar 14, 2018 at 2:43 PM, Juan Pablo Gardella >> <[email protected]> wrote: >> > Hello team, >> > >> > I'm testing QueryDatabaseAdapter against Phoenix DB and it cannot >> > convert >> > TIMESTAMP. The error is described below: >> > >> > >> > https://stackoverflow.com/questions/45989678/convert-varchar-to-timestamp-in-hbase >> > >> > Basically, it's required to use TO_TIMESTAMP(MAX_COLUMN) to make it >> > work. Do >> > you think worth to create a JIRA to fix it? Or are there a workaround >> > for >> > this? >> > >> > Juan
