hey pinot friends, my team and i are looking into how to deploy our schema/table changes into the pinot cluster, we are doing this with version control in github and PRs, one thing that we were wondering is what can we do at the pr lvl to ensure that whatever change is not suppose to break pinot or the current table, are there any validation or dry runs that we can perform with the API that may help us in this regard? what has been your experience with this? thank you!
bumping this up in case anyone has any general thoughts
02/17/2022, 8:34 PM
there is a schema validation api that you can use
checking in the schema into a repo and having a script around that to validate, dry run etc is a great way to make sure that things dont break in production
other options are having dev staging and prod environments
and try out the changes in dev and staging before applying on prod