[ 
https://issues.apache.org/jira/browse/HIVE-23868?focusedWorklogId=460000&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-460000
 ]

ASF GitHub Bot logged work on HIVE-23868:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 16/Jul/20 23:25
            Start Date: 16/Jul/20 23:25
    Worklog Time Spent: 10m 
      Work Description: jdere opened a new pull request #1269:
URL: https://github.com/apache/hive/pull/1269


   Change-Id: I2db8c379cf916b680e226b4a6e77832fb1e2317f
   
   ## NOTICE
   
   Please create an issue in ASF JIRA before opening a pull request,
   and you need to set the title of the pull request which starts with
   the corresponding JIRA issue number. (e.g. HIVE-XXXXX: Fix a typo in YYY)
   For more details, please see 
https://cwiki.apache.org/confluence/display/Hive/HowToContribute
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

            Worklog Id:     (was: 460000)
    Remaining Estimate: 0h
            Time Spent: 10m

> Windowing function spec: support 0 preceeding/following
> -------------------------------------------------------
>
>                 Key: HIVE-23868
>                 URL: https://issues.apache.org/jira/browse/HIVE-23868
>             Project: Hive
>          Issue Type: Bug
>          Components: Query Planning
>            Reporter: Jason Dere
>            Assignee: Jason Dere
>            Priority: Major
>         Attachments: HIVE-23868.1.patch
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> HIVE-12574 removed support for 0 PRECEDING/FOLLOWING in window function 
> specifications. We can restore support for this by converting 0 
> PRECEDING/FOLLOWING to CURRENT ROW in the query plan, which should be the 
> same.



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

Reply via email to