What you indicated here is for a different purpose, is it not? I already do
something similar with my 'q'. For example a sample query logged in
'catalina.out' looks like
webapp=/search path=/select
params={rows=15start=0q=(+(content:umts)+OR+(title:umts)^2+OR+(urltext:umts)^2)}
when the search
I tried hl.maxAnalyzedChars=500 but still the same issue. I get OOM for
row size 20 only.
-Original Message-
From: Otis Gospodnetic [mailto:otis_gospodne...@yahoo.com]
Sent: Thursday, April 16, 2009 9:56 PM
To: solr-user@lucene.apache.org
Subject: Re: OutofMemory on Highlightling
Hi,
On Fri, Apr 17, 2009 at 11:32 AM, ashokc ash...@qualcomm.com wrote:
What we need is for the white_papers pdfs to be boosted, but if and only
if such doucments are valid results to the search term in question. How
would I write my above 'q' to accomplish that?
Thanks for explaining in
I have now :-)
Thanks , missed that in the Wiki.
Ruben
On Apr 16, 2009, at 7:10 PM, Noble Paul നോബിള്
नोब्ळ् wrote:
did you try the deletedPkQuery?
On Thu, Apr 16, 2009 at 7:49 PM, Ruben Chadien ruben.chad...@aspiro.com
wrote:
Hi
I am new to Solr, but have been using Lucene for a
if you are querying using a http request you can add these two parameters:
facet=true
facet.field=field_for_faceting
and optionally this one to set the max number of facets:
facet.limit=facet_limit
I don't know if it's what you need...
On Fri, Apr 17, 2009 at 6:17 AM, Sajith Weerakoon
It is fixed in the trunk
On Thu, Apr 16, 2009 at 10:47 PM, Allahbaksh Asadullah
allahbaks...@gmail.com wrote:
Thanks Noble.Regards,
Allahbaksh
2009/4/16 Noble Paul നോബിള് नोब्ळ् noble.p...@gmail.com
On Thu, Apr 16, 2009 at 10:34 PM, Allahbaksh Asadullah
allahbaks...@gmail.com wrote:
Hello,
I am searching for a way to use the Lucene MultiFieldQueryParser in my
SOLR Installation.
Is there a chance to change the solrQueryParser ?
In my old Lucene Setting I used to combine many different types of
QueryParser in my Querry...
Or is there a chance to get
Hi Christophe,
Did you find a way to fix up your problem, cuz even with replication will
have this problem, lot of update means clear cache and manage that.
I've the same issue, I just wondering if I won't turn off servers during
update ???
How did you fix that ?
Thanks,
sunny
christophe-2
Think there's no search handler that uses MultiFieldQueryParser in Solr. But
check DismaxRequestHandler, probably will do the job. Yo can specify all the
fields where you want to search in and it will build the query using boolean
queries. It includes also many more features:
Marc Sturlese schrieb:
Think there's no search handler that uses MultiFieldQueryParser in Solr. But
check DismaxRequestHandler, probably will do the job. Yo can specify all the
fields where you want to search in and it will build the query using boolean
queries. It includes also many more
Marc Sturlese schrieb:
Think there's no search handler that uses MultiFieldQueryParser in Solr. But
check DismaxRequestHandler, probably will do the job. Yo can specify all the
fields where you want to search in and it will build the query using boolean
queries. It includes also many more
Hi Noble.
Thank you very much. I will download the latest solr nightly build.
Please note this is the another problem which I think is bug.
I am trying out load balancing feature in Solr 1.4 using LBHTTPSolrServer.
Below is setup
I have three solr server. A, B and C.
Now the problem is if I
Well dismax has a q.alt parameter where you can specify a query in lucene
sintax. The query must be empty to use q.alt:
http://.../select?q=q.alt=phone_number:1234567
This would search in the field phone_number independly of what fields you
have configured in teh dismax.
Another way would be to
Marc Sturlese schrieb:
Well dismax has a q.alt parameter where you can specify a query in lucene
sintax. The query must be empty to use q.alt:
http://.../select?q=q.alt=phone_number:1234567
This would search in the field phone_number independly of what fields you
have configured in teh dismax.
Marc Sturlese schrieb:
The only problem I found with q.alt is that it doesn't allow highlighting (or
at least it doesn't showed it for me). If you find out how to do it let me
know.
I use highlighting only with the normal querry !
My q.alt is *.*
But its really sad that the dismax dont support
The only problem I found with q.alt is that it doesn't allow highlighting (or
at least it doesn't showed it for me). If you find out how to do it let me
know.
Thanks!
Kraus, Ralf | pixelhouse GmbH wrote:
Marc Sturlese schrieb:
Well dismax has a q.alt parameter where you can specify a query
Hey there,
I have seen the new feature of EventListeners of DIH in trunk.
dataConfig
document onImportStart =com.FooStart onImportEnd=comFooEnd
/document
/dataConfig
These events are called at the begining and end of the whole indexing
process or at the begining and end of indexing just a
these are for the beginning and end of the whoke indexing process
On Fri, Apr 17, 2009 at 7:38 PM, Marc Sturlese marc.sturl...@gmail.com wrote:
Hey there,
I have seen the new feature of EventListeners of DIH in trunk.
dataConfig
document onImportStart =com.FooStart onImportEnd=comFooEnd
Hey Erik,
I also checked the index using luke and the index shows that
the terms are indexed as they should have been. So that implies that
something is wrong with the querying only and the results are not getting
retrieved.(As i said earlier even the parsed query is the way it
I would also include the -XX:+HeapDumpOnOutOfMemoryError option to get
a heap dump when the JVM runs out of heap space.
On Thu, Apr 16, 2009 at 9:43 PM, Bryan Talbot btal...@aeriagames.comwrote:
If you're using java 5 or 6 jmap is a useful tool in tracking down memory
leaks.
We are currently trying to do the same thing. With the patch unaltered we
can use fq as long as collapsing is turned on. If we just send a normal
document level query with an fq parameter it blows up.
Additionally, it does not appear that the collapse.facet option works at
all.
--
Jeff
In trying to understand the various options for WordDelimiterFilterFactory, I
tried setting all options to 0.
This seems to prevent a number of words from being output at all. In particular
can't and 99dxl don't get output, nor do any wods containing hypens. Is
this correct behavior?
Here is
Seems like we could handle this 2 ways... leave out the field if it's
not defined in the schema, or include it and write it out as a string.
I think either would probably be more useful than throwing an error
(which isn't really a request error but rather a schema/indexing
error).
Thoughts?
: level one#
: level one#level two#
: level one#level two#level three#
:
: Trying to find the right combination of field type and query to get the
: desired results. Saw some previous posts about hierarchal facets which helped
: in the generating the right query but having an issue using the
: How would I set up SNMP monitoring of my Solr server? I've done some
: searching of the wiki and Google and have come up with a blank. Any
: pointers?
it depends on what you want to monitor. if you just want to know what the
JVM is running, this should be fairly easy...
if you wnat to
OK, we've got 3 people... that's enough for a party? :)
Surely there must be dozens more of you guys out there... c'mon,
accelerate your knowledge! Join us in Seattle!
On Thu, Apr 16, 2009 at 3:27 PM, Bradford Stephens
bradfordsteph...@gmail.com wrote:
Greetings,
Would anybody be willing to
The only thing that comes to mind is running Solr under a profiler (e.g.
YourKit) and figuring out which objects are not getting cleaned up and who's
holding references to them.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
From: David Baker
httpClient.getHttpConnectionManager().closeIdleConnections();
--Noble
On Sat, Apr 18, 2009 at 1:31 AM, Rakesh Sinha rakesh.use...@gmail.com wrote:
When we instantiate a commonshttpsolrserver - we use the following method.
CommonsHttpSolrServer server = new
28 matches
Mail list logo
