Skip to content
This repository was archived by the owner on Mar 12, 2026. It is now read-only.

fix: directly return when found no table datas to replay#1062

Merged
Rachelint merged 1 commit into
apache:mainfrom
Rachelint:directly-return-when-found-nothing-repaly
Jul 11, 2023
Merged

fix: directly return when found no table datas to replay#1062
Rachelint merged 1 commit into
apache:mainfrom
Rachelint:directly-return-when-found-nothing-repaly

Conversation

@Rachelint

@Rachelint Rachelint commented Jul 11, 2023

Copy link
Copy Markdown
Contributor

Rationale

Now it will still scan logs from wal when no table datas needed to replay, it should directly return actually.

Detailed Changes

Add a fast path to return directly when no table datas needed to replay.

Test Plan

Test manually.

@Rachelint Rachelint force-pushed the directly-return-when-found-nothing-repaly branch from abbdbd8 to 41aa06c Compare July 11, 2023 06:03

@ShiKaiWi ShiKaiWi left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM

@Rachelint Rachelint merged commit 3dcf83b into apache:main Jul 11, 2023
Rachelint added a commit to Rachelint/ceresdb that referenced this pull request Jul 11, 2023
## Rationale
Now it will still scan logs from wal when no table datas needed to
replay, it should directly return actually.

## Detailed Changes
Add a fast path to return directly when no table datas needed to replay.

## Test Plan
Test manually.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants