You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pinot.apache.org by "egalpin (via GitHub)" <gi...@apache.org> on 2023/02/08 01:04:56 UTC
[GitHub] [pinot] egalpin commented on pull request #10234: Add support for multiple comparison columns (i.e. one comparison column per producer sinking to a table)
egalpin commented on PR #10234:
URL: https://github.com/apache/pinot/pull/10234#issuecomment-1421728942
@Jackie-Jiang If we handle the case where there is a single comparisonColumn in a special way such that the column name is not stored on the RecordLocation, would we be able to support the case where a user wants to update to having many columns after previously having a single comparisonColumn? I guess when state is restored, when reading from the earliest record, the extra data of the column name would be captured at that point?
--
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