{"push_id":540351163,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"c0ddb61c111a5efae48b968fe020807c78acc7b9","before":"c5de006ecd8be30761b888bbf11cf46a978de526","commits":[{"sha":"bb911d44c9cdaffb20849af6100af70d6a3ae952","author":{"email":"bf5e18af55259970721d902a7a602772e5c6126a@spotify.com","name":"Matt Brown"},"message":"add CQL collection support\n\nThis change adds support for CQL collections (Sets, Lists, Maps) for\njobs that return CQLRecords.\n\nThe support is implemented by re-using the TypeSerializer\nimplementations from within Cassandra itself.\n\nIn order to serialize a collection, the serializer for the element type\nneeds to be known as well - it is a bit hacky but the current solution\ninvolves peeking at the first element in the collection to get it's\nruntime type, and retrieving a TypeSerializer from a Map within\nCassandraRecordUtils.\n\nIn implementing this I noticed that the serialization of Collections has\nchanged between V2 and V3 of the CQL protocol. V3 is only supported by\nCassandra v2.1 so far, while V2 is understood by v2.0 (Cassandra v2.1\nshould support protocol V2 also).\n\nSince this implementation reuses the TypeSerializers from within\ncassandra-all:2.0.11:jar, it is implicitly using V2 of the protocol\nformat. This should be fine as long as the target Cassandra server is\nusing v2.0. I have not tested using these serializers when exporting to\nCassandra v1.x or v2.1+.","distinct":true,"url":"https://api.github.com/repos/spotify/hdfs2cass/commits/bb911d44c9cdaffb20849af6100af70d6a3ae952"},{"sha":"c0ddb61c111a5efae48b968fe020807c78acc7b9","author":{"email":"525254d5de392358ba7c82ec0e0627f244bffc25@users.noreply.github.com","name":"Radovan"},"message":"Merge pull request #7 from mattnworb/collection-support\n\nadd CQL collection support","distinct":true,"url":"https://api.github.com/repos/spotify/hdfs2cass/commits/c0ddb61c111a5efae48b968fe020807c78acc7b9"}]}