You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2016/08/22 15:02:20 UTC
[jira] [Updated] (PHOENIX-2990) Ensure documentation on "time/date"
datatypes/functions acknowledge lack of JDBC compliance
[ https://issues.apache.org/jira/browse/PHOENIX-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Elser updated PHOENIX-2990:
--------------------------------
Fix Version/s: 4.8.1
> 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.9.0, 4.8.1
>
> Attachments: PHOENIX-2990.002.diff, 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)