In CDP 7.1.9 , UNBOUNDED FOLLOWING behaves like CURRENT ROW

[#1]

Hi everybody,

Testing CDP 7.1.9, looks like we hit a bug in Hive . The "UNBOUNDED FOLLOWING" actually behaves as "CURENT ROW". But only when the other side of the window is "UNBOUNDED PRECEEDING". Did someone hit this one ?

If we change the PRECEEDING, it's ok

Thanks in advance

[#2 · Accepted solution]

Thanks @vaishaakb for giving me the opportunity to help @ecournarie 

Hello @ecournarie , I did review the fore-mentioned situation, upon checking this seems to be a known issue as per https://issues.apache.org/jira/browse/HIVE-24905 and we have the below workaround,

Can you try disabling vectorization at session level via Beeline and test?
set hive.vectorized.execution.reduce.enabled=false

Thanks,
Tee

[#3]

@ecournarie, Welcome to our community! To help you get the best possible answer, I have tagged in our CDP experts @vaishaakb @rki_  who may be able to assist you further.

Please feel free to provide any additional information or details about your query, and we hope that you will find a satisfactory solution to your question.

[#4]

@ecournarie @VidyaSargur Tagging our Hive expertise @Teens Please help here

[#5]

Omit to say, but it was working for 7.1.7 , so that's may be a regression...

[#6 · Accepted solution]

Thanks @vaishaakb for giving me the opportunity to help @ecournarie 

Hello @ecournarie , I did review the fore-mentioned situation, upon checking this seems to be a known issue as per https://issues.apache.org/jira/browse/HIVE-24905 and we have the below workaround,

Can you try disabling vectorization at session level via Beeline and test?
set hive.vectorized.execution.reduce.enabled=false

Thanks,
Tee

[#7 · Accepted solution]

Hi Tee,,

Thanks for taking care. Indeed, the workaround is working, results are correct when disabling  vectorization.

This bug looks pretty old, guess not a lot of hope to see it fixed somedays....

Thanks again for your help

Eric