Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Apache Arrow on Lifewatch RStudio Server #329

Open
PietrH opened this issue Oct 17, 2024 · 0 comments
Open

Apache Arrow on Lifewatch RStudio Server #329

PietrH opened this issue Oct 17, 2024 · 0 comments
Assignees

Comments

@PietrH
Copy link
Member

PietrH commented Oct 17, 2024

Hi Stijn! As discussed over lunch, here is some written context to serve as a reminder.

In the context of the work on #327 I would like to use the arrow package on the Lifewatch Rstudio Server

The most current version of this package requires a newer R version than currently installed, at least 4.0, but I recommend upgrading to R4.4. An older version of the package exists that supports R3.6, but it still needs a more recent C++ compiler.

It also requires a more recent C++ compiler, in our case, gcc at least version 7 or newer.

For more information on the arrow installation instructions ; https://arrow.apache.org/docs/r/articles/install.html

Just to empathise that I don't actually need a newer version of RStudio Server itself, just of R itself and gcc, the current RStudio Server version is Version 1.2.1335, I believe this version is at least 3 years old, there might be advantages in upgrading RStudio Server as well.

I see 2 courses of action;

  1. Upgrade the C++ compiler only, and I can run an outdated version of arrow, keep the rest the same. -> While this is a quick fix, I don't believe this to be very sustainable. This will have no real impact on other users.
  2. Update R, C++ compiler (and RStudio Server): this opens up access to many newer packages for everyone. Especially now the tidyverse is slowly dropping support for R versions lower as 4: https://www.tidyverse.org/blog/2019/04/r-version-support/, but it might or might not impact existing user package libraries. I believe this depends on the exact configuration of the server, so I can't investigate this.

While option 2 is more work, I think it'll save us time on the long run. Let me know if I can clarify anything!

This is blocking #328

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants