You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A common workflow for me is to deploy a pin containing a dataset to Connect in both a binary and human-readable format. This usually happens when R/python users want a fast, consistently typed binary (like qs or arrow) and other business users want to be able to download from Connect in csv format to pull into a spreadsheet.
Currently, I have to deploy both of these separately with unique names (and GUIDs). When distributing the pin or a when a user searches for the pin in Connect, I either have to inform them of both deployments/names or give them the correct link/name based on their tooling.
For example, my pin_write() calls usually look like this:
board %>%
pin_write(account_information,
name = "account_information",
type = "arrow"
)
board %>%
pin_write(account_information,
name = "account_information_csv",
type = "csv"
)
I'm not sure of the best way to implement this in terms of interface, but in my mind's eye I see something like an option to include_human_readable:
board %>%
pin_write(account_information,
name = "account_information",
type = "arrow",
include_human_readable = TRUE
)
or even an option to include multiple types:
board %>%
pin_write(account_information,
name = "account_information",
type = c("arrow", "csv")
)
Another benefit of "coupling" multiple deployment types of the same deployment could be having import redundancy in the case that the pin reader does not have the required package to download a special type like arrow or qs.
Thanks!
The text was updated successfully, but these errors were encountered:
A common workflow for me is to deploy a pin containing a dataset to Connect in both a binary and human-readable format. This usually happens when R/python users want a fast, consistently typed binary (like
qs
orarrow
) and other business users want to be able to download from Connect incsv
format to pull into a spreadsheet.Currently, I have to deploy both of these separately with unique names (and GUIDs). When distributing the pin or a when a user searches for the pin in Connect, I either have to inform them of both deployments/names or give them the correct link/name based on their tooling.
For example, my
pin_write()
calls usually look like this:I'm not sure of the best way to implement this in terms of interface, but in my mind's eye I see something like an option to
include_human_readable
:or even an option to include multiple types:
Another benefit of "coupling" multiple deployment types of the same deployment could be having import redundancy in the case that the pin reader does not have the required package to download a special type like
arrow
orqs
.Thanks!
The text was updated successfully, but these errors were encountered: