hhhizzz opened a new pull request, #125:
URL: https://github.com/apache/paimon-trino/pull/125

   ## Summary
   
   Bump the connector to Trino 481 and Paimon 1.4.1.
   
   This also updates the connector code for Trino 481 SPI changes and Paimon 
1.4.1 API changes, and fixes packaging/runtime compatibility issues found while 
testing Paimon table queries with Trino 481.
   
   ## Changes
   
   - Upgrade Paimon dependencies to `1.4.1`.
   - Adapt to Trino 481 connector SPI changes:
     - return `SourcePage` from page sources
     - implement connector shutdown hook
     - update `NodeVersion` and filesystem module wiring
     - adjust API usage affected by Trino 481 signature changes
   - Adapt catalog and row handling for Paimon 1.4.1 APIs.
   - Normalize Paimon table option property names to lower case before passing 
them to Paimon, fixing options such as `variant.shreddingSchema`.
   - Update plugin packaging:
     - copy Trino HDFS dependencies as jars for Trino 481
     - include required Hive compatibility jars used by metastore/catalog paths
   - Add focused tests for:
     - Trino 481 page source compatibility
     - Paimon table option normalization
   - Do not include repo-local Maven settings under `.mvn`.
   
   ## Testing
   
   ```bash
   mvn -Dtrino.version=481 -Dtest=TrinoPageSourceTest,TrinoTableOptionUtilsTest 
test
   ```
   
   Result:
   
   ```text
   Tests run: 3, Failures: 0, Errors: 0, Skipped: 0
   BUILD SUCCESS
   ```
   
   ```bash
   mvn -Dtrino.version=481 -DskipTests package
   ```
   
   Result:
   
   ```text
   BUILD SUCCESS
   ```
   
   Also validated the built plugin with Trino 481 against existing Paimon 
tables using count, grouped aggregation, CTE/join, window function, and 
self-join queries.


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