Thank you for all your hard work!
Michael Della Bitta
Appinions
18 East 41st Street, 2nd Floor
New York, NY 10017-6271
www.appinions.com
Where Influence Isn’t a Game
On Wed, Apr 3, 2013 at 6:08 PM, Mark Miller wrote:
>
> On Apr 3, 2013, at 5:5
On Apr 3, 2013, at 5:53 PM, Michael Della Bitta
wrote:
> From what I can tell, the Collections API has been hardened
> significantly since 4.2
I did a lot of work here for 4.2.1 - there was a lot to improve. Hopefully
there is much less now, but if anyone finds anything, I'll fix any JIRA's.
>From what I can tell, the Collections API has been hardened
significantly since 4.2 and now will refuse to create a collection if
you give it something ambiguous to do. So if you upgrade to 4.2,
things will become more safe.
But overall I'd find a way of using the Collections API that works and
s
Michael Della Bitta-2 wrote
> If you can work with a clean state, I'd turn off all your shards,
> clear out the Solr directories in Zookeeper, reset solr.xml for each
> of your shards, upgrade to the latest version of Solr, and turn
> everything back on again. Then upload config, recreate your
> co
If you can work with a clean state, I'd turn off all your shards,
clear out the Solr directories in Zookeeper, reset solr.xml for each
of your shards, upgrade to the latest version of Solr, and turn
everything back on again. Then upload config, recreate your
collection, etc.
I do it like this, but
Michael Della Bitta-2 wrote
> With earlier versions of Solr Cloud, if there was any error or warning
> when you made a collection, you likely were set up for "implicit"
> routing which means that documents only go to the shard you're talking
> to. What you want is "compositeId" routing, which works
With earlier versions of Solr Cloud, if there was any error or warning
when you made a collection, you likely were set up for "implicit"
routing which means that documents only go to the shard you're talking
to. What you want is "compositeId" routing, which works how you think
it should.
Go into t
Chris Hostetter-3 wrote
> I'm not familiar with the details, but i've seen miller respond to a
> similar question with reference to the issue of not explicitly specifying
> numShards when creating your collections...
>
> http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201303.mbox/%
>
: So we indexed a set of 33010 documents on server01 which are now in shard1.
: And we kicked off a set of 85934 documents on server02 which are now in
: shard2 (as tests). In my understanding of how SolrCloud works, the
: documents should be distributed across the shards in the collection. Now I
Michael Della Bitta-2 wrote
> Hello Vytenis,
>
> What exactly do you mean by "aren't distributing across the shards"?
> Do you mean that POSTs against the server for shard 1 never end up
> resulting in documents saved in shard 2?
So we indexed a set of 33010 documents on server01 which are now in
Hello Vytenis,
What exactly do you mean by "aren't distributing across the shards"?
Do you mean that POSTs against the server for shard 1 never end up
resulting in documents saved in shard 2?
Michael Della Bitta
Appinions
18 East 41st Street, 2nd
11 matches
Mail list logo
