[jira] [Updated] (HIVE-20340) Druid Needs Explicit CASTs from Timestamp to STRING when the output of timestamp function is used as String
[ https://issues.apache.org/jira/browse/HIVE-20340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vineet Garg updated HIVE-20340: --- Resolution: Fixed Fix Version/s: 4.0.0 Status: Resolved (was: Patch Available) > Druid Needs Explicit CASTs from Timestamp to STRING when the output of > timestamp function is used as String > --- > > Key: HIVE-20340 > URL: https://issues.apache.org/jira/browse/HIVE-20340 > Project: Hive > Issue Type: Bug > Components: Druid integration >Reporter: Vineet Garg >Assignee: Vineet Garg >Priority: Major > Fix For: 4.0.0 > > Attachments: HIVE-20340.1.patch, HIVE-20340.2.patch, > HIVE-20340.3.patch > > > Druid time expressions return numeric values in form of ms (instead of > formatted timestamp). Because of this expressions/function which expects its > argument as string type ended up returning different values for time > expressions input. > e.g. > {code} > SELECT SUBSTRING(to_date(datetime0),4) FROM tableau_orc.calcs; > | 4-07-25 | > SELECT SUBSTRING(to_date(datetime0),4) FROM druid_tableau.calcs; > | 002240 | > SELECT CONCAT(to_date(datetime0),' 00:00:00') FROM tableau_orc.calcs; > | 2004-07-17 00:00:00 | > SELECT CONCAT(to_date(datetime0),' 00:00:00') FROM druid_tableau.calcs; > | 109045440 00:00:00 | > {code} > Druid needs explicit cast to make this work -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-20340) Druid Needs Explicit CASTs from Timestamp to STRING when the output of timestamp function is used as String
[ https://issues.apache.org/jira/browse/HIVE-20340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vineet Garg updated HIVE-20340: --- Status: Open (was: Patch Available) > Druid Needs Explicit CASTs from Timestamp to STRING when the output of > timestamp function is used as String > --- > > Key: HIVE-20340 > URL: https://issues.apache.org/jira/browse/HIVE-20340 > Project: Hive > Issue Type: Bug > Components: Druid integration >Reporter: Vineet Garg >Assignee: Vineet Garg >Priority: Major > Attachments: HIVE-20340.1.patch, HIVE-20340.2.patch, > HIVE-20340.3.patch > > > Druid time expressions return numeric values in form of ms (instead of > formatted timestamp). Because of this expressions/function which expects its > argument as string type ended up returning different values for time > expressions input. > e.g. > {code} > SELECT SUBSTRING(to_date(datetime0),4) FROM tableau_orc.calcs; > | 4-07-25 | > SELECT SUBSTRING(to_date(datetime0),4) FROM druid_tableau.calcs; > | 002240 | > SELECT CONCAT(to_date(datetime0),' 00:00:00') FROM tableau_orc.calcs; > | 2004-07-17 00:00:00 | > SELECT CONCAT(to_date(datetime0),' 00:00:00') FROM druid_tableau.calcs; > | 109045440 00:00:00 | > {code} > Druid needs explicit cast to make this work -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-20340) Druid Needs Explicit CASTs from Timestamp to STRING when the output of timestamp function is used as String
[ https://issues.apache.org/jira/browse/HIVE-20340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vineet Garg updated HIVE-20340: --- Status: Patch Available (was: Open) > Druid Needs Explicit CASTs from Timestamp to STRING when the output of > timestamp function is used as String > --- > > Key: HIVE-20340 > URL: https://issues.apache.org/jira/browse/HIVE-20340 > Project: Hive > Issue Type: Bug > Components: Druid integration >Reporter: Vineet Garg >Assignee: Vineet Garg >Priority: Major > Attachments: HIVE-20340.1.patch, HIVE-20340.2.patch, > HIVE-20340.3.patch > > > Druid time expressions return numeric values in form of ms (instead of > formatted timestamp). Because of this expressions/function which expects its > argument as string type ended up returning different values for time > expressions input. > e.g. > {code} > SELECT SUBSTRING(to_date(datetime0),4) FROM tableau_orc.calcs; > | 4-07-25 | > SELECT SUBSTRING(to_date(datetime0),4) FROM druid_tableau.calcs; > | 002240 | > SELECT CONCAT(to_date(datetime0),' 00:00:00') FROM tableau_orc.calcs; > | 2004-07-17 00:00:00 | > SELECT CONCAT(to_date(datetime0),' 00:00:00') FROM druid_tableau.calcs; > | 109045440 00:00:00 | > {code} > Druid needs explicit cast to make this work -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-20340) Druid Needs Explicit CASTs from Timestamp to STRING when the output of timestamp function is used as String
[ https://issues.apache.org/jira/browse/HIVE-20340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vineet Garg updated HIVE-20340: --- Attachment: HIVE-20340.3.patch > Druid Needs Explicit CASTs from Timestamp to STRING when the output of > timestamp function is used as String > --- > > Key: HIVE-20340 > URL: https://issues.apache.org/jira/browse/HIVE-20340 > Project: Hive > Issue Type: Bug > Components: Druid integration >Reporter: Vineet Garg >Assignee: Vineet Garg >Priority: Major > Attachments: HIVE-20340.1.patch, HIVE-20340.2.patch, > HIVE-20340.3.patch > > > Druid time expressions return numeric values in form of ms (instead of > formatted timestamp). Because of this expressions/function which expects its > argument as string type ended up returning different values for time > expressions input. > e.g. > {code} > SELECT SUBSTRING(to_date(datetime0),4) FROM tableau_orc.calcs; > | 4-07-25 | > SELECT SUBSTRING(to_date(datetime0),4) FROM druid_tableau.calcs; > | 002240 | > SELECT CONCAT(to_date(datetime0),' 00:00:00') FROM tableau_orc.calcs; > | 2004-07-17 00:00:00 | > SELECT CONCAT(to_date(datetime0),' 00:00:00') FROM druid_tableau.calcs; > | 109045440 00:00:00 | > {code} > Druid needs explicit cast to make this work -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-20340) Druid Needs Explicit CASTs from Timestamp to STRING when the output of timestamp function is used as String
[ https://issues.apache.org/jira/browse/HIVE-20340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vineet Garg updated HIVE-20340: --- Attachment: HIVE-20340.2.patch > Druid Needs Explicit CASTs from Timestamp to STRING when the output of > timestamp function is used as String > --- > > Key: HIVE-20340 > URL: https://issues.apache.org/jira/browse/HIVE-20340 > Project: Hive > Issue Type: Bug > Components: Druid integration >Reporter: Vineet Garg >Assignee: Vineet Garg >Priority: Major > Attachments: HIVE-20340.1.patch, HIVE-20340.2.patch > > > Druid time expressions return numeric values in form of ms (instead of > formatted timestamp). Because of this expressions/function which expects its > argument as string type ended up returning different values for time > expressions input. > e.g. > {code} > SELECT SUBSTRING(to_date(datetime0),4) FROM tableau_orc.calcs; > | 4-07-25 | > SELECT SUBSTRING(to_date(datetime0),4) FROM druid_tableau.calcs; > | 002240 | > SELECT CONCAT(to_date(datetime0),' 00:00:00') FROM tableau_orc.calcs; > | 2004-07-17 00:00:00 | > SELECT CONCAT(to_date(datetime0),' 00:00:00') FROM druid_tableau.calcs; > | 109045440 00:00:00 | > {code} > Druid needs explicit cast to make this work -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-20340) Druid Needs Explicit CASTs from Timestamp to STRING when the output of timestamp function is used as String
[ https://issues.apache.org/jira/browse/HIVE-20340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vineet Garg updated HIVE-20340: --- Status: Patch Available (was: Open) > Druid Needs Explicit CASTs from Timestamp to STRING when the output of > timestamp function is used as String > --- > > Key: HIVE-20340 > URL: https://issues.apache.org/jira/browse/HIVE-20340 > Project: Hive > Issue Type: Bug > Components: Druid integration >Reporter: Vineet Garg >Assignee: Vineet Garg >Priority: Major > Attachments: HIVE-20340.1.patch > > > Druid time expressions return numeric values in form of ms (instead of > formatted timestamp). Because of this expressions/function which expects its > argument as string type ended up returning different values for time > expressions input. > e.g. > {code} > SELECT SUBSTRING(to_date(datetime0),4) FROM tableau_orc.calcs; > | 4-07-25 | > SELECT SUBSTRING(to_date(datetime0),4) FROM druid_tableau.calcs; > | 002240 | > SELECT CONCAT(to_date(datetime0),' 00:00:00') FROM tableau_orc.calcs; > | 2004-07-17 00:00:00 | > SELECT CONCAT(to_date(datetime0),' 00:00:00') FROM druid_tableau.calcs; > | 109045440 00:00:00 | > {code} > Druid needs explicit cast to make this work -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-20340) Druid Needs Explicit CASTs from Timestamp to STRING when the output of timestamp function is used as String
[ https://issues.apache.org/jira/browse/HIVE-20340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vineet Garg updated HIVE-20340: --- Attachment: HIVE-20340.1.patch > Druid Needs Explicit CASTs from Timestamp to STRING when the output of > timestamp function is used as String > --- > > Key: HIVE-20340 > URL: https://issues.apache.org/jira/browse/HIVE-20340 > Project: Hive > Issue Type: Bug > Components: Druid integration >Reporter: Vineet Garg >Assignee: Vineet Garg >Priority: Major > Attachments: HIVE-20340.1.patch > > > Druid time expressions return numeric values in form of ms (instead of > formatted timestamp). Because of this expressions/function which expects its > argument as string type ended up returning different values for time > expressions input. > e.g. > {code} > SELECT SUBSTRING(to_date(datetime0),4) FROM tableau_orc.calcs; > | 4-07-25 | > SELECT SUBSTRING(to_date(datetime0),4) FROM druid_tableau.calcs; > | 002240 | > SELECT CONCAT(to_date(datetime0),' 00:00:00') FROM tableau_orc.calcs; > | 2004-07-17 00:00:00 | > SELECT CONCAT(to_date(datetime0),' 00:00:00') FROM druid_tableau.calcs; > | 109045440 00:00:00 | > {code} > Druid needs explicit cast to make this work -- This message was sent by Atlassian JIRA (v7.6.3#76005)