-
Notifications
You must be signed in to change notification settings - Fork 5.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
infoschema,planner: implement the CLUSTER_LOG memory table predicate push down #14018
Merged
Merged
Changes from 1 commit
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
74bd94b
implement the CLUSTER_LOG memory table predicate push down
lonng c6322db
change multiple pattern protocol
lonng c602fda
Update planner/core/memtable_predicate_extractor.go
lonng d508a1b
update sysutil
lonng 98be3ad
Merge remote-tracking branch 'origin/master' into cluster-log-push-down
lonng 02a3d27
fix CI
lonng a49f2cb
Merge remote-tracking branch 'origin/master' into cluster-log-push-down
lonng ad8d1b1
address comment
lonng 1395624
add some comments
lonng aae31ee
fix time fraction
lonng 022211d
Merge remote-tracking branch 'origin/master' into cluster-log-push-down
lonng f7df50c
Merge branch 'master' into cluster-log-push-down
crazycs520 00fe80b
address comment
lonng 6321029
Merge branch 'cluster-log-push-down' of github.com:lonng/tidb into cl…
lonng e993168
fix time range extraction
lonng f9d1d17
Merge branch 'master' into cluster-log-push-down
lonng 861b205
Merge branch 'master' into cluster-log-push-down
crazycs520 0047748
Merge branch 'master' into cluster-log-push-down
crazycs520 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
address comment
Signed-off-by: Lonng <heng@lonng.org>
- Loading branch information
commit 00fe80b9b9dde043a51111fcdc7f2ba9bbff1d61
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So you don't deal with (time > ... and time < ...) or (time > ... and time < ...)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, to simplify the implementation of the diagnostics service search log interface, it can just accept only one range of time (pick a group of the log files in the time range). So the filtering will be executed in TiDB via Selection executor.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally, we use the cluster level log search function to locate the problem usually only one range of time. So I think it's enough to cover this scenario.