: ...&q={!join+from%3DconceptId+to%3Did+fromIndex%3DSearchProducts0}parentProductId:PROD_Hs01_00179501
: But, I have a client who asked if it would be possible for the parent : product ID to be specified in a case insensitive manner, with or w/o the : underbar characters. So, I figured I could add some index and query : time analysis to the field to do that: Just to clarify: you changed this fieldType in your "SearchProducts0" schema.xml correct? and did you re-index the data in your SearchProducts0 collection after chaning this? Have you tried directly searching SearchProducts0 with that query "parentProductId:PROD_Hs01_00179501" to confirm it's working properly? : My filter query stopped working, but I found some references to the fact : that query time analysis is not performed for filter queries. I do use that's not true at all, and never has been -- what refrences did you find that said that? : (http://blog.trifork.com/2012/01/22/query-time-joining-in-lucene/) : mentions near the end of the article about work yet to be done regarding : the Lucene query time join: that article refers to a lower level lucene/module/join - it does not apply to the {!join} query parser in Solr. : Seems I'm hitting that fact? Is query time analysis of the search term : not performed when using a join? I'm using Solr 4.0 incorporated into : DataStax Enterprise 2.2.3. It's possible that there may be something wonky going on because of the cross-core join. there was a bug a while back about which collection was used to do the query parsing/re-writing, but that was fixed in Solr 4.0-ALPHA (SOLR-2824) ... you may have stumbled upon some other ismilar varient. can you provide a small, complete, example for reproducing the problem? a zip file containing all the neccessary configs and some sample docs attached to a (new) jira issue would be very helpful -Hoss