subourbonite edited a comment on issue #6517: URL: https://github.com/apache/incubator-pinot/issues/6517#issuecomment-771281912
I actually think that having the same column name spread around multiple systems with a different grain / format / definition can become a serious data usability problem over time - especially if queries expecting the original grain or format still run successfully against the 'new' format, but return different (or unexpected) results. I always try to adhere to the principle of least surprise when designing data models for consumption. Does it make sense to possibly make a column replacement fail by default, and require an explicit override to enable? ---------------------------------------------------------------- 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: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For additional commands, e-mail: commits-h...@pinot.apache.org
