lnbest0707-uber commented on issue #14815: URL: https://github.com/apache/pinot/issues/14815#issuecomment-3166652433
> `Actually, what I am thinking is sort of Async Pinot-Kafka consumer. We could have find another pinot-server backfilling threads pool to consume and seal [offset1, offset2), not necessarily a minion task, so that we can reuse the existing pinot-server code.` > > This already exists now. We have a way of re-ingesting. The controller can ask one of the servers to consume -> build -> upload the segment and push the metadata to the controller. > > [@lnbest0707-uber](https://github.com/lnbest0707-uber) are we using this ? Attached the design link (was attached to the PR but not here, added now) TLDR: I plan to introduce the interface for pluggable implementations. At the first stage, I implemented the Kafka Replication based solution. But the design is flexible to adapt other, e.g. reingest, based solution. -- 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]
