We store our database functions in SQL scripts that are automatically executed with every Flyway migration, so-called callback scripts.
In the callback script every function is declared to be created or recreated. As Flyway is executed with each application start, the database functions are recreated with every application start, even if they didn’t change.
This approach has its pros and cons but it ensures that database functions always match the version of the application code.
Because the callback script of a database function is stored in a file that is edited when needed, the Git history works the same as for application code.
Thanks for the illuminating post.
I like how Apache Airflow is used to move the pyspark script to a S3 location so that it can be read by the EMR step.
I remember working on a project where we wanted to automate a data pipeline using Airflow and had this problem of how to get our pipeline scripts to the right locations.
Is Chromium's behavior any different from Chrome's sync. behavior?
Years ago, I started using Chrome instead of Chromium or Firefox because they made Flash work out of the box on Linux.
Although Flash is not important for me anymore, I just never looked back.
With all this new strange Sync and Log-in behavior, I'll might change to a different browser.