How to pass a lot of data to Plumber in R
I would like to play with the plumber
library by making an app that takes 14 days of historical data and returns an exponential smoothing forecast.
The problem is I am somewhat unfamiliar with passing a lot of data (a parameter with multiple values) to an API. My questions can be summarized as follows:
How should I prepare the data in R to be passed to the API?
How should the API be prepared in
plumber
to receive time series data?
Below is some example data and a function which accomplishes what I would like in R.
library(tidyverse)
# data to be passed to API
head(forecast::wineind,14)
#> Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov
#> 1980 15136 16733 20016 17708 18019 19227 22893 23739 21133 22591 26786
#> 1981 15028 17977
#> Dec
#> 1980 29740
#> 1981
#* Return Forecast Data
#* @list a The first number
#* @get /simple_fcast
function()
ts() %>%
forecast::ets() %>%
forecast::forecast()
#> function()
#> ts() %>%
#> forecast::ets() %>%
#> forecast::forecast()
#>
Created on 2018-11-14 by the reprex package (v0.2.1)
r plumber
add a comment |
I would like to play with the plumber
library by making an app that takes 14 days of historical data and returns an exponential smoothing forecast.
The problem is I am somewhat unfamiliar with passing a lot of data (a parameter with multiple values) to an API. My questions can be summarized as follows:
How should I prepare the data in R to be passed to the API?
How should the API be prepared in
plumber
to receive time series data?
Below is some example data and a function which accomplishes what I would like in R.
library(tidyverse)
# data to be passed to API
head(forecast::wineind,14)
#> Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov
#> 1980 15136 16733 20016 17708 18019 19227 22893 23739 21133 22591 26786
#> 1981 15028 17977
#> Dec
#> 1980 29740
#> 1981
#* Return Forecast Data
#* @list a The first number
#* @get /simple_fcast
function()
ts() %>%
forecast::ets() %>%
forecast::forecast()
#> function()
#> ts() %>%
#> forecast::ets() %>%
#> forecast::forecast()
#>
Created on 2018-11-14 by the reprex package (v0.2.1)
r plumber
add a comment |
I would like to play with the plumber
library by making an app that takes 14 days of historical data and returns an exponential smoothing forecast.
The problem is I am somewhat unfamiliar with passing a lot of data (a parameter with multiple values) to an API. My questions can be summarized as follows:
How should I prepare the data in R to be passed to the API?
How should the API be prepared in
plumber
to receive time series data?
Below is some example data and a function which accomplishes what I would like in R.
library(tidyverse)
# data to be passed to API
head(forecast::wineind,14)
#> Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov
#> 1980 15136 16733 20016 17708 18019 19227 22893 23739 21133 22591 26786
#> 1981 15028 17977
#> Dec
#> 1980 29740
#> 1981
#* Return Forecast Data
#* @list a The first number
#* @get /simple_fcast
function()
ts() %>%
forecast::ets() %>%
forecast::forecast()
#> function()
#> ts() %>%
#> forecast::ets() %>%
#> forecast::forecast()
#>
Created on 2018-11-14 by the reprex package (v0.2.1)
r plumber
I would like to play with the plumber
library by making an app that takes 14 days of historical data and returns an exponential smoothing forecast.
The problem is I am somewhat unfamiliar with passing a lot of data (a parameter with multiple values) to an API. My questions can be summarized as follows:
How should I prepare the data in R to be passed to the API?
How should the API be prepared in
plumber
to receive time series data?
Below is some example data and a function which accomplishes what I would like in R.
library(tidyverse)
# data to be passed to API
head(forecast::wineind,14)
#> Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov
#> 1980 15136 16733 20016 17708 18019 19227 22893 23739 21133 22591 26786
#> 1981 15028 17977
#> Dec
#> 1980 29740
#> 1981
#* Return Forecast Data
#* @list a The first number
#* @get /simple_fcast
function()
ts() %>%
forecast::ets() %>%
forecast::forecast()
#> function()
#> ts() %>%
#> forecast::ets() %>%
#> forecast::forecast()
#>
Created on 2018-11-14 by the reprex package (v0.2.1)
r plumber
r plumber
asked Nov 14 '18 at 20:48
AlexAlex
6251822
6251822
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The answer is to use "message body" per the documentation here https://www.rplumber.io/docs/routing-and-input.html#
#' @post /user
function(req, id, name)
list(
id = id,
name = name,
raw = req$postBody
)
Running curl --data "id=123&name=Jennifer" "http://localhost:8000/user"
will return:
"id": [123],
"name": ["Jennifer"],
"raw": ["id=123&name=Jennifer"]
I found that arrays can also be passed to functions.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53308492%2fhow-to-pass-a-lot-of-data-to-plumber-in-r%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The answer is to use "message body" per the documentation here https://www.rplumber.io/docs/routing-and-input.html#
#' @post /user
function(req, id, name)
list(
id = id,
name = name,
raw = req$postBody
)
Running curl --data "id=123&name=Jennifer" "http://localhost:8000/user"
will return:
"id": [123],
"name": ["Jennifer"],
"raw": ["id=123&name=Jennifer"]
I found that arrays can also be passed to functions.
add a comment |
The answer is to use "message body" per the documentation here https://www.rplumber.io/docs/routing-and-input.html#
#' @post /user
function(req, id, name)
list(
id = id,
name = name,
raw = req$postBody
)
Running curl --data "id=123&name=Jennifer" "http://localhost:8000/user"
will return:
"id": [123],
"name": ["Jennifer"],
"raw": ["id=123&name=Jennifer"]
I found that arrays can also be passed to functions.
add a comment |
The answer is to use "message body" per the documentation here https://www.rplumber.io/docs/routing-and-input.html#
#' @post /user
function(req, id, name)
list(
id = id,
name = name,
raw = req$postBody
)
Running curl --data "id=123&name=Jennifer" "http://localhost:8000/user"
will return:
"id": [123],
"name": ["Jennifer"],
"raw": ["id=123&name=Jennifer"]
I found that arrays can also be passed to functions.
The answer is to use "message body" per the documentation here https://www.rplumber.io/docs/routing-and-input.html#
#' @post /user
function(req, id, name)
list(
id = id,
name = name,
raw = req$postBody
)
Running curl --data "id=123&name=Jennifer" "http://localhost:8000/user"
will return:
"id": [123],
"name": ["Jennifer"],
"raw": ["id=123&name=Jennifer"]
I found that arrays can also be passed to functions.
answered Nov 19 '18 at 21:56
AlexAlex
6251822
6251822
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53308492%2fhow-to-pass-a-lot-of-data-to-plumber-in-r%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown