Thanks Yonik and Otis,
I noticed from the log (snapinstaller.log) the following when the slave
attempts to perform snapinstaller:
2007/10/29 10:30:02 started by 1001
2007/10/29 10:30:02 command: /opt/solr/bin/snapinstaller
2007/10/29 10:30:02 installing snapshot
I think about using FunctionQuery. But as I understand, the
FunctionQuery actually overrides the default similarity function. Am I
right? If I am, this means that I cannot access the similarity value,
which is necessary, because I want it have a major influence on the
final score. I eventually
Snapinstaller uses commit to notify Solr to open a new Searcher. Is there
anything in the commit log which shows why the commit failed?
Bill
On 10/29/07, Karen Loughran [EMAIL PROTECTED] wrote:
Thanks Yonik and Otis,
I noticed from the log (snapinstaller.log) the following when the slave
Hi,
I've been trying to get MoreLikeThis running in Solr 1.2, so far without
success. Since there is no mention of any special installation steps in
the Wiki, I had assumed that it was built into 1.2, but that does not
seem to be the case. So now I've downloaded the patches from SOLR-69,
and
Hi Bill, yes, the commit.log shows the following when snapinstaller fails from
the cronjob:
2007/10/29 15:03:03 started by 1001
2007/10/29 15:03:03 command: /opt/solr/bin/commit
2007/10/29 15:03:03 failed to connect to Solr server at
http://localhost:8080/solr/update
2007/10/29 15:03:03 commit
OK, I've mostly figured it out. Patching leaves me with one rejection:
apache-solr-1.2.0$ patch -p0 SOLR-69.patch
(Stripping trailing CRs from patch.)
patching file src/java/org/apache/solr/request/StandardRequestHandler.java
Hunk #2 FAILED at 75.
Hunk #3 succeeded at 150 (offset 10 lines).
Hunk
Hi Bill, just noticing that in the first instance it states started by 1001
and in the 2nd it reports started by autodeploy.
The user id of autodeploy is in fact 1001. ?
Karen
On Monday 29 October 2007 15:07:55 Karen Loughran wrote:
Hi Bill, yes, the commit.log shows the following when
the rejected code appears to be non-vital, so I've just left it out.
Since Solr 1.2 is based on Lucene 2.1, I've used the
lucene-query.2.1.1-dev.jar to compile (after fixing the DEFALT/DEFAULT
typo), and MLT seems to work. Is that the correct procedure? If so, I'll
update the wiki
On Thu, 2007-10-25 at 10:48 -0400, Yonik Seeley wrote:
On 10/25/07, Max Scheffler [EMAIL PROTECTED] wrote:
Is it possible that the prefix-processing ignores the filters?
Yes, It's a known limitation that we haven't worked out a fix for yet.
The issue is that you can't just run the prefix
Hi,
I have written code using the Embedded API from SOLR.
Now there is the requirement for access to a remote server, so I would
need to use HTTP Post.
So is it possible to wrap Embedded API into HTTP Post calls?
If not, how difficult would it be in general to translate the example at
If you need to allow HTTP access to solr, then just use standard solr
with your embedded stuff in a custom request handler (or something).
Any other path, you will be re-inventing many wheels.
If at all possible, I reccomend checking out:
http://wiki.apache.org/solr/Solrj
this is nice because
On 10/29/07, Martin Grotzke [EMAIL PROTECTED] wrote:
On Thu, 2007-10-25 at 10:48 -0400, Yonik Seeley wrote:
On 10/25/07, Max Scheffler [EMAIL PROTECTED] wrote:
Is it possible that the prefix-processing ignores the filters?
Yes, It's a known limitation that we haven't worked out a fix for
Hello all,
I have an application running based on lucene 2.2. Maybe it is not the
most typical usage of Lucene, the main features regarding lucene are:
- I use many indexes, tens or hundreds of them(all contain the same
structure of fields etc),and the number of indexes grows with time.
The
On Mon, 2007-10-29 at 13:31 -0400, Yonik Seeley wrote:
On 10/29/07, Martin Grotzke [EMAIL PROTECTED] wrote:
On Thu, 2007-10-25 at 10:48 -0400, Yonik Seeley wrote:
On 10/25/07, Max Scheffler [EMAIL PROTECTED] wrote:
Is it possible that the prefix-processing ignores the filters?
Hello,
how can I permanently change the loglevel of SOLR output to WARNING? I
know it can be done from /solr/admin/logging.jsp but that change is
forgotten as soon as the server is restarted. I assume I can specify
the log level somewhere in some config file, but where? For now I'm
using Solr
Hi Christopher,
Thanks for the offer to share the details! All of the items really look
interesting and I'd love to know more about what you found about each of them.
At this point in time I'm mostly interested in performance, so how about these:
Indexing performance gains,Size of index v's
16 matches
Mail list logo
