Code Monkey home page Code Monkey logo

Comments (6)

praveen-elastic avatar praveen-elastic commented on June 26, 2024

Hey, I tried this with two different configs having two different content source ids pointing to same SharePoint instance but was unable to reproduce it. I even added document using a custom API source too. All 3 have 411 documents.

I ran below commands:
ees_sharepoint -c sharepoint_server_connector.yml full-sync
ees_sharepoint -c new_sharepoint_server_connector.yml full-sync

image

from enterprise-search-sharepoint-server-connector.

serenachou avatar serenachou commented on June 26, 2024

@artem-shelkovnikov can you check to see how your test differs from Praveens?

from enterprise-search-sharepoint-server-connector.

artem-shelkovnikov avatar artem-shelkovnikov commented on June 26, 2024

@praveen-elastic I've updated the issue description,I was wrong and the problem happened for me when I was running incremental syncs for 2 content sources from a single connector, can you check it?

from enterprise-search-sharepoint-server-connector.

praveen-elastic avatar praveen-elastic commented on June 26, 2024

I see. Using incremental-sync does reproduce this behaviour. However, we have built the architecture with use case of one package one content source. This is because a checkpoint json file is saved after each incremental sync, containing the last updated timestamps of all the site-collections to keep a track of objects indexed in previous incremental syncs.

The next incremental sync checks for the objects created after the timestamps in the checkpoint.json file. This is the expected behaviour. However, in your case, the 2nd content source had no files to be indexed as the checkpoint file is already present because of the previous sync.

To use the same package for multiple content sources, users will have to either run full sync for the first time after switching to the new content source or will have to take care of deleting the checkpoint file before switching to other content source.

from enterprise-search-sharepoint-server-connector.

artem-shelkovnikov avatar artem-shelkovnikov commented on June 26, 2024

cc @danajuratoni @serenachou

from enterprise-search-sharepoint-server-connector.

serenachou avatar serenachou commented on June 26, 2024

After looking at this, since it only affect incremental syncs, and we plan to #56 let's reevaluate this on the new version of the connector.

from enterprise-search-sharepoint-server-connector.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.