In an event-driven application, there is generally a main loop that listens for events, and then triggers a callback function when one of those events is detected.
Nice fishing on the Vertica binary ( you probably use the strings command method ) .
In big data platform the benefit of triggers is significant can be problematic , it will lead to record level validation and will kill your load process , as I see it , in big data platform , set base processing should be your favorite method for triggering changes ( One of the options can be staging area + merge command ) . Despite that still I may see some use cases that triggers can be helpful (mainly for dimensions data) .
it is a debuging aid, currently used in-house by people who have access to Vertica tools and can modify our source code.
We're not secretly hiding them;