Hi Paul,

This looks like a bug in the CMIS connector to me; usually the document
version string the connector constructs should be adequate to detect all
changes.  Can you create a ticket?  https://issues.apache.org/jira ,
project ManifoldCF.  Please include what version of MCF you are using
here.  FWIW, this may be in fact a bug in the Alfresco CMIS implementation,
but we'll have to have some back and forth before I can determine that for
sure.

In the meantime, have you considered using the Alfresco Webscript
connector?  It's the preferred way to do Alfresco indexing, although there
have been issues reported having to do with running it on some
configurations of Alfresco.  I'm not entirely sure what the problem is
there; maybe a version dependency of some kind.

Karl


On Mon, Oct 19, 2015 at 7:43 AM, Paul Farrell <[email protected]>
wrote:

> Hi Everyone,
>
> Hoping someone may be able to advise.
>
> I am currently using Manifold, together with a CMIS connector, to retrieve
> and index content from an Alfresco repository.
>
> All is going well apart from, what I would call, the ‘incremental crawl’.
>
> The main issue I am having is that the modification of a document’s
> security settings, in Alfresco, is not being picked up in next Manifold
> crawl. As an example I have a document ‘TestDoc1’ which has user A and B as
> Consumers. I run a crawl in Manifold and it picks up the documents fine.
> The security is set as expected. I then remove ‘User A’ from the security
> of that document and re-run the Manifold crawl. User A can still see the
> document in the local search engine.
>
> It is as if Manifold is not treating the security update as a
> ‘modification’ and is therefore not refreshing it. Note that if I go into
> the Output Connections, edit and save the relevant output connection and
> then click ‘Remove all associated documents’, the next time I crawl, the
> changes are picked up. It is clear that Manifold is just not updating
> whatever internal record it has for this item.
>
> Any ideas?
>
> Many thanks.

Reply via email to