Can we customize the Lucene built-in to Solr?

Question

Is it possible to configure Lucene, which is built into Solr in the same way as we can in raw Lucene? So that we have “everything” that we have in Lutsen in Solr?

I ask this because we are stuck at the solution point of Solr vs Lucene, thinking this way:

Argument 1:

"We can fall into the dead zone in the future if we choose Solr, and Lucene is a better choice therefore ... So we could also start writing HTTP wrappers and almost half of Solra on top of Lucen should be on the safer side."

Argument 2:

"Solr already has all the functions that we want to use, so why not just use it? Since the people who perform Lutsen are also responsible for Solr, all the functions of Lucene are available to Solr too ..."

I went through many blogs and posts that say something like:

In situations where you have very individual requirements that require low-level access to the Lucene API classes, Solr will be more than help, as it is an additional layer of indirection.
-http: //www.lucenetutorial.com/lucene-vs-solr.html

One way to defend Argument 2 is to confirm that we can configure the base Lucene in Solr just as if we had only Lucene.

Can someone provide a better way to close this argument? :)

ps: we need a quick search with indexing and interleaving terabytes of data ...

Answer 1

Can I customize Lucene built-in to Solr?

Yes you can . But keep this in mind:

Communicators Lucene and Solr are among the leading experts in the field of full-text search. They have many years of experience in this field. If you think you can do better than them, then go and change Solr to your needs (this is an Apache license so that there are no commercial restrictions), and if you do, try to do this in order to subsequently contribute to come back to the project so that everyone can benefit, and the project is moving forward.

However, for the vast majority of Solr users, inventory is more than enough and satisfies all needs.

In other words, before proceeding to change the code, ask on the mailing list (stackoverflow or solr-user), there is a good chance that you really do not need to change any code.

"Quick search with indexing and interleaving terabytes of data" is exactly what Solr was created for. This would be a bad case of Not-Invented - here not to use it or any other similar solutions, such as ElasticSearch, Sphinx, Xapian, etc. If you think that you need to configure or expand the search server in any, consider the license and the base code of each of them. Solr and ElasticSearch are licensed as Apache, so they have no commercial restrictions and are based on the well-known Lucene library.