Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Support Questions

Find answers, ask questions, and share your expertise
Announcements
Share your experience with Cloudera on G2 and get a $25 Amazon Gift card.
Hi, I'm CLEO! Something exciting is coming to the Community. Stay Tuned!

GenerateTableFetch - On Error

avatar
Contributor

Hello,

I have Two Questions

1. In case of error , GenerateTableFetch is not getting routed to Failure.  

mohdriyaz_0-1717299182022.png

2.  GenerateTableFetch keep on trying .  I need it should do this only once in case of error.

mohdriyaz_1-1717299272208.png

Thanks,

Riyaz

1 REPLY 1

avatar
Super Guru

Hi @mohdriyaz ,

It seems the generatetablefetch by design pushes and penalize the flow to the upstream queue when there is an error that is considered none "sql query"  error which per documentation only query execution error will go to the failure rel.

SAMSAL_0-1717328412783.png

It doesnt seem like there is anything you can do to change this behavior. The only thing I can think of to mitigate this issue is by adding another processor as a guard to help checking the connection status before calling the generateTableFetch processor. For example you can use PutSQL processors which seems from the description able to capture connectivity error through retry & maybe the failure rel per description:

SAMSAL_1-1717328678360.png

This is not going to solve the problem 100% but it will minimize it and it will help you capture the error.

You can configure how many to retry and for how long in the relationship tab once you  select to retry.

Hope that helps. If it does help please accept the solution.

S