: If it works, it's performant and not too messy it's a good way :-) . You can
: also consider just faceting on Id, and use the id to fetch the categoryname
: through sql / nosql.
: That way your logic is seperated from your presentation, which makes
: extending (think internationalizing, etc.) easier. Not sure if that's
: appropriate for your 'category' field but anyway.
That's the advice i generally give *if* you already have access to the
system of record for your categorization in your application (if not, the
tradeoff of the extra data lookup may not be worth the cost in
flexibility)
>From the notes in my "Many Facets" talk (slide #24: "Pretty"
facet.field Terms)...
>> If you can use unique identifiers (instead of pretty, long, string
>> labels) it can reduce the memory and simplify the request parsing (see
>> next Tip) but it adds work to your front end application -- keeping
>> track of the mapping between id => pretty label. If your application
>> already needs to knows about these mappsings for other purposes, then
>> it's much simpler to take advantage of that.
http://people.apache.org/~hossman/apachecon2010/facets/
-Hoss
