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 fo
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.
>
> > On Jun 15, 2016, at 12:20
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 format affects schema design.
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.
> On Jun 15, 2016, at 12:20 PM, Jonathan Ellis wrote:
>
> I agree that it should be documented bu
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 one day something li
Definitely required reading for anyone getting into it, plus Aaron's post.
I think ideally one day something like this should live in the docs:
https://www.postgresql.org/docs/9.0/static/storage-page-layout.html
Definitely not suggesting everyone drop what they're doing and document the
3.0 forma
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
> https://issues.apache.org/jira/brow
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.
>
>
> http://thelastpickle.com
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:
> > http://wiki.apache.org/cassandra/ArchitectureSSTable
>
> Be
> 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 p
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 d
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 det
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:
> Where else to discuss it? It should be constructive, yes. But we are all
> here to learn and grow with Cassandra. The original question is a good
> one. The direction it took was poor.
Agreed, hijacking unrelated threads is not good netizenry. There's
obviously a lot of strong opinions here, b
Hi Chris,
Thanks for your advice.
However, according to the Apache Way:
" PMCs are expected to follow corporate policies in terms of licensing,
branding, infrastructure and so on, and are expected to manage their
projects independently using The Apache Way. PMCs are tasked with all other
aspects
Bhuvan,
You didn't disrespect anyone, so please don't apologize! Appreciate your
positive and helpful comment for the OP :)
best,
kjellman
> On Jun 13, 2016, at 8:50 AM, Bhuvan Rawal wrote:
>
> Hi Matt,
>
> I suggested the resources keeping in mind the ease with which one can
> learn. My id
Hi Matt,
I suggested the resources keeping in mind the ease with which one can
learn. My idea was not to disrespect Apache or community in any form, it
was just to facilitate learning of a Newbie.
While having a good wiki would be amazing and I believe we all agree on
this Thread that current Docu
On Mon, Jun 13, 2016 at 8:05 AM, Mattmann, Chris A (3980)
wrote:
> However also see that besides the current documentation, there needs to be
> a roadmap for making Apache Cassandra and *its* documentation (not
> *DataStax’s*)
> up to par for a basic user to build, deploy and run Cassandra. I don
Hi Benjamin,
On 6/13/16, 6:38 AM, "Benjamin Lerer" wrote:
>Hi Chris,
>
>Disclaimer: I am a Datastax employee
>
>It is clear to me that the current official documentation is far from being
>enough. That's why I fully support the decision made by Jonathan to do our
>best to improve it.
Just as
Hi Chris,
Disclaimer: I am a Datastax employee
It is clear to me that the current official documentation is far from being
enough. That's why I fully support the decision made by Jonathan to do our
best to improve it.
As an Apache Cassandra Committer mostly working on the CQL layer, I know
that
Hi Harmeet,
The dev list is the lifeblood of an Apache project, and
projects here at the ASF conduct 99% of their business in
public, not in private. The ASF is a non-profit for the
public good and we have a tradition of openness and
transparency.
Even if the business isn’t pleasant some times
Where else to discuss it? It should be constructive, yes. But we are all
here to learn and grow with Cassandra. The original question is a good
one. The direction it took was poor.
On Jun 11, 2016 11:54 PM, wrote:
> Dear All,
>
> I am user of Cassandra. I am grateful to each of you for providing
Dear All,
I am user of Cassandra. I am grateful to each of you for providing your time as
committers to the code base for a great product.
This is what I wanted to suggest - could you gentlemen not create a group email
Id to discuss matters of such importance amongst yourselves. Using the dev
Looking at that thread, I'm surprised you didn't call Dave out as well,
that attitude did no one any favours.
>Because lets all face the
>facts here, no one "likes" writing drivers and documentation, and I have
>done both for this project.
That's clearly incorrect, I (and I suspect other people)
Hi Russell,
[CC/board@, board members may want to join the
Apache Cassandra lists for specifics and further
engagement]
Multiple things that need to be addressed below, but TL;DR:
1. I have asked the Apache Cassandra PMC, and its chair, to provide
a detailed description on how the project *isn’
It's really not open to debate that the Project needs to provide adequate
documentation. We have dropped the ball on this as a community since Moin
became unusable, but we are now coordinating the replacement on
CASSANDRA-8700 and should have a first version as soon as a week from now.
There is a
I respectfully disagree. "Newbies" should be pointed in the direction that
will ensure the highest possibility of their success with the product.
This is the best decision for the project, regardless of where the
documentation may reside.
As one of the authors of an early book on Cassandra, the r
So then, not going to help, at all. i see.
ok
On 06/11/2016 12:31 PM, Mattmann, Chris A (3980) wrote:
Hi Dave,
Can you please clarify what you mean by “someone of my stature
[sic]” should do something about the tools supplied by Apache? It’s
not my responsibility - it’s the community’s r
Hi Dave,
Can you please clarify what you mean by “someone of my stature
[sic]” should do something about the tools supplied by Apache? It’s
not my responsibility - it’s the community’s responsibility and
infra’s responsibility from a perspective of aiding the communities
here at the foundation.
H
Chris,
The tools supplied by Apache for documentation, ie, wiki, are awful. No
human being should be subjected to those. It would be great if someone
of your stature would do something about that for the entire Apache
community.
On 06/11/2016 12:16 PM, Mattmann, Chris A (3980) wrote:
Hi
Hi Everyone,
While this may be a current great source of documentation on
Cassandra, and while it exists externally, the PMC should be
be promoting (and hopefully ensuring) that the source of documentation
for Apache Cassandra is here at the ASF.
I’m happy to be corrected that that is the case,
Hi Deepak,
You can try Datastax Docs, they are most extensive and updated
documentation available.
As Cassandra is a fast developing technology I wonder if there is a Book in
the market which covers latest features like Materialized Views/ SASI Index
or new SSTable Format. I believe the best start
Hey
Namaskara~Nalama~Guten Tag~Bonjour
I am a newbie.
Which would be the best book for a newbie to learn Cassandra?
Thank You
Deepak
--
Keigu
Deepak
73500 12833
www.simtree.net, dee...@simtree.net
deic...@gmail.com
LinkedIn: www.linkedin.com/in/deicool
Skype: thumsupdeicool
Google talk: de
33 matches
Mail list logo
