Fix behavior of estimateTableSize #845
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
marsishandsome
approved these changes
Jun 20, 2019
|
/run-all-tests |
marsishandsome
pushed a commit
that referenced
this pull request
Jun 20, 2019
|
already merged. |
birdstorm
added a commit
that referenced
this pull request
Jun 26, 2019
zhexuany
pushed a commit
to zhexuany/tispark
that referenced
this pull request
Oct 15, 2019
marsishandsome
pushed a commit
that referenced
this pull request
Oct 15, 2019
wfxxh
pushed a commit
to wanfangdata/tispark
that referenced
this pull request
Jun 30, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Close #844
When estimated count is 0, it is possible that statistics information is not read correctly. Just set its estimate count to
Long.Maxsince we do not want to broadcast this table.