I have been dragged away from my use of C* to do other things... so I don't have the time to work on the plugin that I would like to have... (my working theory is that once you have kids you can have maybe 1.5 hobbies outside of work... those hobbies could be: watching a TV series; a sport; working on an OSS project; maintaining a relationship with your significant other; doing work from home; etc... Given that I am training for the marathon in Oct that leaves perhaps 0.5 of a hobby for my wife... OSS projects are not getting much of a look in until after I finish the Dublin Marathon!)
Patches are welcome. Patches with integration tests are very welcome. On 23 September 2013 10:08, Lorcan Coyle <[email protected]> wrote: > Hi all, > Are there any plans for a goal for running a CQL-based load scripts, along > the lines of the cassandra:load goal for CLI scripts? The Cassandra > community is pushing users away from CLI and towards CQL. I think this > feature could be a useful addition to the cassandra maven plugin. > > The cassandra:cql-exec goal is great for executing statements against a > pre-existing keyspace but it cannot (after many hours trying*) create new > keyspaces and populate them in the same way as the cassandra:load goal does > with CLI scripts. I've hacked a workable solution, whereby I load CLI using > cassandra:load and then follow up with cassandra:cql-exec to execute some > `ALTER TABLE` cql statements to rename columns, etc. to make my column > families / tables more cql-friendly. > > I'll go ahead and add an issue to the jira if there is any take on this > suggestion. I'd be happy to help out on this if I can. If there's no > traction, I'll stick with my hack... > Thanks, > Lorcan > -- > Lorcan Coyle > Dublin, Ireland > p.s. I posted this on the user list a few days ago, it should probably > have been posted here instead. Apologies for cross-posting. > > * cassandra:cql-exec executes all statements individually and in > isolation, so a 'use <keyspace>;' statement doesn't stick. Also, it doesn't > like empty lines or lines with comments (due to the way it splits the input > by semi-colon). For running statements in isolation, against a preexisting > keyspace it does the job. >
