I sent commit=true&optimize=true as a separate command but nothing
happened. Will try with additional options
waitFlush=false&waitSearcher=false&expungeDeletes=true
I wonder why the DIH admin GUI (debug.jsp) is not sending optimize=true
together with full-import ?
Regards,
Bernd
Am 24.01.2011
I think optimize only ever gets done when either a full-import or
delta-import is done. You could optimize the "normal" way though see:
http://wiki.apache.org/solr/UpdateXmlMessages
- Espen
On Mon, Jan 24, 2011 at 8:05 AM, Bernd Fehling
wrote:
>
> Is there a difference between sending optimize=t
Is there a difference between sending optimize=true with
the full-import command or sending optimize=true as
a separate command after finishing full-import?
Regards,
Bernd
Am 23.01.2011 02:18, schrieb Espen Amble Kolstad:
> Your not doing optimize, I think optimize would delete your old index.
Your not doing optimize, I think optimize would delete your old index.
Try it out with additional parameter optimize=true
- Espen
On Thu, Jan 20, 2011 at 11:30 AM, Bernd Fehling
wrote:
> Hi list,
>
> after sending full-import=true&clean=true&commit=true
> Solr 4.x (apache-solr-4.0-2010-11-24_09-
Looks like this is a bug and I should write a jira issue for it?
Regards
Bernd
Am 20.01.2011 11:30, schrieb Bernd Fehling:
> Hi list,
>
> after sending full-import=true&clean=true&commit=true
> Solr 4.x (apache-solr-4.0-2010-11-24_09-25-17) responds with:
> - DataImporter doFullImport
> - Direc
Hi list,
after sending full-import=true&clean=true&commit=true
Solr 4.x (apache-solr-4.0-2010-11-24_09-25-17) responds with:
- DataImporter doFullImport
- DirectUpdateHandler2 deleteAll
...
- DocBuilder finish
- SolrDeletionPolicy.onCommit: commits:num=2
- SolrDeletionPolicy updateCommits
- SolrIn
