Otis
Did you see Boss's answer to a similar question about an hour after your
post?
On Dec 9, 2011 2:19 PM, "Otis Gospodnetic"
wrote:
> Hi,
>
> Is there a reason why we have the "lucene" parser baked into Join?
> Is there a way to use (e)DisMax with Join?
>
> For example, when I do this:
>
>
Did i write wt? Oh dear. The q and w are too close =)
> Markus,
>
> Its not wt its qt, wt for response type,
> Also qt is not for Query Parser its for Request Handler ,In solrconfig.xml
> there are many Request Handlers can be Defined using "dismax" Query Parser
> Or Using "lucene" Query Parser.
>
Markus,
Its not wt its qt, wt for response type,
Also qt is not for Query Parser its for Request Handler ,In solrconfig.xml
there are many Request Handlers can be Defined using "dismax" Query Parser
Or Using "lucene" Query Parser.
If you want to change Query parser then its "defType" parameter
Erick,
The wt parameter does not specifiy the parser but the request handler to use.
Except the confusion between parser and request handler you're entirely right.
Cheers
On Tuesday 18 January 2011 17:37:41 Erick Erickson wrote:
> If you're trying to get to a dismax parser (named "dismax" in
>
If you're trying to get to a dismax parser (named "dismax" in
solrconfig.xml),
you need to specify qt=dismax. NOTE: the Wiki is a bit confusing on this
point, the fact that the dismax parser is *named* dismax in the
solrconfig.xml
file is coincidence, you could name it "erick" and specify qt=erick
with dismax you must specifiy fields to query upon in the qf parameter and the
value for which you want to search through those fields in q.
defType=lucene&q=poi_id:3
defType=dismax&q=3&qf=poi_id
See the DisMaxQParser wiki for more
On Tuesday 18 January 2011 15:50:34 Tri Nguyen wrote:
> Hi,
>
Is this at the broker or the shard? If it is at the shard, does the
log record the full stack trace of the parsing exception?
Do simpler function queries work?
On Sun, Apr 11, 2010 at 5:57 PM, Shawn Heisey wrote:
> Adding it to the main core looks like it works, without the dismax handler
> even
Adding it to the main core looks like it works, without the dismax
handler even present in the live core config. It won't take the bf
value that I described, though.
recip(ms(NOW,product(post_date,1000)),3.17e-11,1,1)
This spits an error:
Problem accessing /solr/main/select. Reason:
und
The query is at the broker level, and is included in the distributed
search. You can't place in the shard, because the distributed search
shortcuts the query handlers (I think).
On 4/11/10, Shawn Heisey wrote:
> I am using a setup where I have specified the shards parameter in a
> broker called "
aw, of course... the standard query parameters can be used with
dismax... sorry for the silly question!
- bram
--
http://www.freesound.org
http://www.smartelectronix.com
http://www.musicdsp.org
On Sun, Jun 29, 2008 at 11:59 AM, climbingrose <[EMAIL PROTECTED]> wrote:
> Hi Bram,
> You can use
Hi Bram,
You can use filter query (fq) to limit your results:
fq=tag:sometag&q=user_input_here
Have a look at dismax and standard query documentation on the wiki.
On Sun, Jun 29, 2008 at 6:49 PM, Bram de Jong <[EMAIL PROTECTED]> wrote:
> hello all,
>
> I would like to combine the DisMaxReques
On 12/2/06, Stephanie Belton <[EMAIL PROTECTED]> wrote:
: more specificly, you are putting your entire search in quotes, which is
: causing it to be treated as a single searchable entity across several
: fields -- a single DisjunctionMaxQuery, instead of multiple disjunctions
: wrapped in a boole
: more specificly, you are putting your entire search in quotes, which is
: causing it to be treated as a single searchable entity across several
: fields -- a single DisjunctionMaxQuery, instead of multiple disjunctions
: wrapped in a boolean. When that quoted chunk of text is analyzed by your
:
Thank you for your message Yonik, that was very helpful. I didn't have much
luck with the SnowballPorterFilterFactory so I wrote my own factory last night
and as you said it gives me much more flexibility. Here it is for anyone who's
interested:
package myApp;
import org.apache.lucene.analysis
: You are including the russian stemmed fields in the dismax query, and
: the analysis of those fields discards numbers, hence 1970 is ignored,
: right? Either querying only the literals, or fixing the stemmed text
: to not discard numbers may help (or get you further along at least).
more speci
On 11/30/06, Stephanie Belton <[EMAIL PROTECTED]> wrote:
I am using Solr to index and search documents in Russian. I have successfully
set up the RussianAnalyzer but found that it eliminates some tokens such as
numbers.
You can get better control (and avoid having numbers removed)
by using To
16 matches
Mail list logo
