lrao-stripe opened a new issue, #11211: URL: https://github.com/apache/pinot/issues/11211
We ran into an issue on one of our tables to the following misconfiguration: - Table config had upload to deep store option set - Streaming servers did not have the segment s3 uri configuration set This resulted in failures to upload the segments to the deep store. However, the failures only manifested during/after segment commit time. It'd be great to have a way to fail faster when there's a misconfiguration possibly: - By adding a check when the consuming segment is created and checking if the s3 uri property is configured - By attempting to do this as a table level validation (this is potentially harder given that tableConfig + server config both need to be matched) -- 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: commits-unsubscr...@pinot.apache.org.apache.org 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
