The full import wasn't spitting out any errors on the web page but in looking at the logs, there were errors. Correcting those errors solved that issue.
Thanks, Brian Lamb On Tue, Mar 29, 2011 at 2:44 PM, Erick Erickson <erickerick...@gmail.com>wrote: > try the schema browser from the admin page to be sure the fields > you *think* are in the index really are. Did you do a commit > after indexing? Did you re-index after the schema changes? Are > you 100% sure that, if you did re-index, the new fields were in the > docs submitted? > > Best > Erick > > On Tue, Mar 29, 2011 at 11: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 > > >
