Yes :) my mistake
But then using 'key' or changing the SimpleFacetParameter to take
'alias' instead of 'key'. So that they use the same keywords for the
same kind of action.
On 5-6-2009 14:01, Noble Paul ??????? ?????? wrote:
did you mean something like'
{code}
using multiple values is better than
fl={!alias=title}placename&fl={!alias=title}subject
{code}
On Fri, Jun 5, 2009 at 5:26 PM, Thijs Vonk (JIRA)<[email protected]> wrote:
[
https://issues.apache.org/jira/browse/SOLR-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716590#action_12716590
]
Thijs Vonk edited comment on SOLR-1205 at 6/5/09 4:54 AM:
----------------------------------------------------------
I already like this feature however, is it possible to conform to some
standard?
With SimpleFacetComponent (see
http://wiki.apache.org/solr/SimpleFacetParameters#head-4ba81c89b265c3b5992e3292718a0d100f7251ef
) you can rename a facet.field with something like facet.field={!ex=dt
key=mylabel}doctype where the field will return as 'mylabel'
could we do the same here? Something like
{code}
fl={!key=placename}title,{!key=subject}title
{code}
This way we can also keep the comma separated field list
was (Author: thyzz):
I already like this feature however, is it possible to conform to some
standard?
With SimpleFacetComponent (see
http://wiki.apache.org/solr/SimpleFacetParameters#head-4ba81c89b265c3b5992e3292718a0d100f7251ef
) you can rename a facet.field with something like facet.field={!ex=dt
key=mylabel}doctype where the field will return as 'mylabel'
could we do the same here? Something like
{code}
fl={!key=placename}title,{!key=subject}title
{code}
add a field alias feature
-------------------------
Key: SOLR-1205
URL: https://issues.apache.org/jira/browse/SOLR-1205
Project: Solr
Issue Type: New Feature
Reporter: Noble Paul
Fix For: 1.5
A feature which is similar to the SQL 'as' can be helpful
see the mail thread
http://www.lucidimagination.com/search/document/63b63edc15092922/customizing_results#63b63edc15092922
it can be implemented as a separate request param
say
{code}
fl.alias=from_name1:to_name1&fl.alias=from_name2:to_name2
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
