Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: error (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAFruNddN_pFF8nHdZZHVXDDM-=daLMcRNG7NaK=2eSPT9d4Rsg@mail.gmail.com>
References: 
 <CAFruNddN_pFF8nHdZZHVXDDM-=daLMcRNG7NaK=2eSPT9d4Rsg@mail.gmail.com>
Date: Tue, 6 Jan 2015 09:58:22 -0800
Message-ID: 
 <CADR+3ZGGRbFjMagF4-tAud-ua_GzMBAfJSu8p0N0MSo=GUpkCw@mail.gmail.com>
Subject: Re: Queries required before data modeling?
From: James Rothering <jrothering@codojo.me>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=001a11340cac885d3b050bff8de1

--001a11340cac885d3b050bff8de1
Content-Type: text/plain; charset=UTF-8

Yes, "remodeling" the schema will be required to have good performance for
new queries which things had not been cached ahead of time to accommodate.

In C*, you're going to pre-compute all caching ahead of time, in order to
maximize performance.

This is in contrast to the relational approach where you get whatever you
want, but your performance may degrade when you do the costly joins.

Regards,

James

On Tue, Jan 6, 2015 at 9:47 AM, Srinivasa T N <seenutn@gmail.com> wrote:

> Hi All,
>    I was just googling around and reading the various articles on data
> modeling in cassandra.  All of them talk about working backwards, i.e.,
> first now what type of queries you are going to make and select a right
> data model which can support those queries efficiently.  But one thing I
> cannot understand: You can expect me that I can know some queries that I
> will be making but how can I know what all queries will be made before
> hand?  I have to remodel the whole stuff when I get a query which I had not
> thought off?
>
> Regards,
> Seenu.
>

--001a11340cac885d3b050bff8de1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Yes, &quot;remodeling&quot; the schema will be required to=
 have good performance for new queries which things had not been cached ahe=
ad of time to accommodate.<div><br></div><div>In C*, you&#39;re going to pr=
e-compute all caching ahead of time, in order to maximize performance.=C2=
=A0</div><div><br></div><div>This is in contrast to the relational approach=
 where you get whatever you want, but your performance may degrade when you=
 do the costly joins.=C2=A0</div><div><br></div><div>Regards,</div><div><br=
></div><div>James</div></div><div class=3D"gmail_extra"><br><div class=3D"g=
mail_quote">On Tue, Jan 6, 2015 at 9:47 AM, Srinivasa T N <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:seenutn@gmail.com" target=3D"_blank">seenutn@gmail.c=
om</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"=
><div><div><div>Hi All,<br></div>=C2=A0=C2=A0 I was just googling around an=
d reading the various articles on data modeling in cassandra.=C2=A0 All of =
them talk about working backwards, i.e., first now what type of queries you=
 are going to make and select a right data model which can support those qu=
eries efficiently.=C2=A0 But one thing I cannot understand: You can expect =
me that I can know some queries that I will be making but how can I know wh=
at all queries will be made before hand?=C2=A0 I have to remodel the whole =
stuff when I get a query which I had not thought off?<br><br></div>Regards,=
<br></div>Seenu.<br></div>
</blockquote></div><br></div>

--001a11340cac885d3b050bff8de1--