Hi,
I have a question about cassandra architecture.
Each node in a cluster is assigned a token. My question is, how does each
node learn about tokens of other nodes? Is it through gossiping? Or do all
nodes have access to a central system table that lists all (end-point,
token) pairs?
Also what
+1
I've been running several of the 1.2.12 patches in production for a
while now.
On 11/20/2013 04:37 AM, Sylvain Lebresne wrote:
A fair number of fixes went in since 1.2.11, I propose the following
artifacts
for release as 1.2.12.
sha1: 026865f2a36d9685057c407e3fa528c101ab46b7
Git:
http://g
+1
On Wed, Nov 20, 2013 at 6:54 AM, Gary Dusbabek wrote:
> +1
>
>
> On Wed, Nov 20, 2013 at 3:37 AM, Sylvain Lebresne >wrote:
>
> > A fair number of fixes went in since 1.2.11, I propose the following
> > artifacts
> > for release as 1.2.12.
> >
> > sha1: 026865f2a36d9685057c407e3fa528c101ab46
OK, that answers my question, thank you!
- Mathieu
Le Nov 20, 2013 à 11:31 AM, Sylvain Lebresne a écrit :
>> Since C* expect a list of values for bind variables in queries, in
>> non-prepared queries the driver has no direct information about the
>> expected order of named variables. Is there a
Sorry about that,
I'm making a driver for Cassandra binary protocol v2. When the driver sends
QUERY queries (unprepared), those can contain only the CQL statement, or, if
there are bind variables in the statement, the values for the bind variables
can be sent along the statement. Recently, C* a
> Since C* expect a list of values for bind variables in queries, in
> non-prepared queries the driver has no direct information about the
> expected order of named variables. Is there a way to reliably predict the
> order of variable values C* will expect?
No, not until you parse the statement d
On Wed, Nov 20, 2013 at 10:13 AM, Mathieu D'Amours wrote:
>
> Since C* expect a list of values for bind variables in queries, in
> non-prepared queries the driver has no direct information about the
> expected order of named variables. Is there a way to reliably predict the
> order of variable val
Hello again,
Since C* expect a list of values for bind variables in queries, in non-prepared
queries the driver has no direct information about the expected order of named
variables. Is there a way to reliably predict the order of variable values C*
will expect?
+1
On Wed, Nov 20, 2013 at 3:37 AM, Sylvain Lebresne wrote:
> A fair number of fixes went in since 1.2.11, I propose the following
> artifacts
> for release as 1.2.12.
>
> sha1: 026865f2a36d9685057c407e3fa528c101ab46b7
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;
+1
On Wed, Nov 20, 2013 at 5:04 AM, Brandon Williams wrote:
> +1
>
>
> On Wed, Nov 20, 2013 at 3:37 AM, Sylvain Lebresne >wrote:
>
> > A fair number of fixes went in since 1.2.11, I propose the following
> > artifacts
> > for release as 1.2.12.
> >
> > sha1: 026865f2a36d9685057c407e3fa528c101a
+1
On Wed, Nov 20, 2013 at 3:37 AM, Sylvain Lebresne wrote:
> A fair number of fixes went in since 1.2.11, I propose the following
> artifacts
> for release as 1.2.12.
>
> sha1: 026865f2a36d9685057c407e3fa528c101ab46b7
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;
+1
On Nov 20, 2013 3:37 AM, "Sylvain Lebresne" wrote:
> A fair number of fixes went in since 1.2.11, I propose the following
> artifacts
> for release as 1.2.12.
>
> sha1: 026865f2a36d9685057c407e3fa528c101ab46b7
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/
A fair number of fixes went in since 1.2.11, I propose the following
artifacts
for release as 1.2.12.
sha1: 026865f2a36d9685057c407e3fa528c101ab46b7
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.2.12-tentative
Artifacts:
https://repository.apache.org/content/
13 matches
Mail list logo
