Unfortunately the number of fees is unknown so we couldn't add the fields
into the solr schema until runtime. The work-around we did was create an
additional column in the view I'm pulling from for the index to determine
each record's minimum "fee" and throw that into the column. A total hack,
but
Hm, yes, it sounds like your "fees" field has multiple values/tokens, one for
each fee. That's full-text search for you. :)
How about having multiple fee fields, each with just one fee value?
Otis
Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
Hadoop ecosystem search :: http://se