First, make sure your request handler is set to spit out everything. I take it you did, but I hate to assume.
Second, I suggest indexing your data twice. One as tokenized-text, the other as a string. It'll save you from howling at the moon in anguish... Unless you really only do care about pure, exact-matching. IE, down to the character-case. Scott On Tue, Mar 29, 2011 at 8:46 AM, Brian Lamb <brian.l...@journalexperts.com>wrote: > Hi all, > > I'm a little confused about the string field. I read somewhere that if I > want to do an exact match, I should use an exact match. So I made a few > modifications to my schema file: > > <field name="id" type="string" indexed="true" stored="true" > required="false" > /> > <field name="common_names" multiValued="true" type="string" indexed="true" > stored="true" required="false" /> > <field name="genus" type="string" indexed="true" stored="true" > required="false" /> > <field name="species" type="string" indexed="true" stored="true" > required="false" /> > > And did a full import but when I do a search and return all fields, only id > is showing up. The only difference is that id is my primary key field so > that could be why it is showing up but why aren't the others showing up? > > Thanks, > > Brian Lamb >
