JingsongLi opened a new pull request, #8602:
URL: https://github.com/apache/paimon/pull/8602

   ## Purpose
   
   Wire source-backed BTree and Bitmap indexes into the primary-key table write 
lifecycle.
   
   ## Changes
   
   - Create a unified bucket-local coordinator for vector, BTree, and Bitmap 
primary-key index definitions.
   - Restore source-backed payloads and construct sorted-index builders from 
the table schema, bucket path, reader factory, and shared `IOManager`.
   - Run multiple scalar index definitions sequentially while allowing a failed 
definition to remain uncovered without suppressing other definitions.
   - Publish index additions and deletions through the append or compact 
increment that owns the corresponding source-file transition.
   - Enable the file-store writer whenever BTree or Bitmap primary-key index 
columns are configured.
   - Keep source-backed payloads out of the ordinary global row-id scanner and 
coverage calculation, so both index models can coexist safely.
   - Keep Postpone Bucket writes unindexed in bucket `-2`; the fixed-bucket 
runtime view used by background compaction creates and publishes the 
coordinator.
   
   ## Impact
   
   Compacted primary-key table files now automatically receive configured BTree 
and Bitmap payloads. Read-side source pruning remains intentionally deferred to 
a follow-up PR.
   
   ## Validation
   
   - `mvn -pl paimon-codegen-loader -am -Pfast-build -DskipTests package`
   - `mvn -pl paimon-core -am -Pfast-build -DfailIfNoTests=false 
-DwildcardSuites=none 
-Dtest=BucketedPrimaryKeyIndexMaintainerTest,PrimaryKeySortedIndexMaintenanceTest,PrimaryKeyIndexWriteTest,PrimaryKeyVectorIndexWriteTest,BtreeGlobalIndexTableTest
 test` (20 tests)
   - `mvn -pl paimon-core -DskipTests validate`
   


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

Reply via email to