notes about search indexing

Thomas Waldmann avatarThomas Waldmann created an issue

speedy indexing / avoiding troubles

it shouldn't be needed to do a 100% full index build, doing and continuing a partial index run must be possible (STILL MISSING)

one idea to implement partial indexing / resumable indexing could be to have different indexing phases:

  1. index all items' metadata, but not the content - this should be rather quick.
  2. index the current revision of all items, but not the content.
  3. index content of current revisions
  4. index content of all other revisions

Problems that can happen:

  • we have to expect crashes from malfunctioning filters
  • we have to expect misbehaved converters/filters (like consuming and not freeing lots of memory)
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.