Aliasing facets in solr

«

Previous topic

|

|

Next topic

»

Author	Message
H-Works Agency	Friday 01 April 2011 4:53:54 am Hello, Is it possible to "alias" facet in that way : - Say i have some results with facet "City" with result : Paris, New-York, London - Can i "alias" the facet so London won't show anymore but London results would be aggregated in Paris facet ? Like this : Before : Paris (1) New-York (4) London (6) After : Paris (7) New-York (4) And a click on Paris would show Paris & London results ? How can this be achieved ? Thanx in advance from any solr guru ! EZP is Great
Philippe VINCENT-ROYOL	Friday 01 April 2011 6:01:50 am Hi, Yes its possible to "merge" two different facet. Its not a clean method but it works. For example if your city attr looks like in solr : attr_city_t You ll have value like attr_city_t:paris and attr_city_t:london When you show link, just add something like &filter[attr_city_t][]=paris&filter[attr_city_t][]=london (depends how you generate your url) Thats all Philippe Certified Developer (4.1): http://auth.ez.no/certification/verify/272607 Certified Developer (4.4): http://auth.ez.no/certification/verify/377321 G+ : http://plus.tl/dspe Twitter : http://twitter.com/dspe
H-Works Agency	Friday 01 April 2011 7:29:49 am Yes the prob is that results count wont be affected i think. EZP is Great
Philippe VINCENT-ROYOL	Friday 01 April 2011 7:39:51 am If you object have only one city, you could add count result.. else maybe try to look at advanced syntax via solr : http://wiki.apache.org/solr/SolrQuerySyntax (im talking before filtrering) After filtring be careful to add an "or" with your 2 attr :) Certified Developer (4.1): http://auth.ez.no/certification/verify/272607 Certified Developer (4.4): http://auth.ez.no/certification/verify/377321 G+ : http://plus.tl/dspe Twitter : http://twitter.com/dspe

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing:	Jan 29 2025 23:47:21
Script start
Timing:	Jan 29 2025 23:47:21
Module start 'layout'
Timing:	Jan 29 2025 23:47:21
Module start 'content'
Timing:	Jan 29 2025 23:47:21
Module end 'content'
Timing:	Jan 29 2025 23:47:21
Script end

Main resources:

Total runtime	0.0153 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0050	588.1563	151.2109
Module start 'layout'	0.0050	0.0034	739.3672	36.6563
Module start 'content'	0.0084	0.0053	776.0234	95.3125
Module end 'content'	0.0136	0.0016	871.3359	33.9766
Script end	0.0152		905.3125

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0024	15.8857	14	0.0002
Check MTime	0.0011	7.4136	14	0.0001
Mysql Total
Database connection	0.0007	4.6359	1	0.0007
Mysqli_queries	0.0027	17.6331	3	0.0009
Looping result	0.0000	0.1839	1	0.0000
Template Total	0.0011	7.4	1	0.0011
Template load	0.0008	5.5446	1	0.0008
Template processing	0.0003	1.8363	1	0.0003
Override
Cache load	0.0005	3.2298	1	0.0005
General
dbfile	0.0004	2.8791	8	0.0001
String conversion	0.0000	0.0655	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs