You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the output of the first query? When you say the output of the second one is EOF you mean the client crashes and EOF gets printed (just those three chars) and the client exists? What do you get when you run the query in beeline?
What is the output of the first query? When you say the output of the second one is EOF you mean the client crashes and EOF gets printed (just those three chars) and the client exists?
Correct. The client exits and the error message EOF is printed (because i let the error object bubble out to my cli).
What do you get when you run the query in beeline?
Not sure... I've never used beeline. But also, i had to refactor my query to make better use of partition pruning and smaller extract sizes to move forward so increasing memory is no longer a blocker for me. You can close this issue if you want, but still would be good to know if using SET statements is not-supported by this driver, or if maybe i was doing it wrong (the later is not at all unlikely).
I have a query that is failing due to memory kill of the form:
However, when i try to increase memory:
The client simply exits with
EOF
being the error. Running the same query on ambari works.The text was updated successfully, but these errors were encountered: