Upgrade or rewrite old version rdb loader

Hi,
we’re thinking about upgrading to the newest rdb loader version.
we’re not sure what version we are and if we might be in an earlier version then the R32 (which has no upgrade guide prior to it), we use those versions:
storage:
versions:
rdb_loader: 0.14.0
rdb_shredder: 0.13.0
emr:
ami_version: 5.9.0.
any recommendations if we should rewrite it, or upgrade it step by step? and if upgrade step by step what steps we need (ie: R35, 1.0.0, 1.2.0).

btw is there any option of a paid support for the proccess?

Hello @NirKirshbloom,

Before version 1.0.0, we were using umbrella R-based versioning. After version 1.0.0, we started to use a single version to refer to set of apps and every individual app. The versions which you use belongs to R28.
We don’t have migration guides until R32 under one place but you can find them in their respective blog post.
R29 blog post
R30 blog post
R31 blog post
Migration guides for R32 and afterward can be found here.

Please let us know if you have further questions.

Regards.

1 Like

Just to add an answer to this part - we at Snowplow offer a service whereby we spin up a pipeline in your account, and manage all of the infrastructure for you, including upgrades: https://snowplowanalytics.com/snowplow-insights/.

Typically this would mean migrating off of Open-Source to us fully managing the infrastructure for you, we don’t offer anything by way of just helping with a single upgrade of your own open-source implementation, however. If that’s what you’re looking for, then it might be worth reaching out to our partners at poplin data: https://poplindata.com.

I’m not entirely certain if they offer this kind of thing, but they may be able to help. :slight_smile:

2 Likes