Skip to content

Change exception code from LOGICAL_ERROR to BAD_ARGUMENTS when the name of remote table is empty.#12147

Merged
alexey-milovidov merged 2 commits intomasterfrom
fix-logical-error-table-function-remote
Jul 6, 2020
Merged

Change exception code from LOGICAL_ERROR to BAD_ARGUMENTS when the name of remote table is empty.#12147
alexey-milovidov merged 2 commits intomasterfrom
fix-logical-error-table-function-remote

Conversation

@alexey-milovidov
Copy link
Member

Changelog category (leave one):

  • Not for changelog (changelog entry is not required)

Not a bug. We ensure that logical errors should never happen.
This fixes #12146.

@blinkov blinkov added the pr-not-for-changelog This PR should not be mentioned in the changelog label Jul 5, 2020
@alexey-milovidov
Copy link
Member Author

Stress test: #12158

@alexey-milovidov alexey-milovidov merged commit 4ec787c into master Jul 6, 2020
@alexey-milovidov alexey-milovidov deleted the fix-logical-error-table-function-remote branch July 6, 2020 06:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr-not-for-changelog This PR should not be mentioned in the changelog

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Logical error: Both table name and UUID are empty.

2 participants