Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of
 prvs=9166a5551=Ben_Boule@rapid7.com designates 208.118.227.12 as permitted
 sender)
Received-SPF: None (smtp002.rapid7.com: no sender authenticity
  information available from domain of Ben_Boule@rapid7.com)
  identity=mailfrom; client-ip=10.3.20.111;
  receiver=smtp002.rapid7.com;
  envelope-from="Ben_Boule@rapid7.com";
  x-sender="Ben_Boule@rapid7.com"; x-conformance=spf_only
Received-SPF: None (smtp002.rapid7.com: no sender authenticity
  information available from domain of
  postmaster@BOSTONEX.tor.rapid7.com) identity=helo;
  client-ip=10.3.20.111; receiver=smtp002.rapid7.com;
  envelope-from="Ben_Boule@rapid7.com";
  x-sender="postmaster@BOSTONEX.tor.rapid7.com";
  x-conformance=spf_only
From: Ben Boule <Ben_Boule@rapid7.com>
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Subject: Determining Snitch at Runtime
Thread-Topic: Determining Snitch at Runtime
Thread-Index: Ac6NOu21ruHc5xo5SfyWuUhOOcDnXQ==
Date: Tue, 30 Jul 2013 15:41:36 +0000
Message-ID: <72199978CE4FB345A2A454C6FEAAB425186CEC95@BOSTONEX.tor.rapid7.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_72199978CE4FB345A2A454C6FEAAB425186CEC95BOSTONEXtorrapi_"
MIME-Version: 1.0

--_000_72199978CE4FB345A2A454C6FEAAB425186CEC95BOSTONEXtorrapi_
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

Hi Everyone,

Sorry if the answer to this question is out there, I can't seem to find it =
by searching.

Is there a way to read the endpoint_snitch at runtime, preferably from a CQ=
L query, but fine if it's available through an older API?   (Or JMX?)

We're automating creating clusters & provisioning our schema appropriately =
into them, it'd be great if the provisioning program could figure this out =
once it connected to the cluster before creating keyspaces.  Right now we a=
re having to track a maze of parameters to make sure that the cluster gets =
created with the right snitch, and then that we can pass a parameter into t=
he provisioning program to tell it which topology strategy to use.

Thank you,
Ben
This electronic message contains information which may be confidential or p=
rivileged. The information is intended for the use of the individual or ent=
ity named above. If you are not the intended recipient, be aware that any d=
isclosure, copying, distribution or use of the contents of this information=
 is prohibited. If you have received this electronic transmission in error,=
 please notify us by e-mail at (postmaster@rapid7.com) immediately.

--_000_72199978CE4FB345A2A454C6FEAAB425186CEC95BOSTONEXtorrapi_
Content-Type: text/html; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<html dir=3D"ltr">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style id=3D"owaParaStyle" type=3D"text/css">P {margin-top:0;margin-bottom:=
0;}</style>
</head>
<body ocsi=3D"0" fpstyle=3D"1">
<div style=3D"direction: ltr;font-family: Tahoma;color: #000000;font-size: =
10pt;">Hi Everyone,<br>
<br>
Sorry if the answer to this question is out there, I can't seem to find it =
by searching.<br>
<br>
Is there a way to read the endpoint_snitch at runtime, preferably from a CQ=
L query, but fine if it's available through an older API?&nbsp;&nbsp; (Or J=
MX?)<br>
<br>
We're automating creating clusters &amp; provisioning our schema appropriat=
ely into them, it'd be great if the provisioning program could figure this =
out once it connected to the cluster before creating keyspaces.&nbsp; Right=
 now we are having to track a maze of parameters
 to make sure that the cluster gets created with the right snitch, and then=
 that we can pass a parameter into the provisioning program to tell it whic=
h topology strategy to use.<br>
<br>
Thank you,<br>
Ben<br>
</div>
<p>This electronic message contains information which may be confidential o=
r privileged. The information is intended for the use of the individual or =
entity named above. If you are not the intended recipient, be aware that an=
y disclosure, copying, distribution or use of the contents of this informat=
ion is prohibited. If you have received this electronic transmission in err=
or, please notify us by e-mail at (postmaster@rapid7.com) immediately.</p><=
/body>
</html>

--_000_72199978CE4FB345A2A454C6FEAAB425186CEC95BOSTONEXtorrapi_--