Hello,

I found a few previous discussions about the implementation of full
text search in Fossil and I'm curious about the current status. It's
clear that this isn't a simple problem to solve, but I think it's an
essential feature to have, even if the initial implementation covers
just the most basic use cases.

As a first step, I would allow searching of the timeline and tickets.
These items don't introduce problems related to branching, and the
database size should not be affected too much. The index should not be
synchronized with other repositories and I would leave it off by
default. Once enabled, the index is updated automatically after each
new timeline entry. If the entry refers to a ticket, then include its
title and comments.

The second step would be to index stand-alone wiki pages. This is also
fairly straightforward; ignore history and index the most recent
version of each page.

The final step would be indexing the actual file contents. This would
apply to the embedded documentation and any other file types. Exactly
how to do this is a tricky question to answer, but my initial thought
is to provide a configuration option through which an admin can
specify the branches and file types to include in the index. For
example:

trunk:*.wiki
release:*.h;*.c;*.txt

As with the stand-alone wiki pages, I would only index the last
version of each matching file in each branch. When a file is changed
by a new check-in or push, remove the old version and index the new
one.

Finally, how should the results be presented? Perhaps the simplest
solution is to only show one type of results on a single page. Just as
you have Tickets Only, Wiki Only, and other buttons on the current
timeline page, the search results can default to the timeline view,
where the user could then click buttons to search for other type of
information (Tickets, Wiki, and Files).

Thoughts?

- Max
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to