suxiaogang223 commented on code in PR #69343:
URL: https://github.com/apache/doris/pull/69343#discussion_r4346023410


##########
fe/fe-connector/fe-connector-paimon/src/main/java/org/apache/doris/connector/paimon/PaimonScanParams.java:
##########
@@ -127,11 +126,11 @@ public final class PaimonScanParams {
     private static final Set<String> PAIMON_READER_SYSTEM_TABLES = 
ImmutableSet.of(
             "audit_log", "binlog", "row_tracking");
 
-    // Not a capability the user selects but a property of where the snapshot 
is resolved: these five
+    // Not a capability the user selects but a property of where the snapshot 
is resolved: these tables
     // pick it inside the BE reader rather than reading what the FE planned. 
See
     // resolvesSnapshotOnBackend for the per-table call chain.
     private static final Set<String> BACKEND_SNAPSHOT_SYSTEM_TABLES = 
ImmutableSet.of(
-            "files", "partitions", "manifests", "statistics", "table_indexes");
+            "files", "file_indexes", "partitions", "manifests", "statistics", 
"table_indexes");

Review Comment:
   Fixed in 9337b7c16c0. The source serialized as 
`doris.serialized-system-source` now receives the catalog snapshot bound before 
its loader is removed. The FE test deserializes that actual scan-properties 
payload with snapshots 1 and 2 on disk while the catalog publishes 1, lowers 
the manifest cap and verifies only snapshot 1's index is read. An additional 
scanner test exercises real JNI reconstruction with pinned/unpinned controls (1 
versus 2 index files).
   
   Validation: FE Paimon 844 passed / 1 connectivity test skipped, Java scanner 
175 passed, native Paimon/JNI/Rust 144 passed, and 51 exercised Paimon cluster 
suites passed. System-table expected output was regenerated and replayed 
successfully.



-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to