Actually, I have no plan so far, and this was just an idea in the doc.
SQLite FTS tables must actually be populated with real data, using INSERT statements, so the index is created. Somehow, the data located within the NSF have to be replicated in this table. SQLite cannot just use the content of the NSF table and search through it. Now, you should be able to create a physical SQLite table and populate it with a simple SQL statement from the NSF table.
To properly work, this needs:
- the SQLite table to be persistant. Last time I tried that, I got a crash, so I'm not sure it works
- add the FTS table DDL in the DB definition
The technical best solution in your case would be to use a real FT indexer like Lucene fed using a DOTS task monitoring all the server events (document create/update/delete operations), or incrementing the index periodically.
Or use an higher level indexer like SOLR. The RESt services should make it easier.
Note that all of this would be a nice project on OpenNTF :-)