Prajwal-banakar opened a new pull request, #2373:
URL: https://github.com/apache/fluss/pull/2373
<!--
*Thank you very much for contributing to Fluss - we are happy that you want
to help us improve Fluss. To help the community review your contribution in the
best possible way, please go through the checklist below, which will get the
contribution into a shape in which it can be best reviewed.*
## Contribution Checklist
- Make sure that the pull request corresponds to a [GitHub
issue](https://github.com/apache/fluss/issues). Exceptions are made for typos
in JavaDoc or documentation files, which need no issue.
- Name the pull request in the format "[component] Title of the pull
request", where *[component]* should be replaced by the name of the component
being changed. Typically, this corresponds to the component label assigned to
the issue (e.g., [kv], [log], [client], [flink]). Skip *[component]* if you are
unsure about which is the best component.
- Fill out the template below to describe the changes contributed by the
pull request. That will give reviewers the context they need to do the review.
- Make sure that the change passes the automated tests, i.e., `mvn clean
verify` passes.
- Each pull request should address only one issue, not mix up code from
multiple issues.
**(The sections below can be removed for hotfixes or typos)**
-->
### Purpose
<!-- Linking this pull request to the issue -->
Linked issue: close #2301
<!-- What is the purpose of the change -->
The purpose of this change is to fix a bug where the LogScanner enters an
infinite retry loop when a table is dropped during an active scan. Instead of
logging "unknown table or bucket" warnings indefinitely, the scanner now
correctly identifies the dropped table via a metadata refresh and terminates
with a TableNotExistException
### Brief change log
Metadata Management: Updated MetadataUtils.java to properly handle cache
eviction of dropped tables during metadata updates.
Log Fetcher Logic: Modified LogFetcher.java to catch fetch errors and
trigger a metadata refresh to verify if the table still exists.
Exception Handling: Implemented logic to throw TableNotExistException (or
handle the wrapped FlussRuntimeException) to break the fetcher's retry loop
when a table is confirmed as deleted.
<!-- Please describe the changes made in this pull request and explain how
they address the issue -->
### Tests
<!-- List UT and IT cases to verify this change -->
Verified the fix with the following tests in the fluss-client module:
New Integration Test: Added testDropTableWhileScanning in
LogScannerITCase.java which simulates a table drop during a scan and asserts
that the scanner fails gracefully.
Full Module Verification: Ran ./mvnw test -pl fluss-client -o to ensure no
regressions were introduced across the 124 existing client tests.
### API and Format
<!-- Does this change affect API or storage format -->
This change does not affect the external public API of Fluss.
This change does not affect the storage format.
### Documentation
<!-- Does this change introduce a new feature -->
This change does not introduce a new feature and does not require a
documentation update.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
