DataStax Enterprise 4.6.1 / C* Pagination in Python using cqlengine 0.21.0 -

After the

I currently query results page from the Delhi stock exchange 4.6.1 (cassandra 2.0.12.200) with python and cqlengine 0.21.0 I'm trying to pointe.

My table is being asked:

  table tags_for_search (village_id integer, tag_prefix text, tag text, time timeuuid, author_id integer, tag_id UUID, create type text, primary Key ((gm_id, tag_profix), tag, time by clustering order (time digc) and bloom_filter_fips_chance = 0.010000 and caching = 'kas_only' and 'comment' and 'decalogical_read_re__chance = 0.100000 and gc_grace_second = 864000 and index_interval = 128 and reed_premier_chance )) = 0.000000 and populate_io_cache_on_flush = 'false' and default_time_to_live = 0 and speculative_retry = '99 .0PERCENTILE 'and memtable_flush_period_in_ms = 0 and compaction = {' class': 'SizeTieredCompactionStrategy'} and compression = {'sstable_compression': 'LZ4Compressor'};  

Is there an option for paging / paging.org (Datastex Enterprise / DSE 4.6.1) for the results of Python (using cqlengine 0.21.0)? Documentary solution () appears to be broken due to #

My initial query for data is:. Choose

  from that_keyspace.tags_for_search where "tag_prefix" = 'der' and 'tag_text' = '#drp1' and 'village_id' = 1 million 10000;  

or via cqlengine in Python:

  village_tags = VillageSearch.objects.filter (village_id = 1, tag_prefix = 'der', tag_text = ' # Derpy1 ') tags_data = [] Village_tags for village_tag: tags_data.append (village_tag.to_dict ()) FIRST_PAGE = village_tags previous = FIRST_PAGE [-1] next_page = list (village_tags.filter (pk__token__gt = cqlengine.Token (last. Pk)))  

Throw this error:

  code = 2200 [invalid query] message = "column" village_id "not both are restricted by a similarity Can be done and an inequality relationship " 

Is there any such option that I can use immediately C I can use to avoid this bug?

Thanks for any help you can provide!

There is no direct substitution for this functionality. The best and most appropriate answer is to upgrade (now this bug Fix is ​​available).

Upgrade your environment for DSE> = 4.6.2 will solve this problem.