If a record has an Endeca.Action property set to DELETE, the record is removed from the Record Store instance. This property setting is useful in an incremental file crawl where files may have been modified or deleted since the last crawl.

If an incremental crawl does not find a file that is listed in the crawl history, the CAS Server treats that file as deleted. For each deleted file, a record is created that contains the location of the deleted file and an Endeca.Action property with a value of DELETE.

For renamed files, the file with the old name is treated as a deleted file while the file with the new name is treated as a new (added) file.

This example shows the record for a TestPlan.doc file that was deleted:

<RECORDS>
  <RECORD>
    <PROP NAME="Endeca.Action">
      <PVAL>DELETE</PVAL>
    </PROP>
    <PROP NAME="Endeca.FileSystem.Path">
      <PVAL>c:\endeca_test_docs\TestPlan.doc</PVAL>
    </PROP>
    <PROP NAME="Endeca.SourceType">
      <PVAL>FILESYSTEM</PVAL>
    </PROP>
    <PROP NAME="Endeca.SourceId">
      <PVAL>FileSystemSource</PVAL>
    </PROP>
  </RECORD>
  ...
</RECORDS>

In your pipeline, you should add a record manipulator to remove records that were marked for deletion.