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

   PR 1 of a 2-PR split.  This change introduces the view-creation and 
materialization pipeline; broker-side query rewrite ships in PR 2.
   
   **Scope of PR 1:**
   - MV table definition (analyzer, time-expression validator, ZK metadata)
   - Per-partition runtime metadata (PartitionInfo, PartitionState, 
PartitionFingerprint) and storage utilities
   - Controller-side consistency manager (subscribes to base-table segment 
events; debounces and CAS-marks affected MV partitions STALE)
   - Controller integration (PinotHelixResourceManager / SegmentDeletionManager 
notify methods; BaseControllerStarter wires the manager before listeners fire)
   - Minion task pipeline (generator + executor + segment lineage replace, 
saturation-LIMIT gate, partition-fingerprint CAS write to runtime znode)
   - AggregationEquivalenceRegistry (used by analyzer at create time; also 
consumed by PR 2's rewrite strategies)
   - pinot-materialized-view module: analysis/, consistency/, metadata/, 
scheduler/, executor/, rewrite/equivalence/, context/
   - Constants moved from MinionConstants.MaterializedViewTask to 
CommonConstants.MaterializedViewTask (pinot-spi)
   - Quickstart: airlineStatsMv example (TIMESTAMP MV column derived from base 
via DaysSinceEpoch * 86400000)
   
   **Out of scope (deferred to PR 2):**
   - Broker query rewrite engine + subsumption strategies
   - Broker metadata cache + handler + split dispatcher
   - BrokerResponse.materializedViewQueried response annotation
   - BaseSingleStageBrokerRequestHandler MV integration
   


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