I am running off of a snapshot taken 5/3/2012 of solr 4.0 and am
noticing some issues around deleteById when a commitWithin parameter
is included using SolrJ, specifically commit isn't executed. If I
later just call commit on the solr instance I see the item is deleted
though. Is anyone aware if
On Thu, Jul 5, 2012 at 4:29 PM, Jamie Johnson jej2...@gmail.com wrote:
I am running off of a snapshot taken 5/3/2012 of solr 4.0 and am
noticing some issues around deleteById when a commitWithin parameter
is included using SolrJ, specifically commit isn't executed. If I
later just call commit
Thanks for the fast response. Yeah, it could be in either place
either SolrJ or on the Server side.
On Thu, Jul 5, 2012 at 4:47 PM, Yonik Seeley yo...@lucidimagination.com wrote:
On Thu, Jul 5, 2012 at 4:29 PM, Jamie Johnson jej2...@gmail.com wrote:
I am running off of a snapshot taken
Ok, so some more context, hopefully this is useful.
I didn't think this was a SolrCloud issue but it appears to be. I
have a simple 2 shard set up, I add 1 document which goes to shard 1.
I then issue a delete to shard 2. The delete gets there and I see the
commit eventually being run in the
Thanks Yonik, glad that it is not an issue on Trunk. I'll see if our
group is interested in updating now to take advantage of this. In the
mean time we just issue a commit after we do deletes and that seems to
be a sufficient workaround.
On Thu, Jul 5, 2012 at 6:05 PM, Yonik Seeley
Our application involves lots of live index updates with mixed priority. A
few updates are very important and need to be in the index promptly, while
we also have a great deal of updates which can be dealt with lazily.
The documentation for the commitWithin leaves some room for interpretation.
On Wed, Oct 21, 2009 at 11:58 AM, Jacob Elder jel...@locamoda.com wrote:
Our application involves lots of live index updates with mixed priority. A
few updates are very important and need to be in the index promptly, while
we also have a great deal of updates which can be dealt with lazily.
