In my case, I write a HTTP gateway between application and Solr engine. This is long existed before I use Solr as SE. Back that time, I figure out one day I might replace our old SE and it would cause two dilemma: 1> If our applications directly call the API of THE search engines, when we replace it with another SE, all the calling statements have to be rewritten. It would be a very hard job for us, especially when the number and size of applications get bigger. 2> We have applications written in different languages and we from time to time need to maunally test status of SE by our system engineers. Furthermore, we want to fix some default parameters in the gateway for simplicity and security issues (e.g. Shortening the size of HTTP call, Prevent db names, field names, etc. shown in the HTTP call, etc.) And these considerations ended up with a gateway design.
For your question, IMHO, I wouldn't define query parameters in Solr unless you think they WOULD BE GLOBALIZED. You can consider our solution. scott.chu，scott....@udngroup.com 2016/6/15 (週三) ----- Original Message ----- From: Derek Poh To: solr-user CC: Date: 2016/6/13 (週一) 11:21 Subject: Define search query parameters in Solr or let clients applicationscraft them? Hi Would like to get some advice on should the queries parameters be define in Solr or let the clients applications define and pass the queries parameters to Solr? Regards, Derek ---------------------- CONFIDENTIALITY NOTICE This e-mail (including any attachments) may contain confidential and/or privileged information. If you are not the intended recipient or have received this e-mail in error, please inform the sender immediately and delete this e-mail (including any attachments) from your computer, and you must not use, disclose to anyone else or copy this e-mail (including any attachments), whether in whole or in part. This e-mail and any reply to it may be monitored for security, legal, regulatory compliance and/or other appropriate reasons. ----- 未在此訊息中找到病毒。 已透過 AVG 檢查 - www.avg.com 版本: 2015.0.6201 / 病毒庫: 4598/12409 - 發佈日期: 06/12/16
