phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-2990) Ensure documentation on "time/date" datatypes/functions acknowledge lack of JDBC compliance
Date Thu, 01 Sep 2016 16:59:20 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455998#comment-15455998
] 

Josh Elser commented on PHOENIX-2990:
-------------------------------------

bq. There's a long standing bug (I finally just documented the workaround here[1]). You need
to manually remove site/publish/language/*.html before running ./build.sh to get the language
htmls to regenerate. Would be great if this happened automatically.

Aha!! I'm glad I asked again :) Thanks!

> 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)

Mime
View raw message