I'm running into the same issue. I've set autoSoftCommit and autoCommit but
the speed at which docs are indexed seems to be inconsistent with the
settings. I have lowered the autoCommit to a minute but it still takes a
few minutes for docs to show after indexing. Soft commit settings also seem
to h
gt; 2> you’ll get some error report from somewhere telling you that Solr is
> broken because it isn’t accepting documents for update ;)
>
> > On Sep 28, 2020, at 9:01 AM, Mr Havercamp wrote:
> >
> > Thanks Eric. My knowledge is fairly limited but 1) sounds feasible. Some
>
old def because merging saw seg1 first. Then
> sometime later seg3 (new def) merges with seg10 and the data mysteriously
> comes back because that merge uses seg3 (new def) as a template for how the
> index “should” look.
>
> But I’ve never heard of Solr (well, Lucene actually) doin
Hi,
We're seeing strange behaviour when records have been committed. It doesn't
happen all the time but enough that the index is very inconsistent.
What happens:
1. We commit a doc to Solr,
2. The doc shows in the search results,
3. Later (may be immediate, may take minutes, may take hours), the
I am currently integrating Solr with a service which uses Zimbra for mail.
I have been tasked with importing inbox content into Solr and have opted to
use DIH.
Because this service adds/removes mailboxes, what would be the best
approach for managing a list of mailboxes for DIH?
My main concern is
ontinue to monitor to see if the problem reoccurs.
Thanks again
Hayden
On 12 September 2015 at 19:48, Shawn Heisey wrote:
> On 9/12/2015 10:51 AM, Mr Havercamp wrote:
> > Unfortunately, has never changed. The issue can take some
> time
> > to show itself although I think there we
Which leaves us with wondering what is
> unexpected in your setup. Everything you've shown us looks good, so I'm
> puzzled.
>
> Best,
> Erick
>
>
> On Fri, Sep 11, 2015 at 9:52 AM, Mr Havercamp
> wrote:
> > I'm wondering if the commitWithin is causin
gt; This is a fundamental part of Solr though, so it's
> virtually certain that there's some innocent-seeming
> thing you're doing that's causing this...
>
> Best,
> Erick
>
> On Fri, Sep 11, 2015 at 8:55 AM, Shawn Heise
I'm wondering if the commitWithin is causing issues.
On 11 September 2015 at 18:52, Mr Havercamp wrote:
> Thanks for the suggestions. No, not using MERGEINDEXES nor
> MapReduceIndexerTool.
>
> I've pasted the XML in case there is something broken there (cut
> d
Hi Shawn
Thanks for your response.
fieldType def:
It is not SolrCloud.
Cheers
Hayden
On 11 September 2015 at 16:35, Shawn Heisey wrote:
> On 9/11/2015 8:25 AM, Mr Havercamp wrote:
> > Running 4.8.1. I am experiencing the same problem where I get duplic
Running 4.8.1. I am experiencing the same problem where I get duplicates on
index update despite using overwrite=true when adding existing documents.
My duplicate ratio is a lot higher with maybe 25 - 50% of records having
duplicates (and as the index continues to run the duplicates increase from
2
I am using Apache Solr 3.6.
I have been playing around with the idea of providing a "similar" search
in the same way Google provides a link against some results with the
ability to search for pages similar to the current result: E.g.
related:lucene.apache.org/solr/ apache solr
One method I t
check
components. Then you can send a request to one particular request
handler and the corresponding spell check component will return its
response.
On Thu, Sep 5, 2013 at 11:29 PM, Mr Havercamp wrote:
I currently have multiple spellchecks configured in my solrconfig.xml to
handle a variety of diff
I currently have multiple spellchecks configured in my solrconfig.xml to
handle a variety of different spell suggestions in different languages.
In the snippet below, I have a catch-all spellcheck as well as an
English only one for more accurate matching (I.e. my schema.xml is set
up to captur
I'm interested to know if there is a way to have Solr index its own
logs, in particular the logging of queries.
One project that showed promise was Sogger but I believe the developer
is working more closely with LogStash which uses ElasticSearch so my
guess is that the Sogger project is no lon
I have been playing around with the new suggestion feature in Solr 3.1
but have run into issues when using spellcheck.q.
I initiate the suggestion handler using:
http://www.domain.tld:8983/solr/suggest?spellcheck.build=true
http://www.domain.tld:8983/solr/suggest?spellcheck.reload=true
And the
16 matches
Mail list logo
