jiangxt2 opened a new pull request, #13428:
URL: https://github.com/apache/gravitino/pull/13428

   ### What changes were proposed in this pull request?
   
   - Add Doris JDBC catalog support for creating and loading DATE/DATETIME AUTO 
RANGE tables partitioned by `date_trunc`. Gravitino-created tables use an empty 
origin-partition list; loading native tables with origin partitions remains 
supported.
   - Read the partition expression from `SHOW CREATE TABLE` and physical range 
bounds from `SHOW PARTITIONS`.
   - Support list/get access to physical partitions and delegate supported 
add/drop operations to Doris.
   - Preserve existing manual RANGE/LIST behavior and add unit and Doris 
integration coverage.
   
   ### Why are the changes needed?
   
   Doris can create date-based range partitions as data arrives, but the Doris 
JDBC catalog currently cannot preserve or create the `date_trunc` AUTO RANGE 
definition through Gravitino. This prevents clients from using Gravitino to 
create, load, and operate on these tables.
   
   Fix: #13424
   
   ### Does this PR introduce _any_ user-facing change?
   
   Yes. Gravitino clients can create and load Doris AUTO RANGE tables using 
`date_trunc` and access their physical partitions through the existing 
partition API. No public API changes are introduced.
   
   ### How was this patch tested?
   
   - `./gradlew :catalogs:catalog-jdbc-doris:test -PskipITs`: passed.
   - Focused AUTO RANGE integration coverage on Doris 3.0.6.2 
(`CatalogDoris3xIT`): passed.
   - Focused AUTO RANGE integration coverage on Doris 4.0.6 
(`CatalogDoris4xIT`), including native origin-partition round-trip and add 
behavior: passed.
   - Complete Doris 1.2 `CatalogDorisIT`: 23 tests passed, including native 
rejection of AUTO RANGE DDL.
   - `spotlessApply` and `git diff --check`: passed.
   


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