When VCS does a large scale operation that can potentially affect many files (eg. an update from the remote repository)
the indexing infrastructure should not react to every single file event fired from the VCS operation. Instead it should
mark the affected roots dirty and rescan them when the VCS operation is finished.
I'm not sure where/how exactly this should be implemented, but I filed it here, because I intend to do some work in this
are in 6.8 timeframe.
*** Issue 167671 has been marked as a duplicate of this issue. ***
It's got a P2 duplicate, so I'm making it P2 as well.
Created attachment 87885 [details]
Prototype of versioning-indexing integration
Tomas, could you please have a look at the attached patch and give me some feedback? It contains new
versioning.indexingbridge module, which implements the bridge between versioning.util and parsing.api modules. There is
also new IndexingBridge class in versioning.util's API, which is then used from subversion module to refresh filesystems
and rescan changes. I'm primarily interested in knowing whether the API in IndexingBridge is adequate for the needs of
our VCS plugins. It seems to be ok for subversion, but I haven't looked at other plugins and obviously I might even have
overlooked something in the subversion module itself. Thanks
Once we are confident that the API is suitable for all our existing VCS plugins, I'll take it for API review.
*** Issue 175631 has been marked as a duplicate of this issue. ***