lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (JIRA) <>
Subject [jira] [Commented] (SOLR-3598) Provide option to allow aliased field to be included in query for EDisMax QParser
Date Thu, 12 Jul 2012 21:54:34 GMT


Jan Høydahl commented on SOLR-3598:

Yes, {{f.<fieldname>.qf}} will wire up "fieldname" as a valid "pseudo field" to be queried,
even if it does not exist in your index schema. Can you test it and report back if it solved
your use case?
> Provide option to allow aliased field to be included in query for EDisMax QParser
> ---------------------------------------------------------------------------------
>                 Key: SOLR-3598
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>          Components: query parsers
>    Affects Versions: 3.6, 4.0-ALPHA
>            Reporter: Jamie Johnson
>            Priority: Minor
>         Attachments: alias.patch
> I currently have a situation where I'd like the original field included in the query,
for instance I have several fields with differing granularity, name, firstname and lastname.
 Some of my sources differentiate between these so I can fill out firstname and lastname,
while others don't and I need to just place this information in the name field.  When querying
I'd like to be able to say name:Jamie and have it translated to name:Jamie first_name:Jamie
last_name:Jamie.  In order to do this it creates an alias cycle and the EDisMax Query parser
throws an exception about it.  Ideally there would be an option to include the original field
as part of the query to support this use case.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message