Plumber API + Scheduled RMarkdown ETL

June 13, 2019 @jeff.keller Jeff Keller

@jeff.keller wrote:

I quite like the simplicity of using scheduled RMarkdown documents in RStudio Connect to create simple ETL flows for subsequent document renders or even shiny apps. @kellobri describes this process here, and suggests using reactivePoll or reactiveFileReader to allow shiny apps to detect changes in a data product and act accordingly.

I would like to know if there is a similar or analogous workflow for plumber APIs? I would like my plumber API to be able to detect changes in a source data set using the above ETL method, and reload the data over HTTP.

I can do this naively by loading the data every time my plumber API is called, but this is no good when the data are large. I think the solution would be to put the code that loads the data outside of the API endpoint functions in my plumber.R file, but then how would I get plumber to restart when the data changes?

Posts: 10

Participants: 4

Read full topic

Previous Article
Shiny dashboard that overlooks all API calls made on connect, timings, trends etc.?
Shiny dashboard that overlooks all API calls made on connect, timings, trends etc.?

@konradino wrote: Hello! I'm looking for a way to set up a dashboard (it doesn't...

Next Article
RStudio Connect 1.7.4.2 - Important Security Patch
RStudio Connect 1.7.4.2 - Important Security Patch

This RStudio Connect patch release addresses an urgent security update and an important bug fix. Security ...