Lucene的数据存储 [英] Lucene as data store

问题描述

是否有可能使用 Lucene的为完全成熟的数据存储（像其他（蒙戈，沙发） NoSQL的变种）。

Is it possible to use Lucene as full fledged data store (like other(mongo,couch) nosql variants).

我知道有像最近更新的文件由一个索引一些限制，不会在其他索引中显示。因此，我们需要重新启动索引器来获取更新。

I know there are some limitations like newly updated documents by one indexer will not be shown in other indexer. So we need to restart the indexer to get the updates.

不过，我偶然发现 Solr的的最近，似乎被某种快照复制的避免这些问题。

But i stumble upon solr lately, it seems these problems are avoided by some kind of snapshot replication.

所以我想我可以利用Lucene作为数据存储，因为这也使用相同类型的文件（基于JSON）由蒙戈和沙发内部用于管理文档，其成熟的索引算法获取记录超级快。

So i thought i could use lucene as a data store since this also uses same kind of documents(JSON based) used by mongo and couch internally to manage documents, and its proven indexing algorithm fetches the records super fast.

不过，我很好奇，有没有人试过，之前..？如果没有什么理由不选择这种方式。

But i am curious has anybody tried that before..? if not what are reasons not choosing this approach.

推荐答案

还有耐用性问题。虽然Lucene索引应该不会被损坏过，我已经看到了这一点。和Lucene带给修复一个破碎指数的方法是把它扔掉，然后从原始数据重建。这使得一个索引工具非常有意义。但它确实需要你有存放在其他地方的数据。

There is also the problem of durability. While a Lucene index should not get corrupted ever, I've seen it happen. And the approach Lucene takes to repairing a broken index is "throw it away and rebuild from the original data". Which makes perfect sense for an indexing tool. But it does require you to have the data stored somewhere else.

这篇关于Lucene的数据存储的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！