Issue with MERGE INTO on Databricks

[jbc]

Hello, we're still seeing the error discussed here ("A ResultSet was expected but not generated" with MERGE INTO queries..)
Is it possible this issue was re-introduced?

Issue with Writing to Databricks

I'm getting error message when writing into DataBricks table using merge statement from retool. The table gets updated successfully, however the error message ("A ResultSet was expected but not generated from query") creates confusion for the end users. I tried masking the error message as "success notification" under failure event handler. My goal is to update databricks table based on the values from temporary state variables. Is there a better way to update multiple records in a Databricks t…

[retool_team]

The issue may have been reintroduced. I have sent the issue over to our team to see what is going on here!

[Harry_Doan]

@jbc Thank you for reporting! The MERGE INTO queries don't usually return any result. Even though it shows the error "A ResultSet was expected but not generated from query", the query should succeed. I've filed a task for the team to improve the UX around this error, meanwhile you can continue using the query!

[malcantara]

I am having that issue myself. How can I get around that?

[malcantara]

Hello Harry. Are there any updates on this?

[Harry_Doan]

@malcantara sorry, my team hasn't had time to look into this yet. Just to reiterate the message above: it is a display error, the query should still succeed. Instead of relying on the error, you can fix the data again to confirm it has been updated. This is required because MERGE INTO doesn't return any result.