Edit 1: Well, I spoke too soon. While the CFSEARCH function is now working properly using combinations of SOME keywords & phrases, it is still giving bogus results on combinations of keywords & phrases when entering DIFFERENT keywords &/'or DIFFERENT phrases.
The solr admin query tool always give the same results as our production server.
But the CFSEARCH function is still not working properly. Go figure!
*****************************************
It took more hours over the course of more days than I like to admit. Sing Hossanah!! I finally solved the problem.
With verity we used the following CFSEARCH code on collections. I.E., there were 2 types of searches available in Verity: "SIMPLE" & "EXPLICIT"
********************************
<CFSEARCH NAME="applicants_#var#"
COLLECTION="#verityCollection#_Apps_#var#"
TYPE="#Form.verityType#"
CRITERIA="#Form.keywords#" >
**************************************
The search started working (to a degree) when I changed it to”
**************************************
<CFSEARCH NAME="applicants_#var#"
COLLECTION="Resumes"
TYPE="standard"
CRITERIA="#Form.keywords#" >
***************************************
I had changed TYPE to “standard” because that is the default Type for Solr. I FINALLY noticed that TYPE was not used in the CFSEARCH examples I saw listed for Solr even though TYPE was an optional parameter for Solr searches.
***************************************
When I commented out the TYPE line of code as shown below, VIOLA, the searches now mirror the searches on the production machine running using Verity!!!!
***************************************
<CFSEARCH NAME="applicants_#var#"
COLLECTION="Resumes"
<!---TYPE="standard" --->
CRITERIA="#Form.keywords#" >
***************************************
For whatever reason, entering the TYPE parameter was porking some of the searches.
AdChoices