Closed GoogleCodeExporter closed 9 years ago
There is a third case of folder rename:
Suppose there is a folder hierarchy like this:
- Folder1
- Folder11
- Folder111
- Folder112
- Folder12
- Folder121
- Folder122
Say, Folder1 is renamed and connector starts crawling all the documents spanned
Folder1, 111, 112, 12, 121 and Folder 122. At some time connector completes
traversing all the documents from Folder11 and its subfolders and heads for
Folder12. By this time Folder12 also gets renamed. At this point, the current
traversal of the connector (initiated due to Folder1 rename) is sufficient to
reflect the rename of Folder12 as well. But, there is no such intelligence in
the connector. Instead, it completes the current traversal and then
re-traverses Folder12 which is not at all required.
Original comment by th.nitendra
on 17 Nov 2010 at 10:21
Original comment by shashank...@gmail.com
on 18 Mar 2011 at 12:05
This issue is filed as Google issue #6513810
Original comment by tdnguyen@google.com
on 18 May 2012 at 12:11
Original issue reported on code.google.com by
th.nitendra
on 11 Jan 2010 at 11:44