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

ASF GitHub Bot commented on KYLIN-3025:
---------------------------------------

asfgit commented on issue #158: KYLIN-3025 fix error: {fn CONVERT} for bigint 
type in tableau 10.4
URL: https://github.com/apache/kylin/pull/158#issuecomment-399852166
 
 
   Can one of the admins verify this patch?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> kylin odbc error : {fn CONVERT} for bigint type in tableau 10.4
> ---------------------------------------------------------------
>
>                 Key: KYLIN-3025
>                 URL: https://issues.apache.org/jira/browse/KYLIN-3025
>             Project: Kylin
>          Issue Type: Bug
>          Components: Driver - ODBC
>    Affects Versions: v2.1.0
>         Environment: Windows 10;kylin v2.2.0;tableau desktop 10.4;kylin odbc 
> v2.1.0
>            Reporter: Hokyung Song
>            Priority: Major
>             Fix For: v2.5.0
>
>
> In Tableau Desktop version 9.3, also it works very well.
> but..when I use measure field (bigint type of data) in Tableau Desktop 
> version 10.4, it occured query error. (decimal type field works well.)
> I guess.. "{fn CONVERT}" function couldn't parsed. please support tableau 
> 10.4 :)
> Detailed query example from tableau:
> {code}
> SELECT "MOMENT"."P_DT" AS "P_DT",
>   SUM({fn CONVERT("MOMENT"."ACTIONCOUNT", SQL_BIGINT)}) AS 
> "sum_ACTIONCOUNT_ok"
> FROM "TEST"."MOMENT" "MOMENT"
> GROUP BY "MOMENT"."P_DT"
> {code}
> ----
> environment
> ----
> * kylin server : v2.2.0
> * kylin odbc (for windows client) : v2.1.0
> * tableau desktop : 10.4
> * client os : windows 10 (64bit)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to