This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
Hoping someone has quick answers to these so I don't have to fidget with my Alteryx Server settings and poke around in MongoDB to figure it out.
1a. If I have the Output Data tools in my workflow configured to write output to disk (rather than return output to the Gallery for the user to download), does MongoDB still persist these "results"?
1b. If I have the Input Data tools in my workflow configured to read from network locations or database at runtime (rather than packaging the data when saving to Gallery or using an app that requires the user to upload a file to the Gallery), does MongoDB still persist this as "uploaded files" or is it only ever stored in memory during job execution?
2. If I set my "Persistence Options" to 0, does this mean that MongoDB never persists any data after the job is complete or does it mean that the data is deleted daily (but is in fact persisted for the time between the job being complete and the MongoDB clean up)?
But regarding 1a: do you know what specific scenarios would cause results to be persisted in MongoDB even if all those outputs are written to disk/database, rather than returning to the Gallery for download? Is it safest to assume that all workflow outputs could be persisted in MongoDB regardless of whether or not they are presented for download on the Gallery?
If the workflow's output updates a table in a DB or creates a file on a shared drive then this is not saved in the MongoDB. If the output is a file a user can download or a table rendered on the screen then it is.