I am using Manifold 2.10 patched for issue https://issues.apache.org/jira/browse/CONNECTORS-1512
I find that the "unconstrained" query submitted to Documentum differs depending on whether the Content Types in the job have been edited or not. This can dramatically affect which files are fetched. After editing, there are likely to be fewer.
For example, having simply created a job connecting to DM and setting only the Paths value to Administrator/james the following request is generated. (Taken from manifoldcf.log).
Note that there are no a_content_type constraints (and my line break for readibility):
Once the Content Types tab has been edited (e.g. to remove the 123w type) it looks like this, i.e. the search constrains to only the selected types (my ellipsis for readibility):
If the 123w type is now reselected in the Content Types tab, the search adds it to the list of a_content_type entries, but doesn't return to the unconstrained initial search:
This means that running what appears to be an equivalent job several times may not fetch the same set of documents from Documentum.
I expect that the same configuration in the UI produces the same search to Documentum, regardless of how the configuration was arrived at.
If the selected items in the Content Types list is treated as the only set of files to fetch (i,.e. the initial unconstrained search is considered incorrect here) then I guess I might also like to have flexibility to fetch file types not on the checklist in the Content Types tab.