Mailing-List: contact user-help@manifoldcf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@manifoldcf.apache.org
Received-SPF: pass (athena.apache.org: domain of daddywri@gmail.com designates
 209.85.216.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <trinity-06802883-0da7-4452-9aeb-cafc9c96e7a5-1384938672508@3capp-webde-bs38>
References: 
 <trinity-06802883-0da7-4452-9aeb-cafc9c96e7a5-1384938672508@3capp-webde-bs38>
Date: Wed, 20 Nov 2013 06:55:53 -0500
Message-ID: 
 <CALUFAGD2SZTexbwYn-2hHmoT9mOb5W+eoB_BZMH6T_UJx0Rcww@mail.gmail.com>
Subject: Re: Does ManifoldCF support distributed search with Apache Solr?
From: Karl Wright <daddywri@gmail.com>
To: "user@manifoldcf.apache.org" <user@manifoldcf.apache.org>
Content-Type: multipart/alternative; boundary=047d7b5db5928e046b04eb9a7646

--047d7b5db5928e046b04eb9a7646
Content-Type: text/plain; charset=ISO-8859-1

Hi Markus,

I am glad that the search component is working for you, but it seems to me
like it is perhaps not optimal, in the sense that there is no reason why
the component should wait to apply its query restrictions so late in the
query resolution cycle.  This may have the unfortunate effect of also
putting additional unnecessary load on the MCF Authority Service as well.

It would be great to know what the recommended setup is for components like
ours within Solr.  If sharding support modifies the query, then I think the
MCF plugin should remain exactly as it is with respect to sharding.  But if
sharding leaves the query alone, we may want to consider running the MCF
plugin up-front instead.


If you are able to do enough research to make a recommendation, I'd be
happy to change the plugin functionality to match - or, at least, provide a
parameter which would allow you to select how you want it to work.

Thanks,
Karl


On Wed, Nov 20, 2013 at 4:11 AM, Markus Schuch <markus_schuch@web.de> wrote:

> Hi Karl,
>
> we activated distributed search an it worked.
>
> It is important to know, that the MCF Security Component must be
> configured in the search handler of each shards.
>
> When the sharded request arrives (having the shards parameter set) the MCF
> Security Component deactivates itself. The search handler creates the 2nd
> stage requests for each shard. These requests don't have the shards
> parameters set (otherwise an endless loop would occur) which results to an
> active the MCF Security Component on each shard in the 2nd stage.
>
> Thanks,
> Markus
>

--047d7b5db5928e046b04eb9a7646
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div><div>Hi Markus,<br><br></div>I am glad that=
 the search component is working for you, but it seems to me like it is per=
haps not optimal, in the sense that there is no reason why the component sh=
ould wait to apply its query restrictions so late in the query resolution c=
ycle.=A0 This may have the unfortunate effect of also putting additional un=
necessary load on the MCF Authority Service as well.<br>
<br></div>It would be great to know what the recommended setup is for compo=
nents like ours within Solr.=A0 If sharding support modifies the query, the=
n I think the MCF plugin should remain exactly as it is with respect to sha=
rding.=A0 But if sharding leaves the query alone, we may want to consider r=
unning the MCF plugin up-front instead.<br>
<br><br></div>If you are able to do enough research to make a recommendatio=
n, I&#39;d be happy to change the plugin functionality to match - or, at le=
ast, provide a parameter which would allow you to select how you want it to=
 work.<br>
<br>Thanks,<br></div>Karl<br><br></div><div class=3D"gmail_extra"><br><br><=
div class=3D"gmail_quote">On Wed, Nov 20, 2013 at 4:11 AM, Markus Schuch <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:markus_schuch@web.de" target=3D"_blan=
k">markus_schuch@web.de</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi Karl,<br>
<br>
we activated distributed search an it worked.<br>
<br>
It is important to know, that the MCF Security Component must be configured=
 in the search handler of each shards.<br>
<br>
When the sharded request arrives (having the shards parameter set) the MCF =
Security Component deactivates itself. The search handler creates the 2nd s=
tage requests for each shard. These requests don&#39;t have the shards para=
meters set (otherwise an endless loop would occur) which results to an acti=
ve the MCF Security Component on each shard in the 2nd stage.<br>

<br>
Thanks,<br>
Markus<br>
</blockquote></div><br></div>

--047d7b5db5928e046b04eb9a7646--