kinda data u have and what is your requirement.
> Date: Thu, 7 Aug 2008 15:40:59 -0700> From: [EMAIL PROTECTED]> To:
> solr-user@lucene.apache.org> Subject: Re: How do I configure commit to run
> after updates> > Thank you so much everyone.> > This community is rea
ich is not
> right. auto committing is the way to go and like fuad said, committing
> nightly is the right way to do it IMO too.
>
>
>
>> Date: Thu, 7 Aug 2008 15:13:18 -0700> From: [EMAIL PROTECTED]> To:
>> solr-user@lucene.apache.org> Subject: Re: How do I co
L PROTECTED]> To:
> solr-user@lucene.apache.org> Subject: Re: How do I configure commit to run
> after updates> > > Okay... so this all makes sense, and I can sorta make it
> work, however,> > the commit is never run by itself when the index is
> updated. I have to
ny docs are pending
> commit.
>
>> Date: Thu, 7 Aug 2008 14:53:02 -0700> From: [EMAIL PROTECTED]> To:
>> solr-user@lucene.apache.org> Subject: Re: How do I configure commit to run
>> after updates> > Hi folks,> > Thanks for the replies. I think I'm get
Oddly, I have 10 docs in the index, as indicated by NumDocs and MaxNumDocs
However, in the Update Handlers section:
commits : 0
autocommits : 0
optimizes : 0
docsPending : 0
All 0s...
Any ideas?
The only idea: you restarted server after 'commit' was issued; you
didn't add any new docs
Okay... so this all makes sense, and I can sorta make it work, however,
the commit is never run by itself when the index is updated. I have to
manually call the commit script from the command line to get it to happen.
Jacob, 'commit' is expensive (you will loose SOLR caches, and etc.)...
'com
I'm using the PHP library provided in JIRA, and I am calling commit()
from it. Unfortunately, I can't see if it is working or not...
Yes, you can't see changes immediately - it requires some time for new
Searcher to open and to warm SOLR caches, several minutes-hours
depending on index si
of how many docs are pending
> commit.
>
>> Date: Thu, 7 Aug 2008 14:53:02 -0700> From: [EMAIL PROTECTED]> To:
>> solr-user@lucene.apache.org> Subject: Re: How do I configure commit to run
>> after updates> > Hi folks,> > Thanks for the replies.
Look at the update handlers section of the Solr stats page. I guess the url is
/admi/stats.jsp. This woudld give u an idea of how many docs are pending commit.
> Date: Thu, 7 Aug 2008 14:53:02 -0700> From: [EMAIL PROTECTED]> To:
> solr-user@lucene.apache.org> Subject: Re: How
Hi folks,
Thanks for the replies. I think I'm getting closer now.
I'm using the PHP library provided in JIRA, and I am calling commit()
from it. Unfortunately, I can't see if it is working or not...
I'm trying to get logging working in jetty for a multi-instance server,
but that's a separate n
Or time.
1 1
> Date: Thu, 7 Aug 2008 18:42:30 -0300> From: [EMAIL PROTECTED]> To:
> solr-user@lucene.apache.org> Subject: Re: How do I configure commit to run
> after updates> > You can configure the autocommit feature in solrconfig
You can configure the autocommit feature in solrconfig.xml to get commit to
work from time to time or based in the number of documents added to your
index.
2008/8/7 Jacob Singh <[EMAIL PROTECTED]>
> Hi,
>
> I'm using the XML based update interface, and feeding requests to update
> the index via j
I'm not exactly a long-time user of Solr yet so forgive me if I'm
missing something really obvious here... but, if I'm not mistaken, you
just add to the end of your update XML. This is how I've
done all of my commits, I wasn't even aware there was a CLI method to
this.
I would worry abo
13 matches
Mail list logo
