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 2019/12/10 22:19:14 UTC
[GitHub] [incubator-pinot] haibow commented on issue #4838: [WIP] Update
schema API to reload table on schema change when applicable
haibow commented on issue #4838: [WIP] Update schema API to reload table on schema change when applicable
URL: https://github.com/apache/incubator-pinot/pull/4838#issuecomment-564285464
> OK, so we all agree that this commit can hold off until the reload is implemented for CONSUMING segments?
I don't think this should be blocked by implementing reload for CONSUMING segments (I will prepare a diff after #4774 is merged). This diff just provides an option to merge two existing endpoints to one for easier operation, and doesn't change the default behavior. In fact without this auto-reload option in schema update endpoint, some users might not even know they need to reload the table for the new schema to be effective on committed segments.
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For additional commands, e-mail: commits-help@pinot.apache.org