RocMarshal commented on PR #235:
URL: 
https://github.com/apache/flink-connector-aws/pull/235#issuecomment-3934321860

   Hi, @ferenc-csaky 
   
   I have tried to reorganize the origin of this issue.
   
   The relationship is as follows:
   First, some documentation was missing in the Flink main repository, so we 
initiated this PR to supplement the missing documentation. During the process, 
we discovered the issue that is currently being fixed in this PR.
   
   Why can this be considered a problem within a certain scope?
   In short, because it failed in CI.
   
   Why did this CI not fail in previous versions but only fail in the current 
version?
   Because the Flink main repository previously depended on flink-connector-aws 
version v5.0. In that version, this syntax error did not exist, so it did not 
cause the documentation build in the Flink main repository to fail. After the 
flink-connector-aws version was upgraded to v6.0, this syntax error was 
introduced, which led to the documentation build failure in the Flink main 
repository.
   
   
   Why did other references in the documentation that also use the ****/#.... 
format succeed?
   
   I briefly searched and summarized the cases where this format succeeded, as 
shown below:
   
   <img width="1932" height="1128" alt="image" 
src="https://github.com/user-attachments/assets/b8f2aaf4-56cf-45a9-a821-1de2dd1e1ec3";
 />
   
   The current encoding approach is not  correct as above.
   
   If the above conclusions are generally correct, perhaps we can try to fix 
the issue in the following way:
   
   <img width="2232" height="753" alt="b392646dc7619faecb1df75d8ea79284" 
src="https://github.com/user-attachments/assets/a32de338-cb36-466b-aebc-8ba2afd076ce";
 />
   
   
   Please correct me if I'm wrong. Thank you very much!


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