Open waj334 opened 2 years ago
Turns out I was using Flink 1.15. Switched 1.14 and it worked.
So the issue has been resolved?
I'd be a bit more concerned if the pipeline were non-trivial. The SDK does do it's own cycle detection. Currently appropriately triaged as a P3.
This is now happening to us after we tried upgrading from 1.14 to 1.15.
is this bug resolved? I just met this problem..
is this bug resolved? I just met this problem..
Is the pipeline more than a trivial single Impulse?
is this bug resolved? I just met this problem..
Is the pipeline more than a trivial single Impulse?
sorry for my poor english, i do not understand what your meaning... I just submit the job to flink 1.13.1 cluster, and successful:
@sdcys-github No worries!
In this instance, I'm curious about what circumstances you have reproduced this bug.
If your pipeline is a single Impulse sith no other transforms, then it's exactly the same. In this case the bug remains on the Flink runner side, not the Go side.
But if your pipeline has additional transforms, and still has a "job graph is cyclic" error, then I would like you to provide the shape of that pipeline. This doesn't mean revealing the code of the transforms, but how they are connected.
The given Pipeline screenshot in your reply has two transforms and the pipeline succeeds according to your comment.
If the pipeline is succeeding, it can't be experiencing this bug.
If it is experiencing this bug, the versions of flink, and beam, and the shape of the pipeline would be valuable in reproducing the issue and ultimately resolving the issue.
What happened?
I tried a extremely simple beam pipeline:
When using the flink runner with the following error:
Issue Priority
Priority: 3
Issue Component
Component: sdk-go