: then in the CustomQueryParser I iterate over all the arguments adding
: each key/value to a Map. I then pass in this to the constructor of a
: basically copied ExtendedDismaxQParser (only difference is the added
: aliases and the logic to add those to the ExtendedSolrQParser).
:
: Now, the thi
Ok, so I think I have something working relatively well. I have a few
issues which I'm not sure how to address though. Currently when I
create my ParserPlugin in solrconfig I do the following
person_name^1.0 person_name_first^0.5 person_name_last^0.5
then in
I'm not following where the aliasing feature I'm looking for is.
Looking at the patch I didn't see it either. Essentially what I'm
looking for is when a user searches for person_name that the query
turns into person_name:john OR person_name_first:john OR
person_name_last:john. I don't see anythin
: Thanks Hoss. I'm not really sure where to begin looking with this, I
: quickly read the JIRA but don't see mention of exposing the multiple
: aliases. Can you provide any more details?
i refered to it as "uf" or "user fields" ... note the specific comment i
linked to in the first url, and th
Thanks Hoss. I'm not really sure where to begin looking with this, I
quickly read the JIRA but don't see mention of exposing the multiple
aliases. Can you provide any more details?
On Tue, Jul 12, 2011 at 1:19 PM, Chris Hostetter
wrote:
> : Taking a closer look at this it seems as if the
> : Di
: Taking a closer look at this it seems as if the
: DisjunctionMaxQueryParser supports doing multiple aliases and
: generating multiple queries, I didn't see this same capability in the
: ExtendedDismaxQParser, am I just missing it? If this capability were
it's never been exposed at a user level
Thanks Dmitry, I think I've got this now.
On Sun, Jul 10, 2011 at 3:55 AM, Dmitry Kan wrote:
> was typying this on-the-go from my phone, I meant LuceneQParserPlugin of
> course.
>
> On Sat, Jul 9, 2011 at 6:39 PM, Dmitry Kan wrote:
>
>> you can try extending LuceneQParser. In its createParser me
was typying this on-the-go from my phone, I meant LuceneQParserPlugin of
course.
On Sat, Jul 9, 2011 at 6:39 PM, Dmitry Kan wrote:
> you can try extending LuceneQParser. In its createParser method
> (lucene 2.9.3 and solr 1.4) you can analyze the input query in the
> param q and modify it accord
Taking a closer look at this it seems as if the
DisjunctionMaxQueryParser supports doing multiple aliases and
generating multiple queries, I didn't see this same capability in the
ExtendedDismaxQParser, am I just missing it? If this capability were
there (and exposed via config options) this would
I do use solr over HTTP. I'm not familiar with Nginx or it's URL
rewrite capabilities. Would this be easier to rewrite a complex query
using this then a custom query parser?
On Sat, Jul 9, 2011 at 2:07 PM, Markus Jelsma
wrote:
> If you use Solr over HTTP, then why don't you use URL rewriting? N
If you use Solr over HTTP, then why don't you use URL rewriting? Nginx has
very powerful rewrite features and is capable of rewriting parts of the URL,
no need to write and compile and deploy code.
> My organization is considering a few different approaches for indexing
> vs query rewrite and I'
Also, I'm not sure if it matters or not but I'm using the edismax
query parser now, and don't wan to lose that functionality.
Really what I'd like is a way to configure the edismax parser so that
it would work on more than just the default field. So for instance if
the user specified first_name:b
If I did that how would I configure solr to use the modified query parser?
On Sat, Jul 9, 2011 at 11:39 AM, Dmitry Kan wrote:
> you can try extending LuceneQParser. In its createParser method
> (lucene 2.9.3 and solr 1.4) you can analyze the input query in the
> param q and modify it accordingly.
you can try extending LuceneQParser. In its createParser method
(lucene 2.9.3 and solr 1.4) you can analyze the input query in the
param q and modify it accordingly.
On 7/9/11, Jamie Johnson wrote:
> My organization is considering a few different approaches for indexing
> vs query rewrite and I'm
14 matches
Mail list logo
