All geek questions in one place

What are the advantages and disadvantages of using a search engine as a repository of key values?

Given a search engine such as Lucene and a set of XML documents that need to be fully preserved, what are the advantages and disadvantages of using the search engine as a keystore for returning XML documents using the unique primary key that each document contains

+3
source share
3 answers

Read the Search Engine and DBMS . IMO, your application falls into the DBMS domain and is probably best served by a database with a key, such as couchDB. This is due to the fact that you do not use text operations, such as tokenization, reduction, etc.

+2
source

If you use something like Compass , and XML-to-Lucene , this is a great solution for storing and querying XML documents before reaching the XML database.

One drawback is that XML documents can only be retrieved through the Lucene API (the main data store is pretty impenetrable), but I can live with it.

+2
source

If all you are going to do is test for key equality and blob extraction, Lucene does not have a visible advantage over, say, bdb. And you have no transactions until you put something else on top. And concurrency has certain difficulties. And the API, well, a little baroque for the simple thing you do.

I implemented something like what you described, but the actual full-text data search was a critical requirement that justified the rest.

0
source

Source: https://habr.com/ru/post/1728115/

More articles:


All Articles