{"push_id":797492910,"size":2,"distinct_size":1,"ref":"refs/heads/trunk","head":"418ecb59ae8cf159c00c2d15c10b5aece03119dc","before":"95ba0e21d9959d16b1d5fcd8d6b60c4361e77657","commits":[{"sha":"762b48f2de02497e97a31210b285eb6d39f236c1","author":{"email":"220beee1e7109cdd1ee75c5c980de34352cf48ab@datastax.com","name":"Sylvain Lebresne"},"message":"Properly extract whether a legacy slice queries static columns\n\nPre-3.0 nodes were using the slices to query or not static columns. 3.0\nhandles this though the ColumnFilter (by explicitly asking for\nstatic columns or not) and has no real way to do so through its slices.\n\nThe backward compatibility code was not handling this correctly: it was\ngenerating the 3.0 slices from the pre-3.0 one somewhat blindly, and\nthen checking if said slices were including Clustering.STATIC. This\nwork most of the time because most query selecting static simply\nstarted at Slice.Bound.BOTTOM which ended up selecting\nClustering.STATIC, but wasn't fully correct.\n\nThe patch makes sure we detect if static are selected when\ndeserializing the old slices.\n\nThe patch also fix a case of incorrect thrift limit in pagedRangeCommand\n\npatch by slebresne & bdeggleston; reviewed by slebresne & bdeggleston for CASSANDRA-10267","distinct":false,"url":"https://api.github.com/repos/apache/cassandra/commits/762b48f2de02497e97a31210b285eb6d39f236c1"},{"sha":"418ecb59ae8cf159c00c2d15c10b5aece03119dc","author":{"email":"220beee1e7109cdd1ee75c5c980de34352cf48ab@datastax.com","name":"Sylvain Lebresne"},"message":"Merge branch 'cassandra-3.0' into trunk","distinct":true,"url":"https://api.github.com/repos/apache/cassandra/commits/418ecb59ae8cf159c00c2d15c10b5aece03119dc"}]}