On 5/15/2015 12:47 PM, Charles Sanders wrote: > Ran the same test as below. Added echoParams=all and debug=query. Thanks for > the help!
Initially, I was a little confused by something I saw in your debug output. I've broken up the query text with newlines into 50 character increments for clarity in an email context: "parsedquery": "portal_package: 12345678901234567890123456789012345678901234567890 12345678901234567890123456789012345678901234567890 12345678901234567890123456789012345678901234567890 12345678901234567890123456789012345678901234567890 12345678901234567890123456789012345678901234567890 12345 portal_package:67890123456789012345678901234567890 12345678901234567890123456789012345678901234567890 12345678901234567890123456789012345678901234567890 12345678901234567890123456789012345678901234567890 12345678901234567890123456789012345678901234567890 1234567890", Then I looked back at your fieldType definition and noticed that you are only defining an index analyzer. Remove the 'type="index"' part of the analyzer config so it happens at both index and query time, reindex, then try again. If your index is small enough (especially if this is the only doc it contains), you can go to the admin UI and load the terms with the Schema Browser after selecting the portal_package field and see what is actually in your index for this document. As long as your analysis chain is the way it is, Solr's behavior will be odd. Once we get it straightened out, then we can look for any other problems. Thanks, Shawn
