By default, conflicts are resolved at row level. When changes from two nodes conflict, either the local or remote tuple is selected and the other is discarded. For example, commit timestamps for the two conflicting changes might be compared and the newer one kept. This approach ensures that all nodes converge to the same result and establishes commit-order-like semantics on the whole cluster.
However, it might sometimes be appropriate to resolve conflicts at the column level rather than the row level, at least in some cases.
When to resolve at the column level
Consider a simple example in which table t has two integer columns, a and b, and a single row (1,1). On one node execute: