INNOCENT-BOY opened a new pull request, #10991: URL: https://github.com/apache/pinot/pull/10991
Even though we enable case-insensitive，we found one potential risk in some occasions. My two colleagues want to add one column to the same table in the same pinot environment. But theirs naming style is different. One person add name callType, other people add CallType, and they all succeed. Because we've already enabled case-insensitive option, so they us all could query from Controller UI and no one found potential risk. But one of client report an incident, they can't query from Trino, it will report Multi Entries error. In my opinion, after we enabled case insensitive, we should't allow user to add the same lowercase column with existed columns. Waiting for maintainer or reviewers to review! -- 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-unsubscr...@pinot.apache.org 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
