[jira] [Updated] (HIVE-22763) 0 is accepted in 12-hour format during timestamp cast
[ https://issues.apache.org/jira/browse/HIVE-22763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marta Kuczora updated HIVE-22763: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to master. Thanks [~klcopp] for the patch and [~belugabehr] for the review! > 0 is accepted in 12-hour format during timestamp cast > - > > Key: HIVE-22763 > URL: https://issues.apache.org/jira/browse/HIVE-22763 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Karen Coppage >Assignee: Karen Coppage >Priority: Minor > Fix For: 4.0.0 > > Attachments: HIVE-22763.01.patch, HIVE-22763.01.patch, > HIVE-22763.01.patch, HIVE-22763.01.patch, HIVE-22763.01.patch, > HIVE-22763.01.patch, HIVE-22763.02.patch, HIVE-22763.03.patch, > HIVE-22763.04.patch, HIVE-22763.04.patch > > > Having a timestamp string in 12-hour format can be parsed if the hour is 0, > however, based on the [design > document|https://docs.google.com/document/d/1V7k6-lrPGW7_uhqM-FhKl3QsxwCRy69v2KIxPsGjc1k/edit], > it should be rejected. > h3. How to reproduce > Run {code}select cast("2020-01-01 0 am 00" as timestamp format "-mm-dd > hh12 p.m. ss"){code} > It shouldn' t be parsed, as the hour component is 0. > h3. Spec > ||Pattern||Meaning||Additional details|| > |HH12|Hour of day (1-12)|Same as HH| > |HH|Hour of day (1-12)|{panel:borderStyle=none} > - One digit inputs are possible in a string to datetime conversion but needs > to be surrounded by separators. > - In a datetime to string conversion one digit hours are prefixed with a zero. > - Error if provided hour is not between 1 and 12. > - Displaying an unformatted timestamp in Impala uses the HH24 format > regardless if it was created using HH12. > - If no AM/PM provided then defaults to AM. > - In string to datetime conversion, conflicts with S and > HH24.{panel:borderStyle=none}| -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HIVE-22763) 0 is accepted in 12-hour format during timestamp cast
[ https://issues.apache.org/jira/browse/HIVE-22763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Coppage updated HIVE-22763: - Attachment: HIVE-22763.04.patch Status: Patch Available (was: Open) > 0 is accepted in 12-hour format during timestamp cast > - > > Key: HIVE-22763 > URL: https://issues.apache.org/jira/browse/HIVE-22763 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Karen Coppage >Assignee: Karen Coppage >Priority: Minor > Fix For: 4.0.0 > > Attachments: HIVE-22763.01.patch, HIVE-22763.01.patch, > HIVE-22763.01.patch, HIVE-22763.01.patch, HIVE-22763.01.patch, > HIVE-22763.01.patch, HIVE-22763.02.patch, HIVE-22763.03.patch, > HIVE-22763.04.patch, HIVE-22763.04.patch > > > Having a timestamp string in 12-hour format can be parsed if the hour is 0, > however, based on the [design > document|https://docs.google.com/document/d/1V7k6-lrPGW7_uhqM-FhKl3QsxwCRy69v2KIxPsGjc1k/edit], > it should be rejected. > h3. How to reproduce > Run {code}select cast("2020-01-01 0 am 00" as timestamp format "-mm-dd > hh12 p.m. ss"){code} > It shouldn' t be parsed, as the hour component is 0. > h3. Spec > ||Pattern||Meaning||Additional details|| > |HH12|Hour of day (1-12)|Same as HH| > |HH|Hour of day (1-12)|{panel:borderStyle=none} > - One digit inputs are possible in a string to datetime conversion but needs > to be surrounded by separators. > - In a datetime to string conversion one digit hours are prefixed with a zero. > - Error if provided hour is not between 1 and 12. > - Displaying an unformatted timestamp in Impala uses the HH24 format > regardless if it was created using HH12. > - If no AM/PM provided then defaults to AM. > - In string to datetime conversion, conflicts with S and > HH24.{panel:borderStyle=none}| -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HIVE-22763) 0 is accepted in 12-hour format during timestamp cast
[ https://issues.apache.org/jira/browse/HIVE-22763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Coppage updated HIVE-22763: - Status: Open (was: Patch Available) > 0 is accepted in 12-hour format during timestamp cast > - > > Key: HIVE-22763 > URL: https://issues.apache.org/jira/browse/HIVE-22763 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Karen Coppage >Assignee: Karen Coppage >Priority: Minor > Fix For: 4.0.0 > > Attachments: HIVE-22763.01.patch, HIVE-22763.01.patch, > HIVE-22763.01.patch, HIVE-22763.01.patch, HIVE-22763.01.patch, > HIVE-22763.01.patch, HIVE-22763.02.patch, HIVE-22763.03.patch, > HIVE-22763.04.patch > > > Having a timestamp string in 12-hour format can be parsed if the hour is 0, > however, based on the [design > document|https://docs.google.com/document/d/1V7k6-lrPGW7_uhqM-FhKl3QsxwCRy69v2KIxPsGjc1k/edit], > it should be rejected. > h3. How to reproduce > Run {code}select cast("2020-01-01 0 am 00" as timestamp format "-mm-dd > hh12 p.m. ss"){code} > It shouldn' t be parsed, as the hour component is 0. > h3. Spec > ||Pattern||Meaning||Additional details|| > |HH12|Hour of day (1-12)|Same as HH| > |HH|Hour of day (1-12)|{panel:borderStyle=none} > - One digit inputs are possible in a string to datetime conversion but needs > to be surrounded by separators. > - In a datetime to string conversion one digit hours are prefixed with a zero. > - Error if provided hour is not between 1 and 12. > - Displaying an unformatted timestamp in Impala uses the HH24 format > regardless if it was created using HH12. > - If no AM/PM provided then defaults to AM. > - In string to datetime conversion, conflicts with S and > HH24.{panel:borderStyle=none}| -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HIVE-22763) 0 is accepted in 12-hour format during timestamp cast
[ https://issues.apache.org/jira/browse/HIVE-22763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Coppage updated HIVE-22763: - Attachment: HIVE-22763.04.patch > 0 is accepted in 12-hour format during timestamp cast > - > > Key: HIVE-22763 > URL: https://issues.apache.org/jira/browse/HIVE-22763 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Karen Coppage >Assignee: Karen Coppage >Priority: Minor > Fix For: 4.0.0 > > Attachments: HIVE-22763.01.patch, HIVE-22763.01.patch, > HIVE-22763.01.patch, HIVE-22763.01.patch, HIVE-22763.01.patch, > HIVE-22763.01.patch, HIVE-22763.02.patch, HIVE-22763.03.patch, > HIVE-22763.04.patch > > > Having a timestamp string in 12-hour format can be parsed if the hour is 0, > however, based on the [design > document|https://docs.google.com/document/d/1V7k6-lrPGW7_uhqM-FhKl3QsxwCRy69v2KIxPsGjc1k/edit], > it should be rejected. > h3. How to reproduce > Run {code}select cast("2020-01-01 0 am 00" as timestamp format "-mm-dd > hh12 p.m. ss"){code} > It shouldn' t be parsed, as the hour component is 0. > h3. Spec > ||Pattern||Meaning||Additional details|| > |HH12|Hour of day (1-12)|Same as HH| > |HH|Hour of day (1-12)|{panel:borderStyle=none} > - One digit inputs are possible in a string to datetime conversion but needs > to be surrounded by separators. > - In a datetime to string conversion one digit hours are prefixed with a zero. > - Error if provided hour is not between 1 and 12. > - Displaying an unformatted timestamp in Impala uses the HH24 format > regardless if it was created using HH12. > - If no AM/PM provided then defaults to AM. > - In string to datetime conversion, conflicts with S and > HH24.{panel:borderStyle=none}| -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HIVE-22763) 0 is accepted in 12-hour format during timestamp cast
[ https://issues.apache.org/jira/browse/HIVE-22763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Coppage updated HIVE-22763: - Attachment: HIVE-22763.03.patch > 0 is accepted in 12-hour format during timestamp cast > - > > Key: HIVE-22763 > URL: https://issues.apache.org/jira/browse/HIVE-22763 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Karen Coppage >Assignee: Karen Coppage >Priority: Minor > Fix For: 4.0.0 > > Attachments: HIVE-22763.01.patch, HIVE-22763.01.patch, > HIVE-22763.01.patch, HIVE-22763.01.patch, HIVE-22763.01.patch, > HIVE-22763.01.patch, HIVE-22763.02.patch, HIVE-22763.03.patch > > > Having a timestamp string in 12-hour format can be parsed if the hour is 0, > however, based on the [design > document|https://docs.google.com/document/d/1V7k6-lrPGW7_uhqM-FhKl3QsxwCRy69v2KIxPsGjc1k/edit], > it should be rejected. > h3. How to reproduce > Run {code}select cast("2020-01-01 0 am 00" as timestamp format "-mm-dd > hh12 p.m. ss"){code} > It shouldn' t be parsed, as the hour component is 0. > h3. Spec > ||Pattern||Meaning||Additional details|| > |HH12|Hour of day (1-12)|Same as HH| > |HH|Hour of day (1-12)|{panel:borderStyle=none} > - One digit inputs are possible in a string to datetime conversion but needs > to be surrounded by separators. > - In a datetime to string conversion one digit hours are prefixed with a zero. > - Error if provided hour is not between 1 and 12. > - Displaying an unformatted timestamp in Impala uses the HH24 format > regardless if it was created using HH12. > - If no AM/PM provided then defaults to AM. > - In string to datetime conversion, conflicts with S and > HH24.{panel:borderStyle=none}| -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HIVE-22763) 0 is accepted in 12-hour format during timestamp cast
[ https://issues.apache.org/jira/browse/HIVE-22763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Coppage updated HIVE-22763: - Attachment: HIVE-22763.02.patch > 0 is accepted in 12-hour format during timestamp cast > - > > Key: HIVE-22763 > URL: https://issues.apache.org/jira/browse/HIVE-22763 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Karen Coppage >Assignee: Karen Coppage >Priority: Minor > Fix For: 4.0.0 > > Attachments: HIVE-22763.01.patch, HIVE-22763.01.patch, > HIVE-22763.01.patch, HIVE-22763.01.patch, HIVE-22763.01.patch, > HIVE-22763.01.patch, HIVE-22763.02.patch > > > Having a timestamp string in 12-hour format can be parsed if the hour is 0, > however, based on the [design > document|https://docs.google.com/document/d/1V7k6-lrPGW7_uhqM-FhKl3QsxwCRy69v2KIxPsGjc1k/edit], > it should be rejected. > h3. How to reproduce > Run {code}select cast("2020-01-01 0 am 00" as timestamp format "-mm-dd > hh12 p.m. ss"){code} > It shouldn' t be parsed, as the hour component is 0. > h3. Spec > ||Pattern||Meaning||Additional details|| > |HH12|Hour of day (1-12)|Same as HH| > |HH|Hour of day (1-12)|{panel:borderStyle=none} > - One digit inputs are possible in a string to datetime conversion but needs > to be surrounded by separators. > - In a datetime to string conversion one digit hours are prefixed with a zero. > - Error if provided hour is not between 1 and 12. > - Displaying an unformatted timestamp in Impala uses the HH24 format > regardless if it was created using HH12. > - If no AM/PM provided then defaults to AM. > - In string to datetime conversion, conflicts with S and > HH24.{panel:borderStyle=none}| -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HIVE-22763) 0 is accepted in 12-hour format during timestamp cast
[ https://issues.apache.org/jira/browse/HIVE-22763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Mollitor updated HIVE-22763: -- Description: Having a timestamp string in 12-hour format can be parsed if the hour is 0, however, based on the [design document|https://docs.google.com/document/d/1V7k6-lrPGW7_uhqM-FhKl3QsxwCRy69v2KIxPsGjc1k/edit], it should be rejected. h3. How to reproduce Run {code}select cast("2020-01-01 0 am 00" as timestamp format "-mm-dd hh12 p.m. ss"){code} It shouldn' t be parsed, as the hour component is 0. h3. Spec ||Pattern||Meaning||Additional details|| |HH12|Hour of day (1-12)|Same as HH| |HH|Hour of day (1-12)|{panel:borderStyle=none} - One digit inputs are possible in a string to datetime conversion but needs to be surrounded by separators. - In a datetime to string conversion one digit hours are prefixed with a zero. - Error if provided hour is not between 1 and 12. - Displaying an unformatted timestamp in Impala uses the HH24 format regardless if it was created using HH12. - If no AM/PM provided then defaults to AM. - In string to datetime conversion, conflicts with S and HH24.{panel:borderStyle=none}| was: Having a timestamp string in 12-hour format can be parsed if the hour is 0, however, based on the [design document|https://docs.google.com/document/d/1V7k6-lrPGW7_uhqM-FhKl3QsxwCRy69v2KIxPsGjc1k/edit], it should be rejected. h3. How to reproduce Run {code}select cast("2020-01-01 0 am 00" as timestamp format "-mm-dd hh12 p.m. ss"){code} It shouldn' t be parsed, as the hour component is 0. > 0 is accepted in 12-hour format during timestamp cast > - > > Key: HIVE-22763 > URL: https://issues.apache.org/jira/browse/HIVE-22763 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Karen Coppage >Assignee: Karen Coppage >Priority: Minor > Fix For: 4.0.0 > > Attachments: HIVE-22763.01.patch, HIVE-22763.01.patch, > HIVE-22763.01.patch, HIVE-22763.01.patch, HIVE-22763.01.patch, > HIVE-22763.01.patch > > > Having a timestamp string in 12-hour format can be parsed if the hour is 0, > however, based on the [design > document|https://docs.google.com/document/d/1V7k6-lrPGW7_uhqM-FhKl3QsxwCRy69v2KIxPsGjc1k/edit], > it should be rejected. > h3. How to reproduce > Run {code}select cast("2020-01-01 0 am 00" as timestamp format "-mm-dd > hh12 p.m. ss"){code} > It shouldn' t be parsed, as the hour component is 0. > h3. Spec > ||Pattern||Meaning||Additional details|| > |HH12|Hour of day (1-12)|Same as HH| > |HH|Hour of day (1-12)|{panel:borderStyle=none} > - One digit inputs are possible in a string to datetime conversion but needs > to be surrounded by separators. > - In a datetime to string conversion one digit hours are prefixed with a zero. > - Error if provided hour is not between 1 and 12. > - Displaying an unformatted timestamp in Impala uses the HH24 format > regardless if it was created using HH12. > - If no AM/PM provided then defaults to AM. > - In string to datetime conversion, conflicts with S and > HH24.{panel:borderStyle=none}| -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HIVE-22763) 0 is accepted in 12-hour format during timestamp cast
[ https://issues.apache.org/jira/browse/HIVE-22763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Coppage updated HIVE-22763: - Attachment: HIVE-22763.01.patch Status: Patch Available (was: Open) > 0 is accepted in 12-hour format during timestamp cast > - > > Key: HIVE-22763 > URL: https://issues.apache.org/jira/browse/HIVE-22763 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Karen Coppage >Assignee: Karen Coppage >Priority: Minor > Fix For: 4.0.0 > > Attachments: HIVE-22763.01.patch, HIVE-22763.01.patch, > HIVE-22763.01.patch, HIVE-22763.01.patch, HIVE-22763.01.patch, > HIVE-22763.01.patch > > > Having a timestamp string in 12-hour format can be parsed if the hour is 0, > however, based on the [design > document|https://docs.google.com/document/d/1V7k6-lrPGW7_uhqM-FhKl3QsxwCRy69v2KIxPsGjc1k/edit], > it should be rejected. > h3. How to reproduce > Run {code}select cast("2020-01-01 0 am 00" as timestamp format "-mm-dd > hh12 p.m. ss"){code} > It shouldn' t be parsed, as the hour component is 0. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HIVE-22763) 0 is accepted in 12-hour format during timestamp cast
[ https://issues.apache.org/jira/browse/HIVE-22763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Coppage updated HIVE-22763: - Status: Open (was: Patch Available) > 0 is accepted in 12-hour format during timestamp cast > - > > Key: HIVE-22763 > URL: https://issues.apache.org/jira/browse/HIVE-22763 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Karen Coppage >Assignee: Karen Coppage >Priority: Minor > Fix For: 4.0.0 > > Attachments: HIVE-22763.01.patch, HIVE-22763.01.patch, > HIVE-22763.01.patch, HIVE-22763.01.patch, HIVE-22763.01.patch, > HIVE-22763.01.patch > > > Having a timestamp string in 12-hour format can be parsed if the hour is 0, > however, based on the [design > document|https://docs.google.com/document/d/1V7k6-lrPGW7_uhqM-FhKl3QsxwCRy69v2KIxPsGjc1k/edit], > it should be rejected. > h3. How to reproduce > Run {code}select cast("2020-01-01 0 am 00" as timestamp format "-mm-dd > hh12 p.m. ss"){code} > It shouldn' t be parsed, as the hour component is 0. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HIVE-22763) 0 is accepted in 12-hour format during timestamp cast
[ https://issues.apache.org/jira/browse/HIVE-22763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Coppage updated HIVE-22763: - Attachment: HIVE-22763.01.patch Status: Patch Available (was: Open) > 0 is accepted in 12-hour format during timestamp cast > - > > Key: HIVE-22763 > URL: https://issues.apache.org/jira/browse/HIVE-22763 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Karen Coppage >Assignee: Karen Coppage >Priority: Minor > Fix For: 4.0.0 > > Attachments: HIVE-22763.01.patch, HIVE-22763.01.patch, > HIVE-22763.01.patch, HIVE-22763.01.patch, HIVE-22763.01.patch > > > Having a timestamp string in 12-hour format can be parsed if the hour is 0, > however, based on the [design > document|https://docs.google.com/document/d/1V7k6-lrPGW7_uhqM-FhKl3QsxwCRy69v2KIxPsGjc1k/edit], > it should be rejected. > h3. How to reproduce > Run {code}select cast("2020-01-01 0 am 00" as timestamp format "-mm-dd > hh12 p.m. ss"){code} > It shouldn' t be parsed, as the hour component is 0. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HIVE-22763) 0 is accepted in 12-hour format during timestamp cast
[ https://issues.apache.org/jira/browse/HIVE-22763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Coppage updated HIVE-22763: - Status: Open (was: Patch Available) > 0 is accepted in 12-hour format during timestamp cast > - > > Key: HIVE-22763 > URL: https://issues.apache.org/jira/browse/HIVE-22763 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Karen Coppage >Assignee: Karen Coppage >Priority: Minor > Fix For: 4.0.0 > > Attachments: HIVE-22763.01.patch, HIVE-22763.01.patch, > HIVE-22763.01.patch, HIVE-22763.01.patch > > > Having a timestamp string in 12-hour format can be parsed if the hour is 0, > however, based on the [design > document|https://docs.google.com/document/d/1V7k6-lrPGW7_uhqM-FhKl3QsxwCRy69v2KIxPsGjc1k/edit], > it should be rejected. > h3. How to reproduce > Run {code}select cast("2020-01-01 0 am 00" as timestamp format "-mm-dd > hh12 p.m. ss"){code} > It shouldn' t be parsed, as the hour component is 0. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HIVE-22763) 0 is accepted in 12-hour format during timestamp cast
[ https://issues.apache.org/jira/browse/HIVE-22763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Coppage updated HIVE-22763: - Attachment: HIVE-22763.01.patch Status: Patch Available (was: Open) > 0 is accepted in 12-hour format during timestamp cast > - > > Key: HIVE-22763 > URL: https://issues.apache.org/jira/browse/HIVE-22763 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Karen Coppage >Assignee: Karen Coppage >Priority: Minor > Fix For: 4.0.0 > > Attachments: HIVE-22763.01.patch, HIVE-22763.01.patch, > HIVE-22763.01.patch, HIVE-22763.01.patch > > > Having a timestamp string in 12-hour format can be parsed if the hour is 0, > however, based on the [design > document|https://docs.google.com/document/d/1V7k6-lrPGW7_uhqM-FhKl3QsxwCRy69v2KIxPsGjc1k/edit], > it should be rejected. > h3. How to reproduce > Run {code}select cast("2020-01-01 0 am 00" as timestamp format "-mm-dd > hh12 p.m. ss"){code} > It shouldn' t be parsed, as the hour component is 0. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HIVE-22763) 0 is accepted in 12-hour format during timestamp cast
[ https://issues.apache.org/jira/browse/HIVE-22763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Coppage updated HIVE-22763: - Status: Open (was: Patch Available) > 0 is accepted in 12-hour format during timestamp cast > - > > Key: HIVE-22763 > URL: https://issues.apache.org/jira/browse/HIVE-22763 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Karen Coppage >Assignee: Karen Coppage >Priority: Minor > Fix For: 4.0.0 > > Attachments: HIVE-22763.01.patch, HIVE-22763.01.patch, > HIVE-22763.01.patch, HIVE-22763.01.patch > > > Having a timestamp string in 12-hour format can be parsed if the hour is 0, > however, based on the [design > document|https://docs.google.com/document/d/1V7k6-lrPGW7_uhqM-FhKl3QsxwCRy69v2KIxPsGjc1k/edit], > it should be rejected. > h3. How to reproduce > Run {code}select cast("2020-01-01 0 am 00" as timestamp format "-mm-dd > hh12 p.m. ss"){code} > It shouldn' t be parsed, as the hour component is 0. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HIVE-22763) 0 is accepted in 12-hour format during timestamp cast
[ https://issues.apache.org/jira/browse/HIVE-22763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Coppage updated HIVE-22763: - Status: Open (was: Patch Available) > 0 is accepted in 12-hour format during timestamp cast > - > > Key: HIVE-22763 > URL: https://issues.apache.org/jira/browse/HIVE-22763 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Karen Coppage >Assignee: Karen Coppage >Priority: Minor > Fix For: 4.0.0 > > Attachments: HIVE-22763.01.patch, HIVE-22763.01.patch, > HIVE-22763.01.patch > > > Having a timestamp string in 12-hour format can be parsed if the hour is 0, > however, based on the [design > document|https://docs.google.com/document/d/1V7k6-lrPGW7_uhqM-FhKl3QsxwCRy69v2KIxPsGjc1k/edit], > it should be rejected. > h3. How to reproduce > Run {code}select cast("2020-01-01 0 am 00" as timestamp format "-mm-dd > hh12 p.m. ss"){code} > It shouldn' t be parsed, as the hour component is 0. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HIVE-22763) 0 is accepted in 12-hour format during timestamp cast
[ https://issues.apache.org/jira/browse/HIVE-22763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Coppage updated HIVE-22763: - Attachment: HIVE-22763.01.patch Status: Patch Available (was: Open) > 0 is accepted in 12-hour format during timestamp cast > - > > Key: HIVE-22763 > URL: https://issues.apache.org/jira/browse/HIVE-22763 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Karen Coppage >Assignee: Karen Coppage >Priority: Minor > Fix For: 4.0.0 > > Attachments: HIVE-22763.01.patch, HIVE-22763.01.patch, > HIVE-22763.01.patch > > > Having a timestamp string in 12-hour format can be parsed if the hour is 0, > however, based on the [design > document|https://docs.google.com/document/d/1V7k6-lrPGW7_uhqM-FhKl3QsxwCRy69v2KIxPsGjc1k/edit], > it should be rejected. > h3. How to reproduce > Run {code}select cast("2020-01-01 0 am 00" as timestamp format "-mm-dd > hh12 p.m. ss"){code} > It shouldn' t be parsed, as the hour component is 0. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HIVE-22763) 0 is accepted in 12-hour format during timestamp cast
[ https://issues.apache.org/jira/browse/HIVE-22763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Coppage updated HIVE-22763: - Attachment: HIVE-22763.01.patch Status: Patch Available (was: Open) > 0 is accepted in 12-hour format during timestamp cast > - > > Key: HIVE-22763 > URL: https://issues.apache.org/jira/browse/HIVE-22763 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Karen Coppage >Assignee: Karen Coppage >Priority: Minor > Fix For: 4.0.0 > > Attachments: HIVE-22763.01.patch, HIVE-22763.01.patch > > > Having a timestamp string in 12-hour format can be parsed if the hour is 0, > however, based on the [design > document|https://docs.google.com/document/d/1V7k6-lrPGW7_uhqM-FhKl3QsxwCRy69v2KIxPsGjc1k/edit], > it should be rejected. > h3. How to reproduce > Run {code}select cast("2020-01-01 0 am 00" as timestamp format "-mm-dd > hh12 p.m. ss"){code} > It shouldn' t be parsed, as the hour component is 0. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HIVE-22763) 0 is accepted in 12-hour format during timestamp cast
[ https://issues.apache.org/jira/browse/HIVE-22763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Coppage updated HIVE-22763: - Status: Open (was: Patch Available) > 0 is accepted in 12-hour format during timestamp cast > - > > Key: HIVE-22763 > URL: https://issues.apache.org/jira/browse/HIVE-22763 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Karen Coppage >Assignee: Karen Coppage >Priority: Minor > Fix For: 4.0.0 > > Attachments: HIVE-22763.01.patch, HIVE-22763.01.patch > > > Having a timestamp string in 12-hour format can be parsed if the hour is 0, > however, based on the [design > document|https://docs.google.com/document/d/1V7k6-lrPGW7_uhqM-FhKl3QsxwCRy69v2KIxPsGjc1k/edit], > it should be rejected. > h3. How to reproduce > Run {code}select cast("2020-01-01 0 am 00" as timestamp format "-mm-dd > hh12 p.m. ss"){code} > It shouldn' t be parsed, as the hour component is 0. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HIVE-22763) 0 is accepted in 12-hour format during timestamp cast
[ https://issues.apache.org/jira/browse/HIVE-22763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Coppage updated HIVE-22763: - Status: Patch Available (was: Open) > 0 is accepted in 12-hour format during timestamp cast > - > > Key: HIVE-22763 > URL: https://issues.apache.org/jira/browse/HIVE-22763 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Karen Coppage >Assignee: Karen Coppage >Priority: Minor > Fix For: 4.0.0 > > Attachments: HIVE-22763.01.patch > > > Having a timestamp string in 12-hour format can be parsed if the hour is 0, > however, based on the [design > document|https://docs.google.com/document/d/1V7k6-lrPGW7_uhqM-FhKl3QsxwCRy69v2KIxPsGjc1k/edit], > it should be rejected. > h3. How to reproduce > Run {code}select cast("2020-01-01 0 am 00" as timestamp format "-mm-dd > hh12 p.m. ss"){code} > It shouldn' t be parsed, as the hour component is 0. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HIVE-22763) 0 is accepted in 12-hour format during timestamp cast
[ https://issues.apache.org/jira/browse/HIVE-22763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Coppage updated HIVE-22763: - Attachment: HIVE-22763.01.patch > 0 is accepted in 12-hour format during timestamp cast > - > > Key: HIVE-22763 > URL: https://issues.apache.org/jira/browse/HIVE-22763 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Karen Coppage >Assignee: Karen Coppage >Priority: Minor > Fix For: 4.0.0 > > Attachments: HIVE-22763.01.patch > > > Having a timestamp string in 12-hour format can be parsed if the hour is 0, > however, based on the [design > document|https://docs.google.com/document/d/1V7k6-lrPGW7_uhqM-FhKl3QsxwCRy69v2KIxPsGjc1k/edit], > it should be rejected. > h3. How to reproduce > Run {code}select cast("2020-01-01 0 am 00" as timestamp format "-mm-dd > hh12 p.m. ss"){code} > It shouldn' t be parsed, as the hour component is 0. -- This message was sent by Atlassian Jira (v8.3.4#803005)