Skip to content

Conversation

@vagetablechicken
Copy link
Collaborator

Closes #689

@github-actions
Copy link
Contributor

github-actions bot commented Nov 16, 2021

Linux Test Report

       58 files       175 suites   37m 5s ⏱️
12 860 tests 12 860 ✔️ 0 💤 0
12 866 runs  12 866 ✔️ 0 💤 0

Results for commit 277f1bb.

♻️ This comment has been updated with latest results.

logger.error("executeSQL fail: {}", status.getMsg());
}
status.delete();
status = null;
Copy link
Collaborator

@jingchen2222 jingchen2222 Nov 16, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dl239 Why didi we use status = null after status.delete()? Did you try to deal with memory leaking?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have not tested whether it has impact on memory release if it is not set to null. In theory, it does not need to be set to null because status.delete() can release the memory alloced in C++.

@dl239 dl239 merged commit a64235b into 4paradigm:main Nov 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support obtain output schema from ExecuteDDLParse

4 participants