Skip to content
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

fix file stream time scanning metrics bug #5019

Closed
xiaoyong-z opened this issue Jan 21, 2023 · 0 comments · Fixed by #5020
Closed

fix file stream time scanning metrics bug #5019

xiaoyong-z opened this issue Jan 21, 2023 · 0 comments · Fixed by #5020
Labels
bug Something isn't working

Comments

@xiaoyong-z
Copy link
Contributor

Describe the bug
A clear and concise description of what the bug is.
currently, file stream time scanning will be 'start()' only once, and may be 'stop()' many times. After the first calling to 'stop()', the self.start value of time scanning will be replaced to default value by 'take()'. The subsequent calling to 'stop()' make no sense.
To Reproduce
Steps to reproduce the behavior:
explain analyze select * from table;
Expected behavior
A clear and concise description of what you expected to happen.

Additional context
Add any other context about the problem here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant