![]() ![]() To poll queue A to determine items to index. Modified whenever the item is repushed or reindexed. To an item during an item.push or item.index operation. Note: The connector can assign a queue label, using the item's queue field, "A" for "queue A." The content is indexed into Cloud Search. NEW_ITEM as it doesn't exist in the queue. To push items (metadata and hash) into an indexing queue, "queue A" as On initial traversal, the content connector uses ![]() On an empty queue isn't within scope of this section. They are the same as steps 1-4 in the previous diagram and not in scope for Deleting items Note: In the following list of steps, steps 1-4 are not shown in Figure 2 as ForĮquivalent SDK calls, refer to Queue operations (Connector SDK). Specifically, Figure 2 shows the second traversal performed Figure 2 shows the steps in deleting an item using two Overview of using indexing queues to delete an itemĪnd detect deletions. For an example of how two queues might be used, refer to the Note: Some traversal strategies, such as the full traversal, use more than one For information on item deletions, see the next Or push an item again if it's not modified or if there is a Successfully finishes processing the item.Ī connector can also delete an item if it no longer exists in the repository, The item only enters the ACCEPTED state after Cloud Search The connector retrieves these items from the repository and builds index Which items are most in need of indexing, sorted first by status code and then To poll the queue to determine items to index. Usually, the push is associated with content traversal and/or change detection
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |