tisonkun opened a new pull request, #20016:
URL: https://github.com/apache/pulsar/pull/20016

   This is a follow-up to https://github.com/apache/pulsar/pull/16683.
   
   And it fixes one of the breaking changes noted at 
https://github.com/apache/pulsar/pull/16494.
   
   The final goal should be catching up to the latest trino version. For 
compatibility, the Trino community says:
   
   > We generally do our best to avoid making breaking changes in SPI, but we 
still do them from time to time.
   >
   > There is a revapi test in SPI which provides compatibility guarantees one 
version back, but we sometimes have to do exclusions there to enable innovation.
   >
   > TL;DR is it’s recommended to build a plugin version for a specific Trino 
version
   
   So it seems the breaking changes and incompatibility is how Trino users 
should be familiar with.
   
   ### Does this pull request potentially affect one of the following parts:
   
   <!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. -->
   
   *If the box was checked, please highlight the changes*
   
   - [x] Dependencies (add or upgrade a dependency)
   - [ ] The public API
   - [ ] The schema
   - [ ] The default values of configurations
   - [ ] The threading model
   - [ ] The binary protocol
   - [ ] The REST endpoints
   - [ ] The admin CLI options
   - [ ] The metrics
   - [ ] Anything that affects deployment
   
   ### Documentation
   
   <!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. -->
   
   - [ ] `doc` <!-- Your PR contains doc changes. -->
   - [ ] `doc-required` <!-- Your PR changes impact docs and you will update 
later -->
   - [x] `doc-not-needed` <!-- Your PR changes do not impact docs -->
   - [ ] `doc-complete` <!-- Docs have been already added -->
   
   ### Matching PR in forked repository
   
   PR in forked repository: 


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