cache functionality about search-index HOT 4 CLOSED

I almost feel like this would be better suited to the application layer. What would be the benefits of adding it to the library itself? There are those of us who believe the node-way of task specific features belong to individual modules.

from search-index.

I tend to agree with @bugs181 on this one!

from search-index.

@bugs181 @mewwts I basically agree with you.

The advantage of dealing with it at the search-index layer is that you can be smarter about handling caching and updating together (since a naïve external cache must delete everything after even a minor update).

Cache functionality is only really useful once you have a lot of data on a single node, and even then only for queries that look up lots of data and are therefore non-specific and not so useful (ie: queries with search terms that are very common in the index). Since we are concentrating on "small data" just now, cache functionality is probably something to think about at some point in the future, if at all.

from search-index.

On reflection I totally agree with you guys :)

from search-index.