1) Anytime the Lucene Jar is updated, a notation is added to CHANGES.txt,
and the svn commit message should have the specifics on the jar like
this..
http://svn.apache.org/viewvc/lucene/solr/trunk/lib/lucene-core-2.4-dev.jar?view=log
2) the Solr Admin screen is just displaying what's listed in
Thanks a lot!!
Regards Erik
On Sep 1, 2008, at 1:51 PM, Erik Holstad wrote:
I thought that 8983 only was for the web interface, but that
is not the case?
Solr's services and web interface all operate from a single web
application. It's all one port for the example configuration, 8983.
Note that in some cases, like S
Thanks for the quick reply!
I thought that 8983 only was for the web interface, but that
is not the case?
Regards Erik
Erik - is the issue the Solr URL? The example you pointed to uses
port 8080, but Solr's example configuration uses port 8983.
Erik
On Sep 1, 2008, at 1:15 PM, Erik Holstad wrote:
Hi!
I'm trying to use solrj to work with solr and tried the example on
http://e-mats.org/tag/solrj/
but
Hi!
I'm trying to use solrj to work with solr and tried the example on
http://e-mats.org/tag/solrj/
but I get this error message:
Sep 1, 2008 9:49:09 AM org.apache.commons.httpclient.HttpMethodDirector
executeWithRetry
INFO: I/O exception (java.net.ConnectException) caught when processing
request:
How many documents do you have in your index? How many unique
queries per day, bot and human? What are your cache hit ratios?
Maybe you can increase the size of the caches and not worry about
it. Search engine position is important. Have marketing pay for
the extra memory (I'm not kidding).
Sendi
Apart from hacking the internals, there's nothing inside Solr which will let
you do that. EHCache is for application layer caches, Solr is an external
server so it can't know about your application. I think that over a period
of time, the caches will be back to normal (through user-generated reques
I get what you are trying to do yes, googlebot essentially fills
up the cache with edge cases.
There is nothing in solr to prevent using the cache for some queries
and not others -- given the way parts of solr works, it is a bad idea
to turn off caching completly (a Document my be retr
Maybe I was a bit unclear, let me try with other words.
I didn't have the statistic-page in mind. All I care about is that I don't
want a massive amount of bot-generated queries affect the internal
statistics of the caches in Solr. If caching would be possible to switch
off for bot-queries the cac
If you are serving cached queries to the bot, what would be the benefit of
suppressing those queries from figuring into the cache statistics page?
On Mon, Sep 1, 2008 at 2:46 PM, Tobias Hill <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> Is there any way to suppress that a certain query gets added to t
Hi all,
Is there any way to suppress that a certain query gets added to the
caches (or is allowed to affect cache statistics) in Solr?
*Reason:* We have a very search oriented website. The SEO-aspects
of the site is also important why almost the entire search-space is
traversable for indexing bot
That wiki page is purely an idea proposal at this time, not a feature
of Solr (yet or perhaps ever).
Erik
On Sep 1, 2008, at 2:23 AM, sanraj25 wrote:
Hi
I read the doument on http://wiki.apache.org/solr/IndexPartitioning
Now i want partition my solr index into two. Based on
13 matches
Mail list logo
