nce" is concerned.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
> From: Shalin Shekhar Mangar <[EMAIL PROTECTED]>
> To: solr-user@lucene.apache.org
> Sent: Sunday, September 14, 2008 1:38:56 AM
> Subject: Re: Help with Dism
Hi Shalin,
This works for me.
--Thanks and Regards
Vaijanath
Shalin Shekhar Mangar wrote:
On Sun, Sep 14, 2008 at 10:08 AM, Vaijanath N. Rao <[EMAIL PROTECTED]>wrote:
We have one field called language, i.e.. language of the documents, we want
people to search for there required query term
On Sun, Sep 14, 2008 at 10:08 AM, Vaijanath N. Rao <[EMAIL PROTECTED]>wrote:
>
> We have one field called language, i.e.. language of the documents, we want
> people to search for there required query terms but limit it to the language
> selected
>
> instead the q can be of type
> q=field1:en +xyz
Hi Chris and David,
We have one field called language, i.e.. language of the documents, we
want people to search for there required query terms but limit it to the
language selected
I think the confusion caused was with the query string
q=field1:xyz+xyz&qt=dismax.
instead the q can be of typ
We need no field queries, never, no way. We don't want accidental
collisions between a new movie title and an existing fieldname that
requires an emergency software push to production.
Same thing for plus, minus, AND, OR, and NOT.
Our customers really, really don't do that. They are not native
sp
: A free text option would be really nice. When our users type
: "mission:impossible", they are not searching a field named "mission".
right ... SOLR-405 was a start, but as i recall it didn't deal with the
case where the stuff before the colon wasn't a field name, and it exposed
raw field names
A free text option would be really nice. When our users type
"mission:impossible", they are not searching a field named "mission".
wunder
On 9/11/08 4:39 PM, "Chris Hostetter" <[EMAIL PROTECTED]> wrote:
>
> : I think the point is that Viaj would like to permit users to specify the
> : field if
: I think the point is that Viaj would like to permit users to specify the
: field if they so choose.
Ah... gotcha. that would fall somewhere along the lines of SOLR-405.
Although as i said in my comment there: at a minimum we need ot make it
smart enough to "do the right" thing both when the
There is a defType parameter and dismax is one such type. But
unfortunately, dismax does a lot of things and it's not structured to be
extended so that this can be modified. Presently you have to write your own
QueryParser Plugin which is not something easily done. SOLR-758 is my
attempt to fix
I think the point is that Viaj would like to permit users to specify the
field if they so choose.
On 9/11/08 12:48 PM, "Chris Hostetter" <[EMAIL PROTECTED]> wrote:
>
> : b) q=field1:xyz+xyz&qt=dismax it returns me zero result.
> :
> : Is there anyway I get results for the query type b but still
: b) q=field1:xyz+xyz&qt=dismax it returns me zero result.
:
: Is there anyway I get results for the query type b but still use the
: DisMaxHandler.
that would kind of defeat the point of dismax, which is to move the
selection of which fields are searched out of the query string (which came
fr
Perhaps we need a syntax option on DisMax. At Netflix, we've modified it
to be pure text, with no operators. My current favorite unsearchable
name is this band:
(+/-)
wunder
On 9/11/08 7:32 AM, "Smiley, David W. (DSMILEY)" <[EMAIL PROTECTED]> wrote:
> I have also wanted to use the very cool Di
Vaijanath N. Rao wrote:
Hi Solr-Users,
I am using DisMaxHandler in my application and I am facing one issue.
The DisMaxHandler works fine for general queries but returns no result
if I do fielded search.
For example
for query
a) q=xyz&qt=dismax returns me the required results
but if I do
b) q
I have also wanted to use the very cool DisMax query handler but was
dismayed that it prevented me from using Solr/Lucene's full syntax
capability. So I took matters into my own hands and modified the source. I
have patches available:
https://issues.apache.org/jira/browse/SOLR-756 757 and 758
Hi Solr-Users,
I am using DisMaxHandler in my application and I am facing one issue.
The DisMaxHandler works fine for general queries but returns no result
if I do fielded search.
For example
for query
a) q=xyz&qt=dismax returns me the required results
but if I do
b) q=field1:xyz+xyz&qt=dismax
Sorry for the late reply, the "fq" param is the recommended way to filter
results without affecting scoring for both the dismax handler and the
standard handler.
if you want to affect scoring without affecting matching, the "bq" param
of dismax is usefull instead.
: Nevermind, I got it ... Someh
Nevermind, I got it ... Somehow I missed the javadoc.
--
Luis Neves
Luis Neves wrote:
Hello all,
Using the standard query handler I can search for a term excluding a category
and sort descending by price, e.g.:
http://localhost/solr/select/?q=book+-Category:Adults;Price+desc&start=0&ro
Hello all,
Using the standard query handler I can search for a term excluding a category
and sort descending by price, e.g.:
http://localhost/solr/select/?q=book+-Category:Adults;Price+desc&start=0&rows=10&fl=*,score
I'm scratching my head on how to do the same with the Dismax query handler,
18 matches
Mail list logo
