[jira] [Updated] (PHOENIX-2990) Ensure documentation on "time/date" datatypes/functions acknowledge lack of JDBC compliance

["Josh Elser (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/PHOENIX-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Elser updated PHOENIX-2990:
--------------------------------
    Attachment: PHOENIX-2990.diff

Some quick updates to the website's Data Type and Function reference guides. DATE should only be "yyyy-MM-dd" and TIME should only be "hh:mm:ss". The Data Type entries are updated to call this out and functions which return date or time refer to the clarification on the data type definition.


Will let this up for a little before committing to make sure the verbage is clear.

> Ensure documentation on "time/date" datatypes/functions acknowledge lack of JDBC compliance
> -------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-2990
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2990
>             Project: Phoenix
>          Issue Type: Task
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 4.8.0
>
>         Attachments: PHOENIX-2990.diff
>
>
> In talking with [~speleato] about some differences in test cases between the thick and thin driver and DATE/TIMESTAMP datatypes, Sergio asked me if the docs were accurate on the Phoenix website about this.
> Taking a look at Data Types and Functions documentation, we don't outwardly warn users that these are not 100% compliant with the JDBC APIs.
> We do have the issue tracked in JIRA in PHOENIX-868 (and more, i'm sure), but it would be good to make sure the website is also forward in warning users.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)