It depends on what kind of behavior you're looking for. if for your queries the order of the 6 integer values doesn't matter you could do:
<field name="item" type="tint" multiValued="true"/> then you could query with ORed or ANDed integer values over that field. If the order matters but you always query on the "set" of 6 values, then you turn your six integers into a guid or simply HEX encode them into singleValued string field. Another possibility is to HEX encode the integers and separate them with whitespace and whitespace tokenize. Then you get a mixture of the two above but you can also specify some locality constraints, eg. using phrase queries, etc. The answer really depends on the types of queries you need to be able to respond to. M -- View this message in context: http://lucene.472066.n3.nabble.com/n-values-in-one-fieldType-tp4034552p4034662.html Sent from the Solr - User mailing list archive at Nabble.com.
