nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

What constitutes an "event" for search event-based index updates

SethHickel

I have iw.index.events.enable=true set in my search.properties. Am I correct in thinking that an event is submission to TeamSite staging? Are there other events that trigger search to index a file? What about a change to a tag value for a file (one that is many versions old) without submitting that file to TeamSite staging?

Thanks.

Find more posts tagged with

Comments

SethHickel

I'm still only seeing that a submit to TeamSite staging triggers the indexing or re-indexing of a file. It does not appear that simply creating, editing, tagging or other workarea centric tasks trigger an index of a file. Am I correct? Is there documentation that lists what events trigger an indexing of a file?

Thanks.

Adam Stoller

I'm still only seeing that a submit to TeamSite staging triggers the indexing or re-indexing of a file. It does not appear that simply creating, editing, tagging or other workarea centric tasks trigger an index of a file. Am I correct? Is there documentation that lists what events trigger an indexing of a file?

Thanks.

Depending on which version of Search you have, I believe there is an option (iw.index.wamodifications.enable) to, uhm, enable workarea-modification indexing.

vijetha

As Ghoti mentioned, enable indexing of workarea modifications by changing the property of wamodifications.enable=true in search.properties files and search for modified content after some time (I think the time it takes to re index depend upon the events.listen.wait value.) as recently modified content might not indexed immediately.

SethHickel

(iw.index.wamodifications.enable) to, uhm, enable workarea-modification indexing

search for modified content after some time

What is interesting is that I have that option set to true. I have the frequency of workare modifications indexing set to two minutes.

My users are trying to search for tag added to content through the tag interface. I wonder if additions or changes to tags for a file is an event that search recognizes as a re-indexing trigger.

Following is taken from my search.properties

# Indexing workarea modifications
# Control whether indexing of and searching across modifications in workareas
# of indexed branches is turned on or not.
iw.index.wamodifications.enable=true
# Control whether indexing the modifications of ALL the workareas of a branch
# at the time the branch is first indexed should be turned on or off (permissible
# values are none and all).
iw.index.wamodifications.branchcreation.default=none
# Control how often (in minutes) an attempt is made to index the modified files in the
# relevant workareas of all the relevant indexed branches.
iw.index.wamodifications.frequency=2
# Control after how much time (in hours) the collections of workarea modifications for a
# branch are considered too old and hence deleted and then re-indexed. Checked during
# index server startup only.
iw.index.wamodifications.deleteindexes=72

Thanks