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
Follow up to the Github issue #5453, clean up the row_context without depending on rows_per_transaction query option.
The context should be reset and deleted based on shouldResetMemoryPerRow flag instead.
The text was updated successfully, but these errors were encountered:
…elation
Summary:
This fix is follow-up to https://phabricator.dev.yugabyte.com/D9313.
In `Copy From`, after all rows from file sourced input have been committed into YBRelation, memory context (`row_context`)
should be cleaned up on the following changed condition:
- without depending on `rows_per_transaction` query option
- must use boolean flag `shouldResetMemoryPerRow` to ensure it is YBRelation table type where its input sourced from file type (ie. not stdin).
`shouldResetMemoryPerRow` is the same flag that is used to verify whether memory context can be reset per row after being inserted into table.
Test Plan: build and reran tests
Reviewers: jason, alex
Reviewed By: jason, alex
Subscribers: yql
Differential Revision: https://phabricator.dev.yugabyte.com/D9342
Follow up to the Github issue #5453, clean up the
row_context
without depending onrows_per_transaction
query option.The context should be reset and deleted based on
shouldResetMemoryPerRow
flag instead.The text was updated successfully, but these errors were encountered: