Skip to main content
ecournarie
Silver ⭐️⭐️
February 26, 2024
Solved

In CDP 7.1.9 , UNBOUNDED FOLLOWING behaves like CURRENT ROW

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 ?

Screenshot 2024-02-06 at 12.20.58.png

If we change the PRECEEDING, it's ok

Screenshot 2024-02-06 at 12.21.31.png

Thanks in advance

Teens
TeensAnswer
Gold ⭐️
March 12, 2024

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

5 replies

VidyaSargur
Community Manager
Community Manager
February 26, 2024

@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.

Translate
Regards, Vidya Sargur, Community Manager Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button.
vaishaakb
Gold ⭐️⭐️⭐️
Gold ⭐️⭐️⭐️
March 8, 2024

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

Translate
ecournarie
Silver ⭐️⭐️
March 8, 2024

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

Translate
Teens
Gold ⭐️
TeensAnswer
Gold ⭐️
March 12, 2024

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

Translate
ecournarie
Silver ⭐️⭐️
March 13, 2024

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

Translate