Kirill Müller 🇺🇦We would like to guide our efforts towards improving duckplyr, focusing on the features with the most impact. For this, duckplyr now has opt-in telemetry: https://duckdblabs.github.io/duckplyr/reference/fallback.html .
This has to be enabled explicitly, and is fairly easy to opt out of entirely. We make an effort to anonymize the data before collecting it or uploading it.
I’m aware this is a sensitive topic, and I’m curious to hear your thoughts. Would you opt in, opt out, or upload manually? https://masto.machlis.com/@smach/112055384564988705
Fallback to dplyr — fallback
The duckplyr package aims at providing a fully compatible drop-in replacement for dplyr. To achieve this, only a carefully selected subset of dplyr's operations, R functions, and R data types are implemented. Whenever duckplyr encounters an incompatibility, it falls back to dplyr. To assist future development, the fallback situations can be logged to the console or to a local file and uploaded for analysis. By default, duckplyr will not log or upload anything. The functions and environment variables on this page control the process. fallback_sitrep() prints the current settings for fallback logging and uploading, the number of reports ready for upload, and the location of the logs. fallback_review() prints the available reports for review to the console. fallback_upload() uploads the available reports to a central server for analysis. The server is hosted on AWS and the reports are stored in a private S3 bucket. Only authorized personnel have access to the reports. fallback_purge() deletes some or all available reports.
vitaly_druker