CASSANDRA-14916

2019-02-01 Thread Jean Carlo
Hello guys, someone can check this jira please? I did not get a feedback from @Dinesh_Joshi for the moments :) https://issues.apache.org/jira/browse/CASSANDRA-14916 Saludos Jean Carlo "The best way to predict the future is to invent it" Alan Kay

Re: CASSANDRA-14916

2019-02-01 Thread VICTOR IBARRA
Ok that’s right Le ven. 1 févr. 2019 à 10:01, Jean Carlo a écrit : > Hello guys, someone can check this jira please? I did not get a feedback > from @Dinesh_Joshi for the moments :) > > https://issues.apache.org/jira/browse/CASSANDRA-14916 > > > Saludos > > Jean Carlo > > "The best way to

Re: SSTable exclusion from read path based on sstable metadata marked by custom compaction strategies

2019-02-01 Thread Carl Mueller
Interesting. Now that we have semiautomated upgrades, we are going to hopefully get everything to 3.11X once we get the intermediate hop to 2.2. I'm thinking we could also use sstable metadata markings + custom compactors for things like multiple customers on the same table. So you could

Re: SSTable exclusion from read path based on sstable metadata marked by custom compaction strategies

2019-02-01 Thread Jeff Jirsa
On Fri, Feb 1, 2019 at 12:58 PM Carl Mueller wrote: > Jeff: so the partition key with timestamp would then need a separate index > table to track the appid->partition keys. Which isn't horrible, but also > tracks into another desire of mine: some way to make the replica mapping > match locally

Re: SSTable exclusion from read path based on sstable metadata marked by custom compaction strategies

2019-02-01 Thread Carl Mueller
Jeff: so the partition key with timestamp would then need a separate index table to track the appid->partition keys. Which isn't horrible, but also tracks into another desire of mine: some way to make the replica mapping match locally between the index table and the data table: So in the

Re: SSTable exclusion from read path based on sstable metadata marked by custom compaction strategies

2019-02-01 Thread Jeff Jirsa
FWIW you can skip 2.2 and go 2.1 -> 3.11. I would wait for 3.11.4 though. On Fri, Feb 1, 2019 at 12:53 PM Carl Mueller wrote: > Interesting. Now that we have semiautomated upgrades, we are going to > hopefully get everything to 3.11X once we get the intermediate hop to 2.2. > > I'm thinking

Re: SSTable exclusion from read path based on sstable metadata marked by custom compaction strategies

2019-02-01 Thread Carl Mueller
I'd still need a "all events for app_id" query. We have seconds-level events :-( On Fri, Feb 1, 2019 at 3:02 PM Jeff Jirsa wrote: > On Fri, Feb 1, 2019 at 12:58 PM Carl Mueller > wrote: > > > Jeff: so the partition key with timestamp would then need a separate > index > > table to track the

Re: SSTable exclusion from read path based on sstable metadata marked by custom compaction strategies

2019-02-01 Thread Jeff Jirsa
Iterate over all of the possible time buckets. On Fri, Feb 1, 2019 at 1:36 PM Carl Mueller wrote: > I'd still need a "all events for app_id" query. We have seconds-level > events :-( > > > On Fri, Feb 1, 2019 at 3:02 PM Jeff Jirsa wrote: > > > On Fri, Feb 1, 2019 at 12:58 PM Carl Mueller > >