xiangfu0 opened a new pull request, #20034:
URL: https://github.com/apache/pinot/pull/20034

   ## What
   End-to-end and mixed-version coverage for VARIANT, plus a packaged Parquet 
VARIANT batch quickstart.
   
   ## Changes
   - `VariantTypeTest`: integration test over a real cluster for both engines.
   - Compatibility verifier: `runIfSystemProperty` gating for ops, a 
`fileContainsOp` that asserts log contents, and an 
`expectedErrorMessageContains` check for query ops. New VARIANT wire suites 
(`variant-wire`, `variant-wire-mixed`, `routing-ready`) plus an 
old-broker/new-servers scenario cover the rolling-upgrade contract from 6/8.
   - `VariantQuickStart` (`quick-start-variant-batch`) with a sample Parquet 
file, schema, table config and README, plus a CI step in the quickstart 
workflow script.
   
   ## Depends on
   7/8. This is the top of the stack; its tree equals #19101's head.
   
   ## About this PR
   This is **part 8 of 8** splitting #19101 (end-to-end Parquet VARIANT 
support) into layered PRs. #19101 stays open as the umbrella with the full 
feature description; 
[`docs/design/VARIANT.md`](https://github.com/apache/pinot/blob/xiangfu0/variant-split/01-spi-foundation/docs/design/VARIANT.md)
 (added in 1/8) is the design reference.
   
   The base branch is the previous PR in the stack, so the diff below is 
exactly this layer. Each layer compiles and passes its own tests on top of the 
one below it, and the top of the stack has the same tree as #19101.
   
   > VARIANT is not usable end to end until the whole stack has landed. 
Raw-value opacity guards arrive in 5/8 (single-stage) and 6/8 (multi-stage), so 
please don't create VARIANT columns on a build that has only part of the stack. 
The stack should land within one release.
   
   ### Full stack (merge bottom → top)
   _filled in once all PRs are open_
   


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