Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

In CDP 7.1.9 , UNBOUNDED FOLLOWING behaves like CURRENT ROW

avatar
New Contributor

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

1 ACCEPTED SOLUTION

avatar
New Contributor

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

View solution in original post

5 REPLIES 5

avatar
Community Manager

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



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.
Learn more about the Cloudera Community:

avatar
Master Collaborator

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

avatar
New Contributor

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

avatar
Contributor

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

avatar
New Contributor

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