{"action":"created","issue":{"url":"https://api.github.com/repos/jhipster/generator-jhipster/issues/3684","repository_url":"https://api.github.com/repos/jhipster/generator-jhipster","labels_url":"https://api.github.com/repos/jhipster/generator-jhipster/issues/3684/labels{/name}","comments_url":"https://api.github.com/repos/jhipster/generator-jhipster/issues/3684/comments","events_url":"https://api.github.com/repos/jhipster/generator-jhipster/issues/3684/events","html_url":"https://github.com/jhipster/generator-jhipster/issues/3684","id":158526073,"number":3684,"title":"Java Based Cassandra Migration Utility","user":{"login":"jd-carroll","id":1885864,"avatar_url":"https://avatars.githubusercontent.com/u/1885864?v=3","gravatar_id":"","url":"https://api.github.com/users/jd-carroll","html_url":"https://github.com/jd-carroll","followers_url":"https://api.github.com/users/jd-carroll/followers","following_url":"https://api.github.com/users/jd-carroll/following{/other_user}","gists_url":"https://api.github.com/users/jd-carroll/gists{/gist_id}","starred_url":"https://api.github.com/users/jd-carroll/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jd-carroll/subscriptions","organizations_url":"https://api.github.com/users/jd-carroll/orgs","repos_url":"https://api.github.com/users/jd-carroll/repos","events_url":"https://api.github.com/users/jd-carroll/events{/privacy}","received_events_url":"https://api.github.com/users/jd-carroll/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/jhipster/generator-jhipster/labels/feature%20request","name":"feature request","color":"0052cc"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2016-06-04T21:56:43Z","updated_at":"2016-06-08T13:08:11Z","closed_at":null,"body":"I've created a simple Java based Cassandra migration utility using code from jsevellec/cassandra-unit and smartcat-labs/cassandra-migration-tool-java.  The utility uses the same cql files that are already available, however instead of executing them in a separate Docker container, it executes them as part of the cluster creation.\r\n\r\nHappy to PR this, if it would be something people are interested in... ?"},"comment":{"url":"https://api.github.com/repos/jhipster/generator-jhipster/issues/comments/224582973","html_url":"https://github.com/jhipster/generator-jhipster/issues/3684#issuecomment-224582973","issue_url":"https://api.github.com/repos/jhipster/generator-jhipster/issues/3684","id":224582973,"user":{"login":"raphaelbrugier","id":579318,"avatar_url":"https://avatars.githubusercontent.com/u/579318?v=3","gravatar_id":"","url":"https://api.github.com/users/raphaelbrugier","html_url":"https://github.com/raphaelbrugier","followers_url":"https://api.github.com/users/raphaelbrugier/followers","following_url":"https://api.github.com/users/raphaelbrugier/following{/other_user}","gists_url":"https://api.github.com/users/raphaelbrugier/gists{/gist_id}","starred_url":"https://api.github.com/users/raphaelbrugier/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/raphaelbrugier/subscriptions","organizations_url":"https://api.github.com/users/raphaelbrugier/orgs","repos_url":"https://api.github.com/users/raphaelbrugier/repos","events_url":"https://api.github.com/users/raphaelbrugier/events{/privacy}","received_events_url":"https://api.github.com/users/raphaelbrugier/received_events","type":"User","site_admin":false},"created_at":"2016-06-08T13:08:11Z","updated_at":"2016-06-08T13:08:11Z","body":"Good!\r\nI think Cassandra has a \"schema agreement\" kind of lock for tables creations, but the other concern is about data migration.\r\nSay, adding a column and then filling it based on some existing data.\r\nA good workaround is to have only idempotent queries, but it's not always feasible and I'm not even sure if this would work concurrently.\r\n\r\nI'm still not sure to buy the idea of having the app itself doing the migration.\r\n@pascalgrimaud @jdubois what do you think?  \r\n\r\nI agree, one cluster per service would probably be a bit of overweighting. 1 keyspace per service  should be enough for most of the use cases.\r\nBut it really depends on your services load and you have to be careful.\r\nYou don't want a very loaded service to have performance impact on another because of the C* cluster. \r\n\r\nYou can keep working on your PR and let me know if I can help.\r\nIf we don't want to have the service instance manage the migration, at least we can use your work to do it externally."}}
{"actor":{"display_login":"raphaelbrugier"}}