Hi
Yes, basically rows have no cells as everything is in the partition
key/clustering columns.
You can always look unto the data using the sstabledump (this is for DSE
6.7 that I have running):
sstabledump ac-1-bti-Data.db
[
{
"partition" : {
"key" : [ "977eb1f1-aa5b-11ea-b91a-db426
Generally if you foresee the partitions getting out of control in terms of
size, a method often employed is to bucket according to some criteria. For
example, if I have a time series use case, I might bucket by month or week.
That presumes you can foresee it though. As far as limiting that ca
On 2016-09-12 10:17 (-0700), Anshu Vajpayee wrote:
> Thanks Jeff. I got the answer now.
> Is there any way to put guardrail to avoid large partition from cassandra
> side? I know it is modeling problem and cassandra writes warning on
> system. log for large partition. But I think there shou
Thanks Jeff. I got the answer now.
Is there any way to put guardrail to avoid large partition from cassandra
side? I know it is modeling problem and cassandra writes warning on
system. log for large partition. But I think there should be a way to put
restriction for it from Cassandra side.
On 1
Mark,
As you admitted: "I subscribed to the mailing list on 22 August" and "my
minimal technical knowledge of Cassandra", then why you're even posting
something that's not providing real help to the Cassandra user community?
As stated in RFC 1855 (https://www.ietf.org/rfc/rfc1855.txt), section
3.
On 2016-09-08 18:53 (-0700), Anshu Vajpayee wrote:
> Is there any way to get partition size for a partition key ?
>
Anshu,
The simple answer to your question is that it is not currently possible to get
a partition size for an arbitrary key without quite a lot of work (basically
you'd have t
In US english it is also debatable over which words are profane.
https://simple.wikipedia.org/wiki/Profanity
Different words can be profanity to different people, and what words are
thought of as profanity in English can change over time.
Suggestion:
https://www.youtube.com/watch?v=L0MK7qz13bU
O
The guidelines stipulate no "excessive or unnecessary" profanity. Perhaps
you also decide what qualifies as necessary or non-excessive?
To summarise my view of this entire discussion: policing users is just...
mind boggling. Well worthy of profanity.
On 12 September 2016 at 14:16, Mark Thoma
On 12/09/2016 12:51, Benedict Elliott Smith wrote:
Please tone down your language. There is no need for profanity.
Now is probably a good time to remind everyone of the Apache Code of
Conduct:
http://www.apache.org/foundation/policies/conduct.html
> (a link to 3rd party docs in response to
(a link to 3rd party docs in response to a question when an equivalent link
> to project hosted docs was available)
>
No, it wasn't. Or at least the link you sent was not remotely the same as
the link in the email you responded to, which was about how to understand
your partition sizes - not the
On 09/09/2016 21:11, Benedict Elliott Smith wrote:
> Come on. This kind of inconsistent 'policing' is not helpful.
How is it inconsistent? Since I subscribed to the mailing list on 22
August, this is the first instance I have seen of anyone providing a
link to third party docs rather than the equi
I fully agree with Benedict here. I would much prefer to keep this sort of
toxic behavior off the ML. People can link to whatever helpful docs /
blogs they choose.
On Fri, Sep 9, 2016 at 1:12 PM Benedict Elliott Smith
wrote:
> Come on. This kind of inconsistent 'policing' is not helpful.
>
> B
Come on. This kind of inconsistent 'policing' is not helpful.
By all means, push the *committers* to improve the project docs as is
happening, and to promote the internal resources over external ones.
But Mark has absolutely no formal connection with the project, and his
contributions have only b
On 9/9/16, 12:14 PM, "Mark Thomas" wrote:
> If you are going to point to docs, please
>point to the official Apache docs unless there is a very good reason not to.
>
(And if the good reason is that there’s a deficiency in the apache Cassandra
docs, please make it known on the list or in a jir
On 9/9/16, 8:47 AM, "Rakesh Kumar" wrote:
>> If your partition sizes are over 100MB iirc then you'll normally see
>> warnings in your system.log, this will outline the partition key, at least
>> in Cassandra 2.0 and 2.1 as I recall.
>
>Has it improved in C* 3.x. What is considered a good partit
On 09/09/2016 16:46, Mark Curtis wrote:
> If your partition sizes are over 100MB iirc then you'll normally see
> warnings in your system.log, this will outline the partition key, at
> least in Cassandra 2.0 and 2.1 as I recall.
>
> Your best friend here is nodetool cfstats which shows you the
> mi
On 9 September 2016 at 16:47, Rakesh Kumar
wrote:
> On Fri, Sep 9, 2016 at 11:46 AM, Mark Curtis
> wrote:
> > If your partition sizes are over 100MB iirc then you'll normally see
> > warnings in your system.log, this will outline the partition key, at
> least
> > in Cassandra 2.0 and 2.1 as I re
On Fri, Sep 9, 2016 at 11:46 AM, Mark Curtis wrote:
> If your partition sizes are over 100MB iirc then you'll normally see
> warnings in your system.log, this will outline the partition key, at least
> in Cassandra 2.0 and 2.1 as I recall.
Has it improved in C* 3.x. What is considered a good part
If your partition sizes are over 100MB iirc then you'll normally see
warnings in your system.log, this will outline the partition key, at least
in Cassandra 2.0 and 2.1 as I recall.
Your best friend here is nodetool cfstats which shows you the min/mean/max
partition sizes for your table. It's quit
19 matches
Mail list logo
