Allow filtering is almost never the answer, especially when you want to do
a full table scan ( there might be some cases where the query is limited to
a partition and allow filtering could be used). And you would like to run
this query every minute - thus extremely good performance is required.
All
last entry
> . So the proposed solution is actually keeping much more data then needed .
>
> On Oct 9, 2017 8:40 PM, "Valentina Crisan"
> wrote:
>
> Allow filtering is almost never the answer, especially when you want to do
> a full table scan ( there might be some
Hello,
as far as I know it is not intended for MV's to have a different TTL than
the base tables. There was patch released at some point to not allow TTL
setting on MV (https://issues.apache.org/jira/browse/CASSANDRA-12868). MV's
should inherit the TTL of the base table.
Valentina
On Fri, Feb 23
:
> Hi Valentina,
>
> In that case, are there any well defined ways on how to do downsampling of
> data in C*?
>
> thanks!
>
>
> On Fri, Feb 23, 2018 at 11:36 AM, Valentina Crisan <
> valentina.cri...@gmail.com> wrote:
>
>> Hello,
>>
>&g
1) I created another table for Query#2/3. The partition Key was StartTime
and clustering key was name. When I execute my queries, I get an exception
saying that I need to ALLOW FILTERING.
*Primary key(startTime,name) - the only queries that can be answered by
this model are: where startTime = , wh
