v0.16.0 (Data Quality - Action Required!) #1152
Replies: 7 comments 4 replies
-
Just 1 data point: I tried to update my docker compose based install from 0.15.5. The container will not start... something about the database migration. I'll probably just scrap it and install a fresh image from the new LinuxServer.io base. Just wanted to report...
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Confirmed that 0.16.1 is up and running! 🚀 |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
I feel as if I have screwed up and just wanted to ask. I only ever saw an export option not a migrate option. I unfortunately didnt read the big !!!THIS IS HAPPENING IN V16!!! message before updaitng and I had to essentially delete the entire container and folders to reinstall. It is back up and running however I lost literally my 10,000+ speedtests that have been running for the past year or two. Am I completely screwed with all of my history and should just suck it up and start over? Or is there a way to import the older CSV data back into the new install? Much appreaciated and I love your work! |
Beta Was this translation helpful? Give feedback.
-
Thing is I NEVER saw a migrate button. Only export. If my data is gone then
I guess nothing I can do further. I just was wondering. I have been using
various revisions of this up to and past 16 and never saw the migrate
button. Which version did you implement the migrate button?
…On Mon, Mar 4, 2024 at 8:04 AM Alex Justesen ***@***.***> wrote:
If you deleted the app container that's ok, but if you deleted your
database you might be SOL. The migration process expects the "bad" data to
be in another table in the same database as there isn't a method of
importing history yet.
—
Reply to this email directly, view it on GitHub
<#1152 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BBIJD3E6RAECS7KKB7R2JCLYWRWNFAVCNFSM6AAAAABDPYZQZ6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DMNRWGUYTG>
.
You are receiving this because you commented.Message ID:
<alexjustesen/speedtest-tracker/repo-discussions/1152/comments/8666513@
github.com>
|
Beta Was this translation helpful? Give feedback.
-
Just wanted to give a thank you for not only giving an in interface breaking change notification, but making it pretty much a one click fix to resolve. The migration process was fast and smooth for me, no issues to report. |
Beta Was this translation helpful? Give feedback.
-
Important
v0.16.0
includes a breaking change that requires user action for existing installs. Make sure to follow the steps below to migrate your result data!This release fixes a data quality issue (#812) that has existed since day-1. Result responses stored in
data
column where incorrectly formatted which caused extra steps and some messy code throughout the application. This release will copy your existingresults
table to a newresults_bad_json
table for safe keeping and deploy new DDL for a freshresults
table.Data Migration
If you have existing results data you can follow the steps below to migrate and fix your data.
FAQ
results_bad_json
for safe keeping.results
tableresults_bad_json
will remain in the database unless you decide to manually drop the table.Additional Changes
Full Changelog: v0.15.5...v0.16.0
This discussion was created from the release v0.16.0 (Data Quality - Action Required!).
Beta Was this translation helpful? Give feedback.
All reactions