mp;utm_campaign=icon>
*From:* Bowen Song
*Sent:* Friday, July 1, 2022 08:48
*To:* user@cassandra.apache.org
*Subject:* Re: Query around Data Modelling -2
This message was sent from outside the company. Please do not
click links or open attachments unle
/SkylineCommu>
>
> <https://www.facebook.com/SkylineCommunications/>
>
> <https://www.instagram.com/skyline.dataminer/>
>
>
> <https://skyline.be/skyline/awards?utm_source=signature&utm_medium=email&utm_campaign=icon>
>
>
>
>
>
>
dium=email&utm_campaign=icon>
[cid:image010.png@01D88D2B.263669C0]
From: Bowen Song
Sent: Friday, July 1, 2022 08:48
To: user@cassandra.apache.org
Subject: Re: Query around Data Modelling -2
This message was sent from outside the company. Please do not click links or
open attachments unles
e
auto-compaction on the table and is relying on weekly scheduled
compactions? Or running weekly major compactions? Neither of these
sounds right.
On 30/06/2022 15:03, MyWorld wrote:
Hi all,
Another query around data Modelling.
We have a existing table with below
ng on weekly scheduled
> compactions? Or running weekly major compactions? Neither of these sounds
> right.
> On 30/06/2022 15:03, MyWorld wrote:
>
> Hi all,
>
> Another query around data Modelling.
>
> We have a existing table with below structure:
> Table(PK,CK, col1,col2,
06/2022 15:03, MyWorld wrote:
Hi all,
Another query around data Modelling.
We have a existing table with below structure:
Table(PK,CK, col1,col2, col3, col4,col5)
Now each Pk here have 1k - 10k Clustering keys. Each PK has size from
10MB to 80MB. We have overall 100+ millions partitions. Also we
:
> How are you running repair? -pr? Or -st/-et?
>
> 4.0 gives you real incremental repair which helps. Splitting the table
> won’t make reads faster. It will increase the potential parallelization of
> compaction.
>
> On Jun 30, 2022, at 7:04 AM, MyWorld wrote:
>
>
> Hi
How are you running repair? -pr? Or -st/-et?
4.0 gives you real incremental repair which helps. Splitting the table won’t
make reads faster. It will increase the potential parallelization of
compaction.
> On Jun 30, 2022, at 7:04 AM, MyWorld wrote:
>
>
> Hi all,
>
> An
Hi all,
Another query around data Modelling.
We have a existing table with below structure:
Table(PK,CK, col1,col2, col3, col4,col5)
Now each Pk here have 1k - 10k Clustering keys. Each PK has size from 10MB
to 80MB. We have overall 100+ millions partitions. Also we have set
levelled
e is still
> under 100 MB
>
> On Thu, Jun 23, 2022, 7:18 AM Jeff Jirsa wrote:
>
>> How many rows per partition in each model?
>>
>>
>> > On Jun 22, 2022, at 6:38 PM, MyWorld wrote:
>> >
>> >
>> > Hi all,
>> >
>>
7:18 AM Jeff Jirsa wrote:
>>> How many rows per partition in each model?
>>>
>>>
>>> > On Jun 22, 2022, at 6:38 PM, MyWorld wrote:
>>> >
>>> >
>>> > Hi all,
>>> >
>>> > Just a small query aroun
022, at 6:38 PM, MyWorld wrote:
>> >
>> >
>> > Hi all,
>> >
>> > Just a small query around data Modelling.
>> > Suppose we have to design the data model for 2 different use cases which
>> > will query the data on same set of (partion
ach model?
>
>
> > On Jun 22, 2022, at 6:38 PM, MyWorld wrote:
> >
> >
> > Hi all,
> >
> > Just a small query around data Modelling.
> > Suppose we have to design the data model for 2 different use cases which
> will query the data on same set
campaign=icon>
[cid:image010.png@01D886E7.E4E5C360]
From: MyWorld
Sent: Thursday, June 23, 2022 09:38
To: user@cassandra.apache.org
Subject: Query around Data Modelling
This message was sent from outside the company. Please do not click links or
open attachments unless you recognise
Table1 should be fine if some column values are not entered than Cassandra
will not create entry for them so partiton will almost be same in
both cases.
On Thu, Jun 23, 2022, 07:08 MyWorld wrote:
> Hi all,
>
> Just a small query around data Modelling.
> Suppose we have to design th
How many rows per partition in each model?
> On Jun 22, 2022, at 6:38 PM, MyWorld wrote:
>
>
> Hi all,
>
> Just a small query around data Modelling.
> Suppose we have to design the data model for 2 different use cases which will
> query the data on same set of (par
Hi all,
Just a small query around data Modelling.
Suppose we have to design the data model for 2 different use cases which
will query the data on same set of (partion+clustering key). So should we
maintain a seperate table for each or a single table.
Model1 - Combined table
Table(Pk,CK, col1
17 matches
Mail list logo
