During a scan, the CodeAware index: 

<CODEINSIGHT_ROOT>/config/.codeaware/working_dir/<UID>/search_terms_index

can grow very large depending on the project(s) scanned. This article goes over these factors and what sizes you can expect to see.

The CodeAware index size is affected by the following factors:

• The indexing size depends on multiple aspects like type of encoding, type of file, size and content of the files, version of Apache Lucene used in our product, the way the indexing is performed, and the details we have stored in our indexes.
• Binary type of files might take less index space compared to source code files.
• The size of the index may range from 2-4 times the size of the codebase.
• With a codebase size of 35 GB and mostly source code files, it may grow up to 4 times the size of the codebase, i.e. 140 GB.

NOTE: After the completion of the automated analysis phase of a scan, CodeAware sends the JSON to the scanner and the indexes are also cleaned up completely, so data would not be retained.