After digging a bit, the regression is that data inserted immediately after secondary index creation may never get indexed.
The operation order goes like this: 1) create CF 2) create secondary index 3) insert data 4) query secondary index If I add a short sleep in between steps 2 and 3, the data gets indexed and the query is successful. If I only add a sleep in between steps 3 and 4, some of the data is never indexed and the query will return incomplete results. This appears to be the case even if the sleep is relatively long (30s), which makes me think the data may never get indexed. On Tue, Mar 25, 2014 at 11:14 AM, Tyler Hobbs <ty...@datastax.com> wrote: > -1 > > I'm seeing a regression from 1.2.15 on secondary index queries (through > Thrift) with a LongType key validator. Specifically, this test in pycassa > is failing against 1.2.16-tentative: > https://github.com/pycassa/pycassa/blob/master/tests/test_autopacking.py#L793 > > I haven't looked into the issue deeply yet to see what's going on. > > > On Mon, Mar 24, 2014 at 12:24 PM, Sylvain Lebresne > <sylv...@datastax.com>wrote: > >> I propose the following artifacts for release as 1.2.16. >> >> sha1: 05fcfa2be4eba2cd6daeee62d943f48c45f42668 >> Git: >> >> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.2.16-tentative >> Artifacts: >> >> https://repository.apache.org/content/repositories/orgapachecassandra-1008/org/apache/cassandra/apache-cassandra/1.2.16/ >> Staging repository: >> >> https://repository.apache.org/content/repositories/orgapachecassandra-1008/ >> >> The artifacts as well as the debian package are also available here: >> http://people.apache.org/~slebresne/ >> >> The vote will be open for 72 hours (longer if needed). >> >> [1]: http://goo.gl/Cgiimu (CHANGES.txt) >> [2]: http://goo.gl/gvKkBm (NEWS.txt) >> > > > > -- > Tyler Hobbs > DataStax <http://datastax.com/> > -- Tyler Hobbs DataStax <http://datastax.com/>
