? --wunder
On Jul 5, 2013, at 1:28 PM, Valery Giner wrote:
Eric,
We did not have any RAM problems, but just the following official limitation
makes our life too miserable to use the shards:
"Makes it more inefficient to use a high "start" parameter. For example, if you request
st
roof. Now
consider allocating longs instead...
which is a long way of saying that I don't really think anyone's going
to be working on this any time soon, especially when SolrCloud removes
a LOT of the pain /complexity (from a user perspective anyway) from
going to a sharded setup...
FW
in multiple shards, that would indicate a bug. But there are many
ways, especially when experimenting, that you could have this happen
which are _not_ a bug. I'm guessing that Luis may be trying the custom
routing option maybe?
Best
Erick
On Fri, May 24, 2013 at 9:09 AM, Valery Giner wrote:
Shawn,
How is it possible for more than one document with the same unique key
to appear in the index, even in different shards?
Isn't it a bug by definition?
What am I missing here?
Thanks,
Val
On 05/23/2013 09:55 AM, Shawn Heisey wrote:
On 5/23/2013 1:51 AM, Luis Cappa Banda wrote:
I've qu
Otis Gospodnetic wrote:
Val,
Haven't seen this mentioned in a while...
I'm curious...what sort of index, queries, hardware, and latency
requirements do you have?
Otis
Solr & ElasticSearch Support
http://sematext.com/
On May 1, 2013 4:36 PM, "Valery Giner" wrote:
Dear Solr
Dear Solr Developers,
I've been unable to find an answer to the question in the subject line
of this e-mail, except of a vague one.
We need to be able to index over 2bln+ documents. We were doing well
without sharding until the number of docs hit the limit ( 2bln+). The
performance was s
