You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pinot.apache.org by GitBox <gi...@apache.org> on 2022/09/09 18:19:47 UTC
[GitHub] [pinot] vvivekiyer opened a new issue, #9360: Update deepstore segments with schema/tableConfig changes
vvivekiyer opened a new issue, #9360:
URL: https://github.com/apache/pinot/issues/9360
Currently, we support a number of preprocessing operations for a segment in response to schema/tableConfig changes. Some of them are:
1. Add a new column. Remove/Modify an autogenerated column.
2. Add a new index, remove an index.
Every time the server downloads and reloads a segment, the server preprocesses the segment and applies these changes. However, the segment directory in the deep store is never modified to reflect these schema changes. As we keep piling more segment preprocessing logic in reload path, time taken to reload a segment could increase if the user has a number of schema/tableConfig changes applied.
The suggestion here is to also update the segment in deep store to reflect these changes. This can be done with a background minion task.
--
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-unsubscribe@pinot.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For additional commands, e-mail: commits-help@pinot.apache.org
[GitHub] [pinot] Jackie-Jiang commented on issue #9360: Update deepstore segments with schema/tableConfig changes
Posted by GitBox <gi...@apache.org>.
Jackie-Jiang commented on issue #9360:
URL: https://github.com/apache/pinot/issues/9360#issuecomment-1242463523
We already have an API to ask server to upload the segment to deep store. We may leverage the same mechanism to refresh the segments in the deep store. Currently it is used to fix the realtime segments that do not have the deep store copy. See `PinotLLCRealtimeSegmentManager.uploadToDeepStoreIfMissing()` for more details
--
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-unsubscribe@pinot.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For additional commands, e-mail: commits-help@pinot.apache.org