s, how would the default setting of 4 for this property
> affect the distribution of data across my nodes?
>
>
>
>
> From: Jake Luciani
> Reply-To: "user@cassandra.apache.org"
> Date: Mon, 15 Aug 2011 12:03:22 -0700
> To: "user@cassandra.apache.org&qu
ciani mailto:jak...@gmail.com>>
Reply-To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Date: Mon, 15 Aug 2011 12:03:22 -0700
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:
Could you reproduce it?
Thx for the info I'll try to reproduce
On Aug 23, 2011, at 9:28 PM, Ashley Martens wrote:
> INFO [769787724@qtp-311722089-9825] 2011-08-23 22:07:53,750 SolrCore.java
> (line 1370) [users] webapp=/solandra path=/select
> params={fl=*,score&start=0&q=+(+(first_name:hatice^1.2)+(first_name:hatic
INFO [769787724@qtp-311722089-9825] 2011-08-23 22:07:53,750 SolrCore.java
(line 1370) [users] webapp=/solandra path=/select
params={fl=*,score&start=0&q=+(+(first_name:hatice^1.2)+(first_name:hatice~0.9^1.0)++)+AND+(+(last_name:ali^3.0)+(last_name:ali~0.9^2.1)++)+&wt=ruby&qt=standard&rows=1}
statu
Multiple cores it is. Thanks.
Solandra manages the "shard" parameters for you. you don't need to specify
anything.
On Mon, Aug 15, 2011 at 3:00 PM, Jeremiah Jordan <
jeremiah.jor...@morningstar.com> wrote:
> When using Solandra, do I need to use the Solr sharding synxtax in my
> queries? I don't think I do because Cassandra i
You want the solandra data stored under two keyspaces? Or you just want two
different logical indexes.
The former requires changing the keyspace name located in
solandra.properties but you can only access one per process.
The latter would involve creating two different solr cores at different
end
seriously, If you change the cluster name in cassandra.yaml they won't
join.
On Thu, Aug 11, 2011 at 12:31 PM, Ashley Martens wrote:
> No shared seeds. Downright freaky.
>
>
--
http://twitter.com/tjake
No shared seeds. Downright freaky.
There is nothing solandra specific that would cause this. There were no shared
seeds?
On Aug 10, 2011, at 6:24 PM, Ashley Martens wrote:
> Nope. Clean system.
>
> On Wed, Aug 10, 2011 at 3:22 PM, Nick Bailey wrote:
> Did you perhaps start up the second cluster with data from the test
> clu
Nope. Clean system.
On Wed, Aug 10, 2011 at 3:22 PM, Nick Bailey wrote:
> Did you perhaps start up the second cluster with data from the test
> cluster? If you accidentally copied the system tables over, cassandra
> would recognize the saved tokens/ips from the test cluster and attempt
> to goss
Did you perhaps start up the second cluster with data from the test
cluster? If you accidentally copied the system tables over, cassandra
would recognize the saved tokens/ips from the test cluster and attempt
to gossip with them.
On Wed, Aug 10, 2011 at 5:19 PM, Ashley Martens wrote:
> I just had
HI Eldad,
You can find the answers inline
1. How can I install Solandra and make use the existing nodes?
download the source from git hub and build locally ( just run "ant" on
source directory)
the build creates a folder "solandra-app", which contains bin,conf, lib.
The bin dir is the o
Wouldn't it be useful to store your data somewhere structured
(Cassandra is obviously an option) and then use MapReduce to store
statistics?
2011/6/22 Jake Luciani :
> Well solandra is running Cassandra so you can use Cassandra as you do today,
> but index some of the data in solr.
>
> On Jun 22
Well solandra is running Cassandra so you can use Cassandra as you do today,
but index some of the data in solr.
On Jun 22, 2011, at 3:41 AM, Sasha Dolgy wrote:
> First, thanks everyone for the input. Appreciate it. The number
> crunching would already have been completed, and all statistics
First, thanks everyone for the input. Appreciate it. The number
crunching would already have been completed, and all statistics per
game defined, and inserted into the appropriate CF/row/cols ...
So, that being said, Solandra appears to be the right way to go ...
except, this would require that
Right, Solr will not do anything other than basic aggregations (facets) and
range queries.
On Tue, Jun 21, 2011 at 3:16 PM, Dan Kuebrich wrote:
> Solandra is indeed distributed search, not distributed number-crunching.
> As a previous poster said, you could imagine structuring the data in a
> s
Solandra is indeed distributed search, not distributed number-crunching. As
a previous poster said, you could imagine structuring the data in a series
of documents with fields containing playername, teamname, position,
location, day, time, inning, at bat, outcome, etc. Then you could query to
get
If I may ask Sasha, what exactly are you trying to achieve using SolR
(or Solandra, I guess it's about the same) ?
Because from what I understood of your problem you need to do statistics
on your matches, players etc... Or do you just want to retrieve
information that are already been computed ?
Your application isn't aware of Cassandra only Solr.
The idea of Solandra is to use Cassandra as a backend for Solr.
Solr has a distributed search mechanism already so by making Solr Cassandra
aware
it can auto-shard and manage distributed queries for you, with replication
and failover etc
As for
Without getting overly complicated and long winded ... are there
practical references / examples I can review that demonstrate the
cassandra/solandra benefitsi had a quick look at
https://github.com/tjake/Solandra/wiki/Solandra-Wiki and it wasn't
dead obvious to me
On Tue, Jun 21, 2011 at
Just wanted to mention that there is also a #solandra irc channel on freenode
in case people are interested.
On Jun 21, 2011, at 1:26 PM, Mark Kerzner wrote:
> Me too!
>
> I would be interested to know how such queries are done in Solandra. I would
> understand it if it creates a complete Luce
Me too!
I would be interested to know how such queries are done in Solandra. I would
understand it if it creates a complete Lucene index of everything that's in
Cassandra, and adds the text search. Then your query goes against Lucene.
But if some data is found in column families in Cassandra, and
Solandra can answer the question you used as an example and it's more of a
fit for low-latency ad-hoc reporting then PIG. Pig queries will take
minutes not seconds.
On Tue, Jun 21, 2011 at 12:12 PM, Sasha Dolgy wrote:
> Folks,
>
> Simple question ... Assuming my current use case is the ability
I can speak for what I know :
Pig I have taken only a quick look and maybe some guys from Twitter can
answer better than me on that particular program. Pig is not for "on demand"
queries: they are quite slow and as you said you extract relevant
information and append it to another CF where you can
26 matches
Mail list logo
