On 11/6/2015 8:39 PM, Yonik Seeley wrote:
> On Fri, Nov 6, 2015 at 10:20 PM, Shawn Heisey wrote:
>> Is there a decent API for getting uniqueKey?
> Not off the top of my head.
> I deeply regret making it configurable and not just using "id" ;-)
By poking around in the admin
On Wed, Nov 4, 2015 at 3:36 PM, Shawn Heisey wrote:
> The specific index update that fails during the optimize is the SolrJ
> deleteByQuery call.
deleteByQuery may be the outlier here... we have to jump through extra
hoops internally because we don't know which documents it
It is pretty handy, though. Great for expunging docs that are marked deleted or
are expired.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Nov 6, 2015, at 5:31 PM, Alexandre Rafalovitch wrote:
>
> Elasticsearch removed
Elasticsearch removed deleteByQuery from the core all together.
Definitely an outlier :-)
Solr Analyzers, Tokenizers, Filters, URPs and even a newsletter:
http://www.solr-start.com/
On 6 November 2015 at 20:18, Yonik Seeley wrote:
> On Wed, Nov 4, 2015 at 3:36 PM, Shawn
On Fri, Nov 6, 2015 at 10:20 PM, Shawn Heisey wrote:
> Is there a decent API for getting uniqueKey?
Not off the top of my head.
I deeply regret making it configurable and not just using "id" ;-)
-Yonik
On Sat, Nov 7, 2015 at 9:09 AM, Yonik Seeley wrote:
> On Fri, Nov 6, 2015 at 10:20 PM, Shawn Heisey wrote:
> > Is there a decent API for getting uniqueKey?
>
> Not off the top of my head.
> I deeply regret making it configurable and not just using "id"
On 11/6/2015 6:18 PM, Yonik Seeley wrote:
> On Wed, Nov 4, 2015 at 3:36 PM, Shawn Heisey wrote:
>> The specific index update that fails during the optimize is the SolrJ
>> deleteByQuery call.
>
> deleteByQuery may be the outlier here... we have to jump through extra
> hoops
On 11/6/2015 2:23 PM, Pushkar Raste wrote:
> I may be wrong but I think 'delete' and 'optimize' can not be executed
> concurrently on a Lucene index
It certainly is looking that way. After discussing it with Hoss on IRC,
I tried a manual test where I started an optimize and then did some
"add"
I may be wrong but I think 'delete' and 'optimize' can not be executed
concurrently on a Lucene index
On 4 November 2015 at 15:36, Shawn Heisey wrote:
> On 11/4/2015 1:17 PM, Yonik Seeley wrote:
> > On Wed, Nov 4, 2015 at 3:06 PM, Shawn Heisey
> wrote:
On 11/4/2015 1:17 PM, Yonik Seeley wrote:
> On Wed, Nov 4, 2015 at 3:06 PM, Shawn Heisey wrote:
>> I had understood that since 4.0, Solr (Lucene) can continue to update an
>> index even while that index is optimizing.
> Yes, that should be the case.
>
>> I have discovered in
I had understood that since 4.0, Solr (Lucene) can continue to update an
index even while that index is optimizing.
I have discovered in the logs of my SolrJ index maintenance program that
this does not appear to actually be true. My dev index is running Solr
5.2.1 and my production indexes are
On Wed, Nov 4, 2015 at 3:06 PM, Shawn Heisey wrote:
> I had understood that since 4.0, Solr (Lucene) can continue to update an
> index even while that index is optimizing.
Yes, that should be the case.
> I have discovered in the logs of my SolrJ index maintenance program
12 matches
Mail list logo