xinzhuxiansheng opened a new issue, #28742:
URL: https://github.com/apache/doris/issues/28742

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/doris/issues?q=is%3Aissue) and found no 
similar issues.
   
   
   ### Description
   
   Based on the documentation available at 
https://doris.apache.org/zh-CN/docs/ecosystem/flink-doris-connector/
   
   The document initially states:
   "The current deletion is to support Flink CDC to access data to achieve 
automatic deletion. If it is to delete other data access methods, you need to 
implement it yourself. For the data deletion usage of Flink CDC, please refer 
to the last section of this document."
   
   However, the last section of the document introduces "Use Flink to delete 
data based on specified columns."
   
   There appears to be some conflict in these statements. For instance, when 
the data in a Kafka Topic is:
   ```json
   {"PRD_CODE":"1","PRD_NAME":"测试数据","op_type":"D"}
   ```
   
   And I execute the SQL:
   ```
   INSERT INTO doris_sink 
   SELECT *,
   if(op_type='D',1,0) as __DORIS_DELETE_SIGN__ 
   FROM kafka_source;
   ```
   
   This also results in deletion, even though the data structure in the Kafka 
topic is not the CDC data structure. 
   
   
   ### Solution
   
   I think that the documentation could be amended for clarity, such as:
   The current deletion support includes the following methods:
   1. Support Flink CDC to access data to achieve automatic deletion.
   2. Use Flink to delete data based on specified columns.
   If it is to delete data using other access methods, it needs to be 
implemented by the user.
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to