Re: Jira down, again?

down. again. > On Jun 14, 2016, at 11:14 AM, Alex Popescu wrote: > > I've been trying to get to a ticket for the last 2h and I only get service > unavailable :-( > > On Tue, Jun 14, 2016 at 10:26 AM, Michael Kjellman < > mkjell...@internalcircle.com> wrote: > >> and, it's

Re: NewBie Question

For newcomers that ( https://github.com/apache/cassandra/blob/cassandra-3.0.0/guide_8099.md) is probably a bad document to point them to, as it will no doubt confuse them - the naming, behaviour and format descriptions are all now partially incorrect. It was, by its own admission, intended only

Re: SSTable index format

C* 2.2 SSTable format is "la", "ma" is introduced in 3.0 including big changes on storage engige. Assuming you are asking about 2.2 and you are aware of SSTable is compound by different components. Index file which is Index.db just maps row keys to the position in Data.db. Now about how is

Re: NewBie Question

Exactly. On Wed, Jun 15, 2016 at 7:26 PM, J. D. Jordan wrote: > I think high level concepts of how data is stored should be in user facing > documentation. Storage format affects schema design. But low level > specifics should be kept to contributor documentation. > >

Re: NewBie Question

Since the specs change with the code id argue everything belongs in the git repo including deep technical specs. On Wed, Jun 15, 2016 at 10:26 AM J. D. Jordan wrote: > I think high level concepts of how data is stored should be in user facing > documentation. Storage

Re: NewBie Question

I agree that it should be documented but I don't think it should be in user level docs. Let's keep it in the wiki for contributors. On Jun 15, 2016 7:04 PM, "Jonathan Haddad" wrote: > Definitely required reading for anyone getting into it, plus Aaron's post. > I think ideally

Re: NewBie Question

This was forwarded to me yesterday... a helpful first step https://github.com/apache/cassandra/blob/cassandra-3.0.0/guide_8099.md > On Jun 15, 2016, at 9:54 AM, Jonathan Haddad wrote: > > Maybe some brave soul will document the 3.0 on disk format as part of >

Re: NewBie Question

Maybe some brave soul will document the 3.0 on disk format as part of https://issues.apache.org/jira/browse/CASSANDRA-8700. On Wed, Jun 15, 2016 at 7:02 AM Christopher Bradford wrote: > Consider taking a look at Aaron Morton's dive into the C* 3.0 storage > engine. > > >

Re: Documentation on a new CQL feature of 3.6

As far as I understand this wording, it's correct. Prior to 3.6 *filtering* was not allowed on clustering columns. It was allowed to do non-filtering queries involving clustering columns, although you could not specify any clustering column (or combine multiple range queries). Now it is allowed.

Documentation on a new CQL feature of 3.6

Hi to all, DS Documentation says that *In Cassandra 3.6 and later, clustering columns can be defined in WHERE clauses if ALLOW FILTERING is also used even if a secondary index is not created. The table definition is given and then the SELECT command. Note that race_start_date is a clustering

Re: NewBie Question

Consider taking a look at Aaron Morton's dive into the C* 3.0 storage engine. http://thelastpickle.com/blog/2016/03/04/introductiont-to-the-apache-cassandra-3-storage-engine.html On Wed, Jun 15, 2016 at 9:38 AM Jim Witschey wrote: > >

SSTable index format

Hi, I'm interested in the SSTable index file format and particularly in Cassandra 2.2 which uses the SSTable version "ma". Apart from keys and their corresponding offsets in the data file what else is included in each index entry? I'm trying to trace code when an SSTable is flushed

Re: Better code review

We had a pretty long conversation about this very topic on the dev list awhile ago (search for "Discussion: reviewing larger tickets" on the mailing list). I think the final conclusion was that having the back-and-forth via JIRA helped codify some of the design decisions that took place during

Re: NewBie Question

> http://wiki.apache.org/cassandra/ArchitectureSSTable Be aware that this page hasn't been updated since 2013, so it doesn't reflect any changes to the SSTable format since then, including the new storage engine introduced in 3.0 (see CASSANDRA-8099). That said, I believe the linked Apache wiki

Re: Possible Bug: bucket_low has no effect in STCS

When in doubt, just open a JIRA. Thanks. --  AY On 15 June 2016 at 13:56:24, Anuj Wadehra (anujw_2...@yahoo.co.in.invalid) wrote: Should I raise JIRA ?? Or some develiper with knowledge of STCS could confirm the bug ?? Anuj Sent from Yahoo Mail on Android On Tue, 14 Jun, 2016 at

Re: Possible Bug: bucket_low has no effect in STCS

Should I raise JIRA ?? Or some develiper with knowledge of STCS could confirm the bug ?? Anuj Sent from Yahoo Mail on Android On Tue, 14 Jun, 2016 at 12:52 PM, Anuj Wadehra wrote: Can any developer confirm the issue? ThanksAnuj Sent from Yahoo Mail on

Re: NewBie Question

The file format is SSTable: http://wiki.apache.org/cassandra/ArchitectureSSTable If you're getting into byte-level detail, I highly recommend you familiarize yourself with the read and/or write path first, because that deep in the bowels there are some non-obvious things going on where Cassandra

Re: NewBie Question

It's a little more involved than that. I suggest inserting a single row in a test table, then looking at the sstabledump output as a first step, then compare with two rows in a single partition. Then you can code dive to see what sstabledump is actually doing if you really need the byte-level

Reason for Trace Message Drop

Hi all, Can anyone tell me that what are all possible reasons for below log:- *"INFO [ScheduledTasks:1] 2016-06-14 06:27:39,498 MessagingService.java:929 - _TRACE messages were dropped in last 5000 ms: 928 for internal timeout and 0 for cross node timeout".* I searched online for the same and

Better code review

Hi, Today I noticed there is a https://reviews.apache.org/r/# website which can be used for code review. Why not use it or even better use GitHub PR code review facilities? Best Regards

NewBie Question

Hey Namaskara~Nalama~Guten Tag~Bonjour I tried searching for the fileformat of how cassandra stores its data, but I couldn't find any... Suppose I have a database structure of the following format: RowID: Name:Age 1: Deepak : 33 2: Deepak1:34 3: