[jira] [Updated] (HIVE-10140) Window boundary is not compared correctly
[ https://issues.apache.org/jira/browse/HIVE-10140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-10140: Affects Version/s: 1.1.0 1.2.0 0.13.0 0.14.0 Window boundary is not compared correctly - Key: HIVE-10140 URL: https://issues.apache.org/jira/browse/HIVE-10140 Project: Hive Issue Type: Bug Components: PTF-Windowing Affects Versions: 0.13.0, 0.14.0, 1.0.0, 1.2.0, 1.1.0 Reporter: Yi Zhang Assignee: Aihua Xu Priority: Minor Fix For: 1.3.0 Attachments: HIVE-10140.patch “ROWS between 10 preceding and 2 preceding” is not handled correctly. Underlying error: Window range invalid, start boundary is greater than end boundary: window(start=range(10 PRECEDING), end=range(2 PRECEDING)) If I change it to “2 preceding and 10 preceding”, the syntax works but the results are 0 of course. Reason for the function: during analysis, it is sometimes desired to design the window to filter the most recent events, in the case of the events' responses are not available yet. There is a workaround for this, but it is better/more proper to fix the bug. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-10140) Window boundary is not compared correctly
[ https://issues.apache.org/jira/browse/HIVE-10140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aihua Xu updated HIVE-10140: Attachment: HIVE-10140.patch Window boundary is not compared correctly - Key: HIVE-10140 URL: https://issues.apache.org/jira/browse/HIVE-10140 Project: Hive Issue Type: Bug Components: PTF-Windowing Affects Versions: 1.0.0 Reporter: Yi Zhang Assignee: Aihua Xu Priority: Minor Attachments: HIVE-10140.patch “ROWS between 10 preceding and 2 preceding” is not handled correctly. Underlying error: Window range invalid, start boundary is greater than end boundary: window(start=range(10 PRECEDING), end=range(2 PRECEDING)) If I change it to “2 preceding and 10 preceding”, the syntax works but the results are 0 of course. Reason for the function: during analysis, it is sometimes desired to design the window to filter the most recent events, in the case of the events' responses are not available yet. There is a workaround for this, but it is better/more proper to fix the bug. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
