Hi Markus, The canonical way that a connector handles incrementality changed from 1.7 to 1.10. We maintained backwards compatibility through the inclusion of legacy base connector methods. CONNECTORS-1153 reported a problem in one of those base connector methods, which has been fixed by 1.10. I can't tell whether this applies to your situation.
On 2.x the base connector methods no longer have all of the legacy base connector methods at all, so if you have a custom connector you will need to rework your connector class to adhere to the newer model. Specifically, there is no such method anymore as "getDocumentVersions()". Instead, your connector must signal its disposition of any document using the IProcessActivity methods available for that purpose. Can you describe in more detail what you are doing here? (a) Is this a custom connector? (b) Was it developed on 1.7 or before? (c) Are you trying to run it on 1.10 or on 2.x? That will help me give you better responses. Karl On Fri, Mar 4, 2016 at 5:28 AM, Markus Schuch <[email protected]> wrote: > Hi, > > we ran on MCF 1.7 for quite a while and in this environment a document > send to the ingestion pipeline together with an empty version string was > always reingested. > On MCF 2.3 this is no longer the case. > > I found https://issues.apache.org/jira/browse/CONNECTORS-1153 and may be > the 1.7 behavior we were relying on was always a bug. > > Question: > Is the new 2.3 behavior the expected case how the ingestion pipeline > handles an empty version string? > And how can "always reingestion" be triggered? > > Thanks in Advance, > Markus >
