Hi,

1. openSearcher (autoCommit)
According to the Apache Solr reference, "autoCommit/openSearcher" is set to 
false by default.

https://cwiki.apache.org/confluence/display/solr/UpdateHandlers+in+SolrConfig

But on Solr v4.8.1, if "openSearcher" is omitted from the autoCommit config, 
new searchers are opened and warmed post auto-commits. Is this behaviour 
intended or the wiki wrong?

2. openSearcher and other default commit settings
From previous posts, I know it's not possible to disable commits completely in 
Solr config (without coding). But is there a way to configure the default 
settings of hard/explicit commits for the update handler? If not it makes sense 
to have a configuration mechanism. Currently, a simple commit call seems to be 
hard-wired with the following options:

.. 
commit{,optimize=false,openSearcher=true,waitSearcher=true,expungeDeletes=false,softCommit=false,prepareCommit=false}

There's no server-side option, e.g. to set "openSearcher=false" as default or 
"invariant" (cf. searchHandler) to prevent new searchers from opening.

I found that at times it is necessary to have better server- or 
infrastructure-side controls for update/commits, especially in agile teams. 
Client/UI developers do not necessarily have complete Solr knowledge. 
Unintended commits from misbehaving client-side updates may be norm (e.g. 10 
times per minute!).

Regards,

Boon


-----
Boon Low
Search Engineer,
DCT Family History




______________________________________________________________________
"brightsolid" is used in this email to mean brightsolid online technology
limited.

Email Disclaimer

This message is confidential and may contain privileged information. You should
not disclose its contents to any other person. If you are not the intended
recipient, please notify the sender named above immediately. It is expressly
declared that this e-mail does not constitute nor form part of a contract or
unilateral obligation. Opinions, conclusions and other information in this
message that do not relate to the official business of brightsolid shall be
understood as neither given nor endorsed by it.
______________________________________________________________________
This email has been scanned by the brightsolid Email Security System. Powered by
McAfee.
______________________________________________________________________

Reply via email to