Any suggestions on how to resolve this issue permanently. At present the only workaround that I've is to restart StreamSets. I did that in development (local) environment. But that's not an option in Production.
Regards
Swayam
Page 1 / 1
@swayam The Jira states that this issue happens when there are some data rules created and the workaround would be to delete those.
Hi @Sanjeev
“there are some data rules created” - I’m unable to understand what data rules it is reffering to? My pipeline is as below:
If you don’t have the data rules defined, perhaps the issue is caused by something else.
Thanks - actually there is no “Data Rules’ that is configured in pipeline. So the actual cause of the issue is still unknown and there is no elegant recovery from this.
Regards
Swayam
@swayam Please raise a support ticket for the RCA & resolution.