Currently a DB sink requires all columns of the target DB table to be posted to the DB sink. This implies that SESAM has the correct values for all the columns. It is not uncommon that SESAM has correct values only for a subset of target DB table columns. In this case SESAM updates other columns to null even if the schema definition contains a subset of columns.
One could argue that reading in the target table would solve the problem but this is an impractical solution.
Hence, SESAM should support updating subset of target DB table columns.
Please sign in to leave a comment.