Re: [I] Lake Tiering Service is not compatible with Flink 2.1 (ClassNotFoundException MultipleParameterTool) [fluss]

Tue, 23 Dec 2025 00:29:22 -0800 


sd4324530 commented on issue #1983:
URL: https://github.com/apache/fluss/issues/1983#issuecomment-3685712469

   > Hi, [@sd4324530](https://github.com/sd4324530) , would you like to test 
lake tiering service in real session, I have found that 
getRuntimeContext().getAttemptNumber() is also not founded in flink 
2.1您好，您是否想在实际会话中测试 Lake Tiering 服务？我发现 Flink 2.1 中也找不到 
`getRuntimeContext().getAttemptNumber()` 方法。
   > 
   > <img alt="Image" width="822" height="357.625" 
src="https://private-user-images.githubusercontent.com/125648852/529549153-5364a98b-cc03-4a6a-ba31-6cabb6f238e5.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjY0Nzg0MDEsIm5iZiI6MTc2NjQ3ODEwMSwicGF0aCI6Ii8xMjU2NDg4NTIvNTI5NTQ5MTUzLTUzNjRhOThiLWNjMDMtNGE2YS1iYTMxLTZjYWJiNmYyMzhlNS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUxMjIzJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MTIyM1QwODIxNDFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT04OTEyYjVjYTZhYjgzMjExNzhkNTU3MDkxNGIzNGE5NzczZDAwODI4NTlmNDAxZGUwODFmZTU2MmM1MWU2Y2Y5JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.mJacNFzxAc3nCnadrvSQP6K3uR68IxGfrQomGYbBPrc";>
   
   @loserwang1024 Thank you very much, but I haven't officially used Fluss in 
my data warehouse yet, so I don't have a real environment to test it.
   However, I see that Flink's official documentation addresses the issue 
you've raised.
   The current code is compatible with Flink version 1.18. Newer versions can 
replace it with: `getRuntimeContext().getTaskInfo().getAttemptNumber()`.
   We should need to adapt it for Flink 1.19 and above.
   
   <img width="639" height="285" alt="Image" 
src="https://github.com/user-attachments/assets/0676edc5-1630-4ba4-8567-0d78833f137f";
 />
   


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