ianvkoeppe edited a comment on pull request #5745: URL: https://github.com/apache/incubator-pinot/pull/5745#issuecomment-663328375
> There's also a new api being added in the controller that makes it a protocol. Perhaps you could piggy-back on it to update time-boundary? @snleee What do you think? > #5712 Subbu mentioned this functionality might be possible via the controller in the future. I have just a couple concerns with that approach. 1) We are planning to build a reporting pipeline within an execution environment where we may not have the flexibility or control to configure jobs which call the controller. Pinot segment creation, upload, etc. is all abstracted away. 2) Managing the time boundary ourselves might be error prone since it means we have to have custom code to track our latest successful job runs and update the time boundary correctly afterwards. I'm worried about maintaining a custom job step that could potentially update the time boundary incorrectly, or having to think about how we'd rollback an update if we wanted to delete a badly pushed segment. I'm interested to hear your thoughts on these. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For additional commands, e-mail: commits-h...@pinot.apache.org
