You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pinot.apache.org by "Jackie-Jiang (via GitHub)" <gi...@apache.org> on 2023/09/13 19:47:49 UTC

[GitHub] [pinot] Jackie-Jiang commented on issue #11570: Deprecate schema name field in table config

Jackie-Jiang commented on issue #11570:
URL: https://github.com/apache/pinot/issues/11570#issuecomment-1718223073

   I'd suggest enforcing it instead of trying to handle the bad config by copying and renaming underlying. If we do this transparently, it can actually cause confusion because user might find their uploaded schema disappear, or the modification not reflected. Also, it is adding management overhead.
   We can do an one time effort to move the existing schema, but for new tables, we simply disallow using different schema name. This way we can ensure a clean connection between table and schema


-- 
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