Gurbeer Not sure but can you check the scope of search defined into the seachable-expression element of search:resolve option.
Regards Abhishek Srivastav Systems Engineer Tata Consultancy Services Cell:- +91-9883389968 Mailto: [email protected] Website: http://www.tcs.com ____________________________________________ Experience certainty. IT Services Business Solutions Outsourcing ____________________________________________ From: "Singh, Gurbeer" <[email protected]> To: <[email protected]> Date: 06/21/2011 10:46 PM Subject: [MarkLogic Dev General] Search:resolve @total count and Search-result count mismatch Sent by: [email protected] Hi, We are facing one issue with ML code search:resolve. We have specific requirement to change the relevancy order of searched document. So we are not using search:search We have written our own query given different weight as per the requirement and using search:resolve , but we are facing one issue with this. The number of result/@total is different with total search/@result. Facet count is also not matching. I am giving you the query which I am executing If we execute below query search:response/@total is 4 Count(search:result) is 2, also facet count is different I tried by adding "fragment-frequency option" in all of the facet but no luck. I have enclosed search query and related module for reference I am also sending you four documents. Please don't assume that this is happening only with these four documents. When I search for key "Acceptance of Money Orders and Travelers Checks" I am getting @total 4 but result 2 When I am search for "Money Orders" I am getting @total 4 and @result 4 which is correct. ~Gurbeer NOTICE: Morgan Stanley is not acting as a municipal advisor and the opinions or views contained herein are not intended to be, and do not constitute, advice within the meaning of Section 975 of the Dodd-Frank Wall Street Reform and Consumer Protection Act. If you have received this communication in error, please destroy all electronic and paper copies and notify the sender immediately. Mistransmission is not intended to waive confidentiality or privilege. Morgan Stanley reserves the right, to the extent permitted under applicable law, to monitor electronic communications. This message is subject to terms available at the following link: http://www.morganstanley.com/disclaimers. If you cannot access these links, please notify us by reply message and we will send the contents to you. By messaging with Morgan Stanley you consent to the foregoing._______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you
_______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
