Hi,
We personally use dismax as a more basic search endpoint so that users who
are not aware for lucene syntax don't end up using special keywords or
chars. which might affect their search queries.
The switch between dismax and edismax is triggered by an advanced get param.
I imagine there
Question in general for the community :
what is the dismax capable of doing that the edismax is not ?
Is it really necessary to keep both of them or the dismax could be
deprecated ?
Cheers
-
---
Alessandro Benedetti
Search Consultant, R&D Software Engineer, Director
Sease Ltd. -
Wouldn't all of this depend entirely on the tokenizers used? I was talking
about phrases in a multi-token sense.
Regardless, I still think there should be similarity between dismax and
edismax for the commonly parameters. (Either extend the edismax logic to
dismax or vice versa)
Regards,
Sa
That would make sense.
Multi-term synonyms get into a weird case too. Should the single-term
words that have multi-term synonyms expand out? Or should the multi-term
synonyms that have single-term synonyms contract down and count as only a
single clause for pf2 or pf3.
On Tue, May 29, 2018 at 1
I don't have any hard position on this, It's ok to not build a phrase boost
if the input query is 1 term and it remains one term after the analysis for
one of the pf fields.
But if the term produces multiple tokens after query time analysis, I do
believe that building a phrase boost should be the
t balances the documents that have enough terms per mm and
documents that have enough terms in one field.
Elizabeth Haubert
On Tue, May 29, 2018 at 5:14 AM, Alessandro Benedetti
wrote:
> In my opinion, given the definition of dismax and edismax query parsers,
> they
> should
In my opinion, given the definition of dismax and edismax query parsers, they
should behave the same for parameters in common.
To be a little bit extreme I don't think we need the dismax query parser at
all anymore ( in the the end edismax is only offering more than the dismax)
Finally,
query parsing between dismax and edismax, but it was closed
since it required further discussion on whether this was intended or not.
I personally found adding phrasal boosts to single token queries very
non-intuitive and IMO dismax parser should be updated to apply phrasal
boosts to multi-token
ou.
Best,
Andrea
On 27/05/18 15:14, Sambhav Kothari wrote:
Hello,
I experienced a weird behaviour with dismax and edismax query parsers.
Dismax will include pf boosts when we query something that has just a
single word, edismax on the other hand will not include pf boosts.
The result is that a
Hello,
I experienced a weird behaviour with dismax and edismax query parsers.
Dismax will include pf boosts when we query something that has just a
single word, edismax on the other hand will not include pf boosts.
The result is that a dismax and an edismax handler with the same set of
defaults
Hi:
I have a question about edismax and dismax.
I'm using SOLR 6.3.0. Both types of query statements are the same, but the
results is differ.
Now there is such a document:
pj_title:word1 word2 word3
1. edismax
q=word1 word2&qf=pj_title&pf=pj_title&defType=edi
er queries, so perhaps I still have
it all wrong after all. But if it helps anybody at all in the future, I THINK
- large pinch of salt - the anatomy of a dismax and scored block join query in
the Solr Admin Console (note you'll have to encode a GET request) is like:
q=+{!dismax v=&qu
d be more than happy to. What goes around comes around!
>
> -Original Message-
> From: Alexandre Rafalovitch [mailto:arafa...@gmail.com]
> Sent: 21 November 2016 13:01
> To: solr-user
> Subject: Re: Combined Dismax and Block Join Scoring on nested documents
>
> A blog a
ovitch [mailto:arafa...@gmail.com]
Sent: 21 November 2016 13:01
To: solr-user
Subject: Re: Combined Dismax and Block Join Scoring on nested documents
A blog article about what you learned would be very welcome. These edge cases
are something other people could certainly learn from.
Share the knowledge f
> -Original Message-
> From: Mikhail Khludnev [mailto:m...@apache.org]
> Sent: 18 November 2016 12:58
> To: solr-user
> Subject: Re: Combined Dismax and Block Join Scoring on nested documents
>
> Hello Mike,
> Structured queries in Solr are way cumbersome.
> Start from:
&g
ember 2016 12:58
To: solr-user
Subject: Re: Combined Dismax and Block Join Scoring on nested documents
Hello Mike,
Structured queries in Solr are way cumbersome.
Start from:
q=+{!dismax v="skirt" qf="name"} +{!parent which=content_type:product score=min
v=childq}&childq=+i
ly stupid as I'm new to Solr. I am
> having an issue with scoring child documents in a block join query when
> including a dismax query. I'm actually a little unclear on whether or not
> that's a complete oxymoron, combining dismax and block join.
>
>
>
> Problem sta
Apologies if I'm doing something incredibly stupid as I'm new to Solr. I am
having an issue with scoring child documents in a block join query when
including a dismax query. I'm actually a little unclear on whether or not
that's a complete oxymoron, combining dismax and blo
Hi Andreas,
You are correct, no re-indexing required for autoGeneratePhraseQueries.
Ahmet
On Thursday, September 24, 2015 3:52 PM, Andreas Hubold
wrote:
Thank you, autoGeneratePhraseQueries did the job.
I assume that this setting just affects query generation and I don't
need to reindex af
Thank you, autoGeneratePhraseQueries did the job.
I assume that this setting just affects query generation and I don't
need to reindex after changing the field type accordingly. Is this correct?
BTW, I just found SOLR-3589 where the same issue was reported and fixed
for the edismax parser. It
Use fq
Bill Bell
Sent from mobile
> On Sep 23, 2015, at 1:00 PM, Andreas Hubold
> wrote:
>
> Hi,
>
> we're using Solr 4.10.4 and the dismax query parser to search across multiple
> fields. One of the fields is configured with a StandardTokenizer (type
> "text_general"). I set mm=100% to o
Hi Andreas,
Thats weird. It looks like mm calculation is done before the tokenization took
place.
You can try to set autoGeneratePhraseQueries to true
or replace dashes with white-spaces at client side.
Ahmet
On Wednesday, September 23, 2015 10:00 PM, Andreas Hubold
wrote:
Hi,
we're usin
Hi,
we're using Solr 4.10.4 and the dismax query parser to search across
multiple fields. One of the fields is configured with a
StandardTokenizer (type "text_general"). I set mm=100% to only get hits
that match all terms.
This does not seem to work for queries that are split into multiple
:
> Does anyone have a great tutorial for learning the solr query language,
> dismax and edismax?
> I've searched endlessly for one but I haven't been able to locate one that
> is comprehensive enough and has a lot of examples (that actually work!).
> I also tried
Does anyone have a great tutorial for learning the solr query language,
dismax and edismax?
I've searched endlessly for one but I haven't been able to locate one that
is comprehensive enough and has a lot of examples (that actually work!).
I also tried to use wildcards, logical operat
: I am starting to wonder whether the module giving finnish language support
: (lingsoft) might be the cause?
It's extremeley possible -- the details relaly matter when debugging
things like this.
Since i don't have any access to these custom plugins, i don't know what
they might be doing, or
Hello,
I am starting to wonder whether the module giving finnish language
support (lingsoft) might be the cause?
Like I earlier said I have inherited this project so my understanding of
all the bells and whistles is a bit limited.
Some selected parts from the schema.xml file:
...
: /solr/ftf/dismax/?q=libya
: &debugQuery=off
: &hl=true
: &start=
: &rows=10
: --
:
: I am trying to factor in created to the SCORE. (boost) I have tried a million
: ways to do this, no success. I know the dates are populating correctly because
: I can
Yes. Just try it with &debugQuery=on and you can see the parsed
form of the query.
Best
Erick
On Wed, Nov 2, 2011 at 6:20 PM, Jamie Johnson wrote:
> Is it possible to do Proximity queries using edismax? I saw I could
> do the following
>
> q="batman movie"&qs=100
>
> but I wanted to be able to
: ...is this perhaps a side effect of the new autoGeneratePhraseQueries
: option? ... you are explicitly specifying a quoted phrase, but
: maybe somehwere in the code path of the dismax parser that information is
: getting lost?
FWIW:
a) I just realized you said in your first message you were
Interesting, in the case where you use quotes...
: +
...
: "asuntojen hinnat"
: "asuntojen hinnat"
...there is one DisjunctionMaxQuery (expected) for the entire phrase,
but in the sub-clauses for each individual field the clauses coming from
your "_fi" fields are just building boolean
Is it possible to do Proximity queries using edismax? I saw I could
do the following
q="batman movie"&qs=100
but I wanted to be able to handle queries like "batman movie"~100
I know I can do
text:"batman movie"~100
but I'm trying to do this without specifying a field. Is this possible?
tion that might be worth overcoming --
I'm sure my use case is not the only one where this could matter. Has anyone
given this any thought?
- Demian
> -Original Message-
> From: Erick Erickson [mailto:erickerick...@gmail.com]
> Sent: Thursday, October 27, 2011 8:21 AM
&g
> the user's original query, which then gets cleaned up bythe
> ICUFoldingFilterFactory and allows a match.
>
> The problem is that in my real-world application, which uses DisMax, neither
> of these solutions work. It appears that even though (if I understand
> correctly)
elimiterFilterFactory is returning ALTERNATIVE tokens, the DisMax
handler is combining them a way that requires all of them to match in an
inappropriate way... for example, here's partial debugQuery output for the
"exaMple" search using Dismax and solution #2 above:
"parsedq
On 10/23/2011 09:34 PM, Erick Erickson wrote:
Hmmm dismax is, indeed, different. Note that dismax doesn't respect
the default operator at all, so don't be mislead there.
Could you paste the debug output for both the queries? Perhaps something
will jump out at us.
Best
Erick
Thank you Erick. I'
Solr Specification Version: 1.4.0
Solr Implementation Version: 1.4.0 833479 - grantingersoll - 2009-11-06
12:33:40
Lucene Specification Version: 2.9.1
Lucene Implementation Version: 2.9.1 832363 - 2009-11-03 04:37:25
precisionStep="6" positionIncrementGap="0"/>
stored="false" omitNorms="true"
; a strict phrase query, just use standard request handler, not dismax.
>>
>> Otis
>>
>> Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
>> Lucene ecosystem search :: http://search-lucene.com/
>>
>>
>>> _
h :: http://search-lucene.com/
From: Hyttinen Lauri
To: solr-user@lucene.apache.org
Sent: Wednesday, October 19, 2011 5:02 AM
Subject: Dismax and phrases
Hello,
I've inherited a solr-lucene project which I continue to develop. This
particular SOLR (1.4.1) uses dismax for
not dismax.
Otis
Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
Lucene ecosystem search :: http://search-lucene.com/
>
>From: Hyttinen Lauri
>To: solr-user@lucene.apache.org
>Sent: Wednesday, October 19, 2011 5:02 AM
>Subject:
Hello,
I've inherited a solr-lucene project which I continue to develop. This
particular SOLR (1.4.1) uses dismax for the queries but I am getting
some results that I do not understand. Mainly when I search for two
terms I get some results however when I put quotes around the two terms
I get
Hello,
I think I have found something extrange with local params and edismax. If I do
querys like :
"params":{
"hl.requireFieldMatch":"true",
"hl.fragsize":"200",
"json.wrf":"callback0",
"indent":"on",
"hl.fl":"domicilio,deno",
"wt":"json",
"hl":"true",
Hmmm, let's see
1> your fieldtype definition from the schema.xml for the field in question
2> the results of adding &debugQuery=on to the URL
Otherwise it's kind of hard to know the details of your problem...
Also, have you looked at the analysis page for the field in question (from the
admin pag
>
>
> Cheers,
>
> David
>
>
>
> ___________
> If you reply to this email, your message will be added to the discussion
below:
>
http://lucene.472066.n3.nabble.com/Dismax-and-worddelimiterfilter-tp2732007p2732007.html
> To start a
Hi,
I am having some really strange issues matching "N61JQ-B2". If I had a
field "N61JQ-B2", and I wanted to match "N61JQ", "N61JQB2", "N61JQ-B2"
and "N61JQ B2" in dismax, what fieldtype should it have? My final
fallback is to use ngrams but that would impose a pretty large overhead,
since the
Hi Jonathan:
On Mar 7, 2011, at 8:33 AM, Jonathan Rochkind wrote:
> I use about that many qf's in Solr 1.4.1. It works. I'm not entirely sure
> if it has performance implications -- I do have searching that is somewhat
> slower then I'd like, but I'm not sure if the lengthy qf is a contributi
I use about that many qf's in Solr 1.4.1. It works. I'm not entirely
sure if it has performance implications -- I do have searching that is
somewhat slower then I'd like, but I'm not sure if the lengthy qf is a
contributing factor, or other things I'm doing (like a dozen different
facet.field
Hello:
I'm working on implementing a requirement where when a document is returned, we
want to pithily tell the end user why. That is, say, with five documents
returned, they may be so for similar or different reasons. These "reasons" are
the field(s) in which matches occurred. Some are more i
: I am trying to debug my queries and see how scoring is done. I have 6 cores
and
: send the quesy to 6 shards and it's dismax handler (with search on various
: fields with different boostings). I enable debug, and view source but I'm
unable
: to see the explanations. I'm returning ID and sco
Hi All,
I am trying to debug my queries and see how scoring is done. I have 6 cores and
send the quesy to 6 shards and it's dismax handler (with search on various
fields with different boostings). I enable debug, and view source but I'm
unable
to see the explanations. I'm returning ID and scor
I have finally figured out how to turn this off in Thunderbird 3:
Go to Tools, Options, Display, and turn off "Display emoticons as
graphics".
On 4/12/2010 12:04 PM, Shawn Heisey wrote:
On 4/12/2010 11:55 AM, Shawn Heisey wrote:
[NOW-6MONTHS TO NOW]^5.0 ,
[NOW-1YEARS TO NOW-6MONTHS]^3.0
[NO
Standard DisMax does not fully support explicit AND/OR.
You can prove that by trying to say q=fuel+OR+cell and see that the score stays
the same (given mm=100%)
It appears that DisMax does SOME intelligent handling of AND/OR/NOT, because it
adds the "+" on the AND and a "-" on the NOT. But adding
Hmmm, maybe I'm wrong and it does support AND. Looking at the code I
don't see why it wouldn't, actually. Though I believe I've seen it
documented that it isn't supported (or at least not advertised to
support). Ok, from the dismax wiki page it says: "This query handler
supports an extre
Thanks, Erik. that does work. I misunderstood the documentation, i
thought "clause" meant "field" rather than the terms in the query.
If dismax doesn't support the operator AND, why would the query
"solr/select?q=fuel+cell" and "solr/select?q=fuel+AND+cell" get parsed
differently(it adds the
dismax does not support the operator AND. It uses +/- only.
set mm=100% (not 1), as Hoss said, and try your query again.
Erik
On Jun 17, 2010, at 8:08 PM, Tommy Chheng wrote:
I don't think setting the mm helps.
I have mm to 1 which means the query terms should be in at least one
fi
I don't think setting the mm helps.
I have mm to 1 which means the query terms should be in at least one
field. Both query strings satisfy this condition.
The query "solr/select?q=fuel+cell" is parsed as
"querystring":"fuel cell",
"parsedquery":"+((DisjunctionMaxQuery((text:fuel |
organi
: I'm using the dismax request handler and want to set the default operator to
: AND.
: Using the standard handler, i could just use the q.op or defaultOperator in
: the schema, but this doesn't work using the dismax request handler.
:
: For example, if I call "solr/select/?q=fuel+cell", I want
I'm using the dismax request handler and want to set the default
operator to AND.
Using the standard handler, i could just use the q.op or defaultOperator
in the schema, but this doesn't work using the dismax request handler.
For example, if I call "solr/select/?q=fuel+cell", I want solr to ha
here wouldn't be any legal issues with
mgmt.
Thanks,
Amit
> Victoria,
>
> An example of specifically what types of queries you'd like to do
> would be helpful.
>
> Using nested queries you can leverage dismax and your custom query
> parser together, which may be
I found what I believe is a better option even if the multiplication
would work - FROM_UNIXTIME. That returns the same kind of output as you
get from an actual database date field.
On 4/20/2010 12:07 PM, Shawn Heisey wrote:
So, if I have my database multiply my value by 1000, I can put that
d
So, if I have my database multiply my value by 1000, I can put that
directly into a tdate field and it'll work as expected?
If that's the case, I think I might be able to modify my query from
"SELECT *" to "SELECT *,post_date*1000 as pdate" and add the pdate field
to the schema as type tdate.
No, a copyField will not do the xlation from (seconds from epoch) to
(milliseconds from 1/1/1970). You should be able to do this with a
combination of functions in your database SELECT call. The major DBs
all have a wealth of functions that xform between numbers and dates.
The DIH is smart about t
It's stored in the database as a bigint, seconds since epoch, not a
date. I need to store the integer value in Solr for the application to
consume (done as a tlong), but I want to create a second copy that's
tdate. That's the part I don't know how to do. If I just do a
copyField in the schem
Wait- it's in a database? That's much simpler.
The select should supply the date as an SQL Date or Timestamp type.
The DIH will get this directly and store it as a Solr tdate. You
should not have to do any arithmetic or formatting of date strings.
This may need a few layers of SQL functions.
On
On 4/14/2010 8:12 AM, Shawn Heisey wrote:
On 4/12/2010 9:29 PM, Lance Norskog wrote:
During indexing: the basic Solr XmlUpdateHandler does not have a
facility for this. In the DataImportHandler you can add Javascript
that takes your 'seconds since epoch', adds the delta between your
epoch and 1/
Victoria,
An example of specifically what types of queries you'd like to do
would be helpful.
Using nested queries you can leverage dismax and your custom query
parser together, which may be what you're looking for. See this
article for details on nested quer
Hi,
We are using payloads for score boosting. For this purpose we've implemented
custom boosting QueryParser and similarity function. We followed
http://www.lucidimagination.com/blog/2009/08/05/getting-started-with-payloads/
.
On the other hand, we'd like to use dismax query handling because of it
o boost relevancy based on a date field with dismax, and I've
> included the requestHandler config below. The post_date field in my
> database is simple UNIX time, seconds since epoch. It's in a MySQL bigint
> field, so I've stored it as a tlong in Solr. This filed is req
On 4/12/2010 11:55 AM, Shawn Heisey wrote:
[NOW-6MONTHS TO NOW]^5.0 ,
[NOW-1YEARS TO NOW-6MONTHS]^3.0
[NOW-2YEARS TO NOW-1YEARS]^2.0
[* TO NOW-2YEARS]^1.0
And here we have the perfect example of something I mentioned a while
ago - my Thunderbird (v3.0.4 on Win7) turning Solr boost syntax into
I am trying to boost relevancy based on a date field with dismax, and
I've included the requestHandler config below. The post_date field in
my database is simple UNIX time, seconds since epoch. It's in a MySQL
bigint field, so I've stored it as a tlong in Solr. This filed is
.@gmail.com]
> Gesendet: Samstag, 10. April 2010 12:51
> An: solr-user@lucene.apache.org
> Betreff: dismax and qf
>
> Hi,
>
> I use *dismax* and have specified my fields to be boosted in the qf
> parameter in solrconfig.xml. What I understand is that in the
> search U
Perhaps a silly question, but it's amazing
how many of my problems turn out to be
something I do to myself...
Are you sorting on anything other than
score?
Best
Erick
On Sat, Apr 10, 2010 at 6:51 AM, Mark Fletcher
wrote:
> Hi,
>
> I use *dismax* and have specified my fields to
Add &debugQuery=true to your URL, look at the parsed query in the
debug output to see if things changed there between the two qf values,
and then take a look at the score explanations in the debug output.
Erik
On Apr 10, 2010, at 6:51 AM, Mark Fletcher wrote:
Hi,
I use *di
Hi,
I use *dismax* and have specified my fields to be boosted in the qf
parameter in solrconfig.xml. What I understand is that in the search URL
also I can specify these qf value by doing the addition &qf=field1^100
field2^200 which can override the boost specified to each field in
solrconfig
Hi Hoss,
Thankyou so much for your time.
Regarding the last one I myself got confused when I posed the question. I
got it after your reply. I think I was actually looking for some thing like
the debugQuery="on" option, which I found later.
Best Regards,
Mark.
On Tue, Mar 23, 2010 at 6:56 PM, Ch
: *I haven't mentioned value for mm*
...
: My result:- No results; but each of the terms individually gave me results!
http://wiki.apache.org/solr/DisMaxRequestHandler#mm_.28Minimum_.27Should.27_Match.29
"The default value is 100% (all clauses must match)"
: 2. Does the default
Hi,
I am using dismax handler. I have it set up in my solrconfig.xml.
I have *not* used default="true" while setting it up (the standard still
has default="true")
*I haven't mentioned value for mm*
In my schema.xml I have set the default operator to be AND.
When I query I use the following in m
t;0" splitOnCaseChange="0"/>
>
> protected="protwords.txt"/>
>
>
>
>
>
> I get results back when I tried to use solr.LowerCaseTokenizerFactory
> instead of solr.WhitespaceTokenizerFactory. However, the conce
s anyone have a better idea on what
to try next? Thanks!
Wen
-Original Message-
From: ysee...@gmail.com [mailto:ysee...@gmail.com] On Behalf Of Yonik Seeley
Sent: Thursday, March 11, 2010 10:51 AM
To: solr-user@lucene.apache.org
Subject: Re: dismax and WordDelimiterFilterFactory with Preserv
On Thu, Mar 11, 2010 at 1:07 PM, Ya-Wen Hsu wrote:
> Hi all,
>
> I'm facing the same issue as previous post here:
> http://www.mail-archive.com/solr-user@lucene.apache.org/msg19511.html. Since
> no one answers this post, I thought I'll ask again. In my case, I use below
> setting for index
> g
Hi all,
I'm facing the same issue as previous post here:
http://www.mail-archive.com/solr-user@lucene.apache.org/msg19511.html. Since no
one answers this post, I thought I'll ask again. In my case, I use below
setting for index
and
for query.
When I use query with word "ain't", no result is
27;
Subject: RE: How to use dismax and boosting properly?
Try setting the boost to 0 for the fields you don't want to contribute
to the score.
Kallin Nagelberg
-Original Message-
From: Jason Chaffee [mailto:jchaf...@ebates.com]
Sent: Thursday, February 25, 2010 4:03 PM
To: solr-us
Try setting the boost to 0 for the fields you don't want to contribute to the
score.
Kallin Nagelberg
-Original Message-
From: Jason Chaffee [mailto:jchaf...@ebates.com]
Sent: Thursday, February 25, 2010 4:03 PM
To: solr-user@lucene.apache.org
Subject: How to use dismax and boo
I am using dismax and I have configured to search 3 different fields
with one field getting an extra boost so that I the results of that
field are at the top of result set. Then, I sort the results by another
field to get the ordering.
My problem is that the scores are being skewed by the
t; To: solr-user@lucene.apache.org
> Sent: Thu, February 11, 2010 10:47:03 PM
> Subject: Re: dismax and multi-language corpus
>
> That's a bug, IMO...
>
> On Thu, Feb 11, 2010 at 1:30 PM, Otis Gospodnetic
> wrote:
> > I don't know, but the other day I did see a NP
> Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
> Hadoop ecosystem search :: http://search-hadoop.com/
>
>
>
> - Original Message
>> From: Jason Rutherglen
>> To: solr-user@lucene.apache.org
>> Sent: Thu, February 11, 2010 12:36:00 AM
&
ext.com/ :: Solr - Lucene - Nutch
Hadoop ecosystem search :: http://search-hadoop.com/
- Original Message
From: Claudio Martella
To: solr-user@lucene.apache.org
Sent: Thu, February 11, 2010 3:21:32 AM
Subject: Re: dismax and multi-language corpus
I'll try removing the '-'. I do need now
> From: Claudio Martella
> To: solr-user@lucene.apache.org
> Sent: Thu, February 11, 2010 3:21:32 AM
> Subject: Re: dismax and multi-language corpus
>
> I'll try removing the '-'. I do need now to search it. the other option
> would be to request the user what
op.com/
- Original Message
> From: Jason Rutherglen
> To: solr-user@lucene.apache.org
> Sent: Thu, February 11, 2010 12:36:00 AM
> Subject: Re: dismax and multi-language corpus
>
> > Claudio - fields with '-' in them can be problematic.
>
> Why&
make your searches better.
>
> Otis
>
> Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
> Hadoop ecosystem search :: http://search-hadoop.com/
>
>
>
> - Original Message
>
>> From: Claudio Martella
>> To: solr-user@lucene.apache.org
&
io Martella
>> To: solr-user@lucene.apache.org
>> Sent: Wed, February 10, 2010 3:15:40 PM
>> Subject: dismax and multi-language corpus
>>
>> Hello list,
>>
>> I have a corpus with 3 languages, so i setup a text content field (with
>> no stemming) and
tem search :: http://search-hadoop.com/
- Original Message
> From: Claudio Martella
> To: solr-user@lucene.apache.org
> Sent: Wed, February 10, 2010 3:15:40 PM
> Subject: dismax and multi-language corpus
>
> Hello list,
>
> I have a corpus with 3 languages, so
Hello list,
I have a corpus with 3 languages, so i setup a text content field (with
no stemming) and 3 text-[en|it|de] fields with specific snowball stemmers.
i copyField the text to my language-away fields. So, I setup this dismax
searchHandler:
dismax
title^1.2 content-en^0.8 content-it
akes only one qf filed, so it doesn't help much either.
>
> Any suggestions will be helpful.
>
> Thanks
> Ram
> --
> View this message in context:
> http://old.nabble.com/Dismax-and-Standard-Queries-together-tp26157830p26157830.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
>
esn't help much either.
Any suggestions will be helpful.
Thanks
Ram
--
View this message in context:
http://old.nabble.com/Dismax-and-Standard-Queries-together-tp26157830p26157830.html
Sent from the Solr - User mailing list archive at Nabble.com.
x27;-queries get analyzed according to the
>> normal
>> analysis rules for the field it's getting sent to? Or are they passed
>> through verbatim?
>>
>> I'm hoping it's the former, as we have a variety of different field types
>> with rad
tion and filtering...
>
> Also, is there any plan to implement wildcards in dismax, or is this
> unfeasible?
>
> Thanks once again :-)
>
> Andrew.
>
> --
> View this message in context:
> http://www.nabble.com/dismax-and-query-analysis-tp26111465p26111465.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
>
ent field types
with radically different tokenization and filtering...
Also, is there any plan to implement wildcards in dismax, or is this
unfeasible?
Thanks once again :-)
Andrew.
--
View this message in context:
http://www.nabble.com/dismax-and-query-analysis-tp26111465p26111465.html
Sent from
> body
>>> 3
>>> true
>>>
>>> body
>>> 256
>>>
>>>
>>> Full solrconfig.xml and other files:
>>> http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/apachesolr/?pathrev=DRUPAL-6--1
>&g
6
>>
>>
>> Full solrconfig.xml and other files:
>> http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/apachesolr/?pathrev=DRUPAL-6--1
>>
>> --
>> Peter M. Wolanin, Ph.D.
>> Momentum Specialist, Acquia. Inc.
>> peter.wola...@acquia.com
>>
>
>
>
> --
> Peter M. Wolanin, Ph.D.
> Momentum Specialist, Acquia. Inc.
> peter.wola...@acquia.com
>
>
--
View this message in context:
http://www.nabble.com/bug--No-highlighting-results-with-dismax-and-q.alt%3D*%3A*-tp23438048p23450189.html
Sent from the Solr - User mailing list archive at Nabble.com.
1 - 100 of 161 matches
Mail list logo
