My implementation supports what i’d like to say is “full-text” search, but is still in early beta.
@Jeff some valid points there especially on the concurrent updates when i first attempted to create a simple index i ran into those issues but simple code changes and additions solved those issues.
My solution was to maintain a column family for index logs where i keep track of what is being written with other useful info including a status of success or failure. Since its a search engine which is continually running i simply use a few methods in a class to periodically check for error statuses in the log. Each success log is deleted at some point and i check my column families to see if any rows or columns were written that are marked as failed in the log. If no record is found in the column family the value should have been written then i retry and then continue to check for inconsistency in other column families related to the failed update and try to correct them. It’s extra work but it has worked out quite well to so far. My data set is only 100 GB right now but it’s growing day by day and i’ve hammered out quite a lot of issues and she’s fairly stable to this end and quite fast one searches which is my priority