If the check is not expensive, UpdateRequestProcessor may do the trick. Or
have a flag that is force set on all queries and do atomic update after you
validated.
Regards,
Alex
On 2 Aug 2013 04:48, "Furkan KAMACI" <furkankam...@gmail.com> wrote:
> I use Solr 4.2.1 as SolrCloud. My live indexes will be search by huge
> amounts of users and I don't want to have anything wrong. I have some
> criteria for my indexes. i.e. there mustn't be spam documents at my index
> (I have a spam detector tool), some documents should be at first result
> page (or within first and second result page, doesn't important) when I
> search for certain keywords (I don't want to organize them with query
> elevation, it doesn't important to be at first row or tenth.
>
> So I want to run a index verification tool for my indexes. How can I do
> that with SolrCloud? Should I build a pseudo SolrCloud, make tests on them
> and if everything OK then send to live SolrCloud? Or can I send documents
> to SolrCloud, don't commit them into live indexes then run that
> verification tool for not yet committed documents and then if everything is
> OK commit them.
>
> What do you prefer me for such cases who wants to run a verification
> process at their indexes before commit them into live indexes?
>
