fuweng11 commented on issue #8192:
URL: https://github.com/apache/inlong/issues/8192#issuecomment-1582345304

   > @fuweng11, I don't understand, the implementation[1] 
![image](https://user-images.githubusercontent.com/14038849/244355945-bf9eb2c2-d2a6-41b9-9c83-f52374f27c3c.png)
   > 
   > is actually directly migrated [2]: 
![image](https://user-images.githubusercontent.com/14038849/244356160-30bc0522-12dc-4766-9e32-456b94e22b78.png)
   > 
   > Is there a problem with the previous logic, then why is there no error 
reported?
   > 
   > 1. 
https://github.com/apache/inlong/blob/master/inlong-dataproxy/dataproxy-source/src/main/java/org/apache/inlong/dataproxy/config/holder/MetaConfigHolder.java#L375
   > 2. 
https://github.com/apache/inlong/blob/branch-1.7/inlong-dataproxy/dataproxy-source/src/main/java/org/apache/inlong/dataproxy/sink/mq/kafka/KafkaHandler.java#L150
   
   Yes, this problem was not discovered before because if 
`streamInfo.mqResource` is not set when the stream is created, the manager side 
will automatically set `streamId` to `streamInfo.mqResource`, and in most cases 
`streamId` and streamInfo.mqResource` are the same.


-- 
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: commits-unsubscr...@inlong.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to