Closed GoogleCodeExporter closed 9 years ago
If supported say run once a day, this could well lead to a situation where new
site
collections are kept adding and hence the connector's first crawl cycle is
never
completed. That means connector will take longer time to detect changes in any
of the
already crawled site collections.
Need to consider these use cases while designing the solutions for the same.
Can the discovery of site collections be a background thread running
continuously at
a specified rate?
Original comment by rakeshs101981@gmail.com
on 11 Aug 2009 at 2:16
Ideally discovery should be handled by a different thread.
Internally the connector should maintain a queue of all the documents to be fed
to
the GSA. Multiple threads may add entries to this queue. It will also help if
we can
have multiple threads for Discovery and Crawl (Change Detection). The number of
threads for each of these, their priorities and schedules should be kept
configurable.
This will give the user some significant control on how quickly changes need to
be
fed.
Also a feature of type "index now" will prove beneficial when the user wants to
force
feed a newly added site.
Original comment by j.dars...@gmail.com
on 15 Sep 2009 at 8:22
Original comment by rakeshs101981@gmail.com
on 25 Sep 2009 at 2:10
This issue is filed as Google issue #6513772
Original comment by tdnguyen@google.com
on 18 May 2012 at 12:36
Original issue reported on code.google.com by
rakeshs101981@gmail.com
on 11 Aug 2009 at 2:12