THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
The current connector implementor has no way of knowing that the last three fields were added by the planner and not from real user data. The user has to declare several different schemas (containing only partial column information and no overlap except for the primary key) to get around the current problem.
By adding targetColumnList target column list information to the DynamicTableSink#Context, this problem can be solved.
...
Add new getTargetColumns to DynamicTableSink#Context.
| Code Block | ||
|---|---|---|
| ||
/** * Returns an {@link Optional} array of column index paths related to user specified target * column list or an empty{@link Optional#empty()} when not specified. The array indices are 0-based and support * and *support composite columns within (possibly nested) structures. * * <p>This information comes from the column list of the DML clause, e.g., for a sink table * t1 which schema is: {@code a STRING, b ROW < b1 INT, b2 STRING>, c BIGINT} * * <ul> * <li>insert: 'insert into t1(a, b.b2) ...', the column list will be 'a, b.b2', and will * return {@code [[0], [1, 1]]}. The columnstatement list'insert willinto betarget empty for 'insert into targetselect ...' without * specifying a column list will select ...'.return {@link Optional#empty()}. * <li>update: 'update target set a=1, b.b1=2 where ...', the column list will be 'a, * b.b1', will return {@code [[0], [1, 0]]}. * </ul> * * <p>Note: will always return empty for the delete statement because it has no column list. */ Optional<int[][]> getTargetColumns(); |
...