Any reason why you are merging into Jothi's fork instead of main branch?

At first I didn't realize that you created two forks 🙂 But if that works for you - why not.

We cannot merge directly into Databricks fork because we need it to be stable. This feature is big and the code will not be usable until we're fully done. Therefore we had to work either on a dedicated feature branch, or on the fork (like in this case).

Why targeting jprakash-db/PECO-1706 instead of main? That's generally a good practice when doing chained PRs. This allows to see only relevant changes in diff. Once previous PR is merged - GitHub automatically updates the chained PR to target main branch