{"action":"created","issue":{"url":"https://api.github.com/repos/DHI-GRAS/terracotta/issues/118","repository_url":"https://api.github.com/repos/DHI-GRAS/terracotta","labels_url":"https://api.github.com/repos/DHI-GRAS/terracotta/issues/118/labels{/name}","comments_url":"https://api.github.com/repos/DHI-GRAS/terracotta/issues/118/comments","events_url":"https://api.github.com/repos/DHI-GRAS/terracotta/issues/118/events","html_url":"https://github.com/DHI-GRAS/terracotta/issues/118","id":392482517,"node_id":"MDU6SXNzdWUzOTI0ODI1MTc=","number":118,"title":"Database compatibility across versions","user":{"login":"mrpgraae","id":3639582,"node_id":"MDQ6VXNlcjM2Mzk1ODI=","avatar_url":"https://avatars1.githubusercontent.com/u/3639582?v=4","gravatar_id":"","url":"https://api.github.com/users/mrpgraae","html_url":"https://github.com/mrpgraae","followers_url":"https://api.github.com/users/mrpgraae/followers","following_url":"https://api.github.com/users/mrpgraae/following{/other_user}","gists_url":"https://api.github.com/users/mrpgraae/gists{/gist_id}","starred_url":"https://api.github.com/users/mrpgraae/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mrpgraae/subscriptions","organizations_url":"https://api.github.com/users/mrpgraae/orgs","repos_url":"https://api.github.com/users/mrpgraae/repos","events_url":"https://api.github.com/users/mrpgraae/events{/privacy}","received_events_url":"https://api.github.com/users/mrpgraae/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2018-12-19T08:04:11Z","updated_at":"2018-12-20T16:03:21Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"There is no guarantee that a database created with an older version of Terracotta will work with a newer version. This means that upgrading an existing deployment of Terracotta can be a bit of a pain, since every dataset in the deployment must be re-ingested into a new database.\r\n\r\nWe could make this a bit easier, by making a `migrate-db` command, which takes an old db and creates a new one by re-ingesting everything using the keys and paths in the old db.\r\nAdditionally, we could have an option for simply forcing a version bump in the db without re-ingesting (like `--force-version-bump` or so) for power-users who know that the new version is compatible with their database. This could be nice for large deployments, where re-ingesting everything might take days.\r\n\r\nThe release notes should also specify whether or not the new version is compatible with databases from the previous version."},"comment":{"url":"https://api.github.com/repos/DHI-GRAS/terracotta/issues/comments/449047509","html_url":"https://github.com/DHI-GRAS/terracotta/issues/118#issuecomment-449047509","issue_url":"https://api.github.com/repos/DHI-GRAS/terracotta/issues/118","id":449047509,"node_id":"MDEyOklzc3VlQ29tbWVudDQ0OTA0NzUwOQ==","user":{"login":"mrpgraae","id":3639582,"node_id":"MDQ6VXNlcjM2Mzk1ODI=","avatar_url":"https://avatars1.githubusercontent.com/u/3639582?v=4","gravatar_id":"","url":"https://api.github.com/users/mrpgraae","html_url":"https://github.com/mrpgraae","followers_url":"https://api.github.com/users/mrpgraae/followers","following_url":"https://api.github.com/users/mrpgraae/following{/other_user}","gists_url":"https://api.github.com/users/mrpgraae/gists{/gist_id}","starred_url":"https://api.github.com/users/mrpgraae/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mrpgraae/subscriptions","organizations_url":"https://api.github.com/users/mrpgraae/orgs","repos_url":"https://api.github.com/users/mrpgraae/repos","events_url":"https://api.github.com/users/mrpgraae/events{/privacy}","received_events_url":"https://api.github.com/users/mrpgraae/received_events","type":"User","site_admin":false},"created_at":"2018-12-20T16:03:21Z","updated_at":"2018-12-20T16:03:21Z","author_association":"CONTRIBUTOR","body":"Thanks for the clarification.\r\n\r\n>Yes, part of my point is that migration scripts are probably not particularly useful for us. Incompatibility always means we need to re-compute metadata.\r\n\r\nGood, we are on the same page then 😄 "}}
{"actor":{"display_login":"mrpgraae"}}