Xiezhibin opened a new issue, #5696:
URL: https://github.com/apache/paimon/issues/5696

   ### Search before asking
   
   - [x] I searched in the [issues](https://github.com/apache/paimon/issues) 
and found nothing similar.
   
   
   ### Motivation
   
   In the context of the Apache Paimon documentation, particularly in the 
section [Partial 
Update](https://paimon.apache.org/docs/master/primary-key-table/merge-engine/partial-update/)
 discussing "Sequence Group" and "Aggregation For Partial Update", it has come 
to our attention that there are inaccuracies regarding the representation of 
update fields and sequence-group fields.
   
   See the example. There are issues with the remarks that "g_2 should not be 
updated" and "g_1, g_3 should not be updated."
   
   - Both g_2 and g_1, g_3 are sequence-group fields, so it should specify 
whether a and c will be updated.
   - The judgment on the updates is incorrect; the fields a corresponding to 
g_1 and g_3 were updated.
   
   ```
   CREATE TABLE AGG
   (
       k   INT,
       a   INT,
       b   INT,
       g_1 INT,
       c   VARCHAR,
       g_2 INT,
       g_3 INT,
       PRIMARY KEY (k) NOT ENFORCED
   ) WITH (
         'merge-engine' = 'partial-update',
         'fields.a.aggregate-function' = 'sum',
         'fields.g_1,g_3.sequence-group' = 'a',
         'fields.g_2.sequence-group' = 'c');
   -- a in sequence-group g_1, g_3 with sum agg
   -- b not in sequence-group
   -- c in sequence-group g_2 without agg
   
   INSERT INTO AGG
   VALUES (1, 1, 1, 1, '1', 1, 1);
   
   -- g_2 should not be updated
   INSERT INTO AGG
   VALUES (1, 2, 2, 2, '2', CAST(NULL AS INT), 2);
   
   SELECT *
   FROM AGG;
   -- output 1, 3, 2, 2, "1", 1, 2
   
   -- g_1, g_3 should not be updated
   INSERT INTO AGG
   VALUES (1, 3, 3, 2, '3', 3, 1);
   
   SELECT *
   FROM AGG;
   -- output 1, 6, 3, 2, "3", 3, 2
   ```
   
   ### Solution
   
   _No response_
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [ ] I'm willing to submit a PR!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to