[ch140184] Update documentation about fallback templates

[Shylpx]

Resources

• Clubhouse story

Context

• Fallback templates were implemented only at the query level here. Fallbacks are also implemented at the job level here, but without any template.
• However, the example in the documentation is using the fallback template at the job level, storing the information about the error when the table name in the query is invalid, and this can only be performed at the query level (even if there were templates also for the job, because the error_message is not propagated).

Changes

• Updating the documentation, by using the fallback templates at the query level.
• Removing the message about new templates, since I guess that is not true at this point :eyes:.

[shortcut-integration[bot]]

This pull request has been linked to Clubhouse Story #140184: [gloval-seven-admin] Batch query fallback templates not being replaced.

[dgaubert]

IIRC you can define both fallbacks, at query level and job level:

• Main (job) fallback: https://github.com/CartoDB/CartoDB-SQL-API/blob/master/lib/batch/models/query/main-fallback.js
• Query fallback: https://github.com/CartoDB/CartoDB-SQL-API/blob/master/lib/batch/models/query/fallback.js

[dgaubert]

Not every job type supports main fallback, see: https://github.com/CartoDB/CartoDB-SQL-API/tree/master/lib/batch#fallback

[Shylpx]

@dgaubert You can define both fallbacks, but not templates for both, right? I mean, as you said, you can define fallbacks at query level and at job level (documentation). But AFAIK fallback templates are only implemented at query level, so I'm trying to update only the documentation for that subsection.

[dgaubert]

Perfect then, nice job.