Low Description
Currently, any triggers configured for a table are not executed during LWT operations. If we were to enable triggers support for conditional operations, we'd need to restrict the kinds of mutations that those triggers are permitted to generate. More specifically, we'd need to ensure that only mutations that apply to the same partition as the primary condition are allowed. If a configured trigger emits mutations for another partition, or a different table, then the whole operation should be aborted in the same way as we abort non-LWT updates when a trigger produces invalid mutations.