Hitachi Content Platform​

not sure what you mean by reset, but you really have two options. 

A) if all you want is the workflow stats reset you can go into the workflow and clear/ start over.  This will reset it back to zero

B) if you are referring to the index itself and not having the data in it/ search the easiest answer is to copy it as index 2, which will carry over your index settings but not the actual fields that were  indexed.

Workflow and index settings troy notes

Adding multiple fields to an index

HCI index options-20171224 1534-2.mp4

HCI workflow settings-20171226 1359-1.mp4

Hi Troy,

The problem we are having is this:

Tanmoy had indexing running on an HCP namespace (example NS1). Later he deleted/purged the namespace (NS1) and created a new namespace (NS2). He then updated the HCI connection to reflect this new namespace (NS2). When we re-run the index process, we are still seeing the results from the old deleted/purged namespace (NS1).

What is the expected behavior here? Should the old namespace results remain in the index, even thought the namespace has been deleted? 

Hi John,

yes. This is expected behavior as long you will search in the old index. Go the way Troy has showed and copy the index to a new index and call it different. Then HCI will create that new index with exactly the same settings as the old one. But no data in. Once this is done, change the output in the workflow and point to that new index. Then run the workflow again with the new namespace as the input. All old data should be gone then.

Ecky

This also brings up another good point.  Even if a file/object is deleted from the original source it will show up in your index unless you have "HCI_deleted".  You need to have the included in your index and then if you do not want to show deleted put in a parameter about not showing I believe it is  "True". 

Do we need to specify this field under Schema? For my index, it looks like "HCI_deleted" field is already added to my index.

Please let me know which attribute to select or discard?

You have 2 options:

1. In your search query specify +HCI_deleted:true which will exclude any deleted entries in the index

2. Create a new index and change the workflow to reflect the new index and not the old one. Delete the old index.

We are adding "Delete by Query" to version 1.4 to make this easier to manage.

Thanks John for your valuable inputs

Jon, is it possible to "tell to the Search App" not to show the deleted files, not the custom search app?

I try to do this with HCP AW latest connector.

I've tried to remove such files on a pipeline level with something like that (if statement based on HCI_deleted), but still I can see the files in the results. I ran the workflow, deleted a file and reran it again. I got the file returned in the search results:

User3 with npp...exe deleted!

Workflow with if statement:

Search results. One of the files is still there (npp...exe) - where HCI_deleted doesn't exists (I put this field as a metadata)

One of the deleted files is also there, with HCI_deleted = true even if I put this if statement (in the results of the pipeline I have 0 dropped documents)

So, each time I want a precise result I need to delete the index, make a new one and use that. Any workaround not to do that?

See this blog post: https://community.hitachivantara.com/message/34358-re-how-do-i-make-sure-deletions-are-reflected-in-the-index

Thanks Yury!

1. From that post: "A search application could filter out all deleted objects from queries by specifying -(HCI_deleted:true) as a filter query on all user query requests". Where should I turn on that setting so it is done automatically for all users (so the user don't need to put this expression in the search console by himself)? The idea is that the user don't even see that option and I don't have this nice "Exclude deleted objects" in the HCP AW connector

2. I've described above the situation where the object was deleted by the user, but it is still in the search index without this tag HCI_deleted. Which is a bit strange

There is no way to exclude deleted files from search results automatically in 1.3. This is improved in 1.4, where you can configure the workflow to delete documents from index when the file is deleted from the source.

Not sure about the file that was deleted but is not tagged with HCI_deleted=true field. Should not happen. If this is reproducible, I’d be interested in exact steps.

Ok, thanks Yury!