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

Gabor Arki updated KYLIN-4382:
------------------------------
    Description: 
h4. Environment
 * Kylin JDBC driver: 3.0.0
 * Kylin server: 3.0.0

h4. Reproduction steps
 * Use a cube with a DATE column (like the derived day_start)
 * Create a prepared statement and try to filter with this column in a where 
clause
 * Pass the values as java.sql.Date type

h4. Expected result
 * The proper response is provided for the query with the values for the 
specified date(s)

h4. Actual result
 * No data is returned
 * StreamStorageQuery's _Skip cube segment_ log message is containing the 
filter with an epoch day value, for example: {{}}{{DAY_START GTE [18231]}}
 * Executing the same query from the web UI you get the expected response. Now 
the same log message is containing the filter in epoch millis format, for 
example: {{DAY_START IN [1580774400000, 1580860800000]}}

 * Passing the value as String instead of java.sql.Date fails on server-side 
with: {{exception while executing query: java.lang.String cannot be cast to 
java.lang.Integer}}
 * Passing the value as java.sql.Timestamp or java.util.Date fails on 
server-side with: {{exception while executing query: java.lang.Long cannot be 
cast to java.lang.Integer}}

 

  was:
h4. Environment
 * Kylin JDBC driver: 3.0.0
 * Kylin server: 3.0.0

h4. Reproduction steps
 * Use a cube with a DATE column (like the derived day_start)
 * Create a prepared statement and try to filter with this column in a where 
clause
 * Pass the values as java.sql.Date type

h4. Expected result
 * The proper response is provided for the query with the values for the 
specified date(s)

h4. Actual result
 * No data is returned
 * 
StreamStorageQuery's _Skip cube segment_ log message is containing the filter 
with an epoch day value, for example: {{}}{{DAY_START GTE [18231]}}
 * Executing the same query from the web UI you get the expected response. Now 
the same log message is containing the filter in epoch millis format, for 
example: {{DAY_START IN [1580774400000, 1580860800000]}}

 * Passing the value as String instead of java.sql.Date fails on server-side 
with: {{exception while executing query: java.lang.String cannot be cast to 
java.lang.Integer}}
 * Passing the value as java.sql.Timestamp or java.util.Date fails on 
server-side with: {{exception while executing query: java.lang.Long cannot be 
cast to java.lang.Integer}}

 


> Unable to use DATE type in prepared statements
> ----------------------------------------------
>
>                 Key: KYLIN-4382
>                 URL: https://issues.apache.org/jira/browse/KYLIN-4382
>             Project: Kylin
>          Issue Type: Bug
>          Components: Query Engine
>            Reporter: Gabor Arki
>            Priority: Major
>
> h4. Environment
>  * Kylin JDBC driver: 3.0.0
>  * Kylin server: 3.0.0
> h4. Reproduction steps
>  * Use a cube with a DATE column (like the derived day_start)
>  * Create a prepared statement and try to filter with this column in a where 
> clause
>  * Pass the values as java.sql.Date type
> h4. Expected result
>  * The proper response is provided for the query with the values for the 
> specified date(s)
> h4. Actual result
>  * No data is returned
>  * StreamStorageQuery's _Skip cube segment_ log message is containing the 
> filter with an epoch day value, for example: {{}}{{DAY_START GTE [18231]}}
>  * Executing the same query from the web UI you get the expected response. 
> Now the same log message is containing the filter in epoch millis format, for 
> example: {{DAY_START IN [1580774400000, 1580860800000]}}
>  * Passing the value as String instead of java.sql.Date fails on server-side 
> with: {{exception while executing query: java.lang.String cannot be cast to 
> java.lang.Integer}}
>  * Passing the value as java.sql.Timestamp or java.util.Date fails on 
> server-side with: {{exception while executing query: java.lang.Long cannot be 
> cast to java.lang.Integer}}
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to