-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
migration path for tokyocabinet with v1.4 #1783
Comments
Hello Antonio, unfortunately both database files are not compatible. You will need to parse your logs from scratch, though the performance of the new storage should be much better than tokyocabinet. |
well those logs have been rotated away, I don't have them anymore. so this means I will lose my access data |
Are you keeping all your data on the same report? or multiple reports per access log? |
I have a single db per site that accumulates the access data since the site went live. |
Let me check if I can implement something quick for to migrate those records. I'll post back. |
could you at least document the file format produced by 1.3 and by 1.4 so that someone could write a migration tool? |
Hi,
I have a few sites where continuously updated an on-disk tokyocabinet database with goaccess v1.3. I see that v1.4 dropped support for it. Maybe I missed it, but is there any migration path so that I don't lose my current database?
The text was updated successfully, but these errors were encountered: