MisterRaindrop opened a new issue, #2013:
URL: https://github.com/apache/cloudberry/issues/2013

   Part of #2008. Letters (A, B0–B7, C, D, E) are the PRs listed there; this is 
**B3**.
   
   ### Scope
   The kernel behind B1, with no catalog service yet: every operation takes a 
`metadata_location`. This is what the Builtin catalog (B4) needs and what every 
catalog provider (B5–B7) builds on.
   - Through iceberg-java: initial metadata for a new table at a location; 
load, statistics, the schema changes the AM allows, truncate.
   - Planning: a snapshot's data files, delete files and row-group ranges 
streamed as fragments; file groups for rewrite.
   - Staging: append and update per statement, producing a new uncommitted 
metadata file whose location the caller commits (B4 locally, B5–B7 through the 
catalog).
   - An `operation_id` claim store so a retried request applies once.
   - Storage from the request: `ResolvingFileIO` with `S3FileIO` for `s3://`.
   - iceberg-java moves from the 1.3 line the port started on to a current 1.x.
   - In-process unit tests per RPC; end-to-end against MinIO alone.
   
   ### Out of scope
   Catalog providers (B5–B7); compaction and snapshot expiry; data-file I/O 
(the agent never touches data files).
   
   ### Depends on
   B1; verified through B2.
   
   ### Acceptance
   - Create, load, plan and stage against MinIO alone, driven by the B2 
conformance suite.
   - A staged append retried with the same `operation_id` yields one metadata 
file.
   - Credentials never appear in agent logs; agent memory is flat over ten 
thousand plan calls.
   


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