Page History

...

1. The Rules of Solr may be changed by consensus.
2. Community over code.
You We will consider your our fellow and future developer developers before your our spiffy code change/fix/feature. We share this project.
3. Develop for long term health.
We will work towards solutions that can maintain - via enforcement, documentation, and consideration. I'm not as smart as you, I don't have as much time as you, and I'm not here for the same reasons as you - but there is work I need to do.
4. Code reviews for anything beyond trivial.
We will not be a kitchen sink or a pet project or test bed because of ill timing or current developer level health.

...

To be successful with Solr, all you really need is a good attitude. But if you want to go deeper, this is the required reading list:

1. Java Concurrency
2. Lucene
3. HTTP 1.1 and 2
4. Jetty
5. RandomizedTesting
6. Gradle
7. Apache Solr Reference Guide
8. Developer Docs

...

HTTP does not have this race problem and has much hardier connections that multiple requests can multiplexed over. Solr currently uses a combination of HTTP1.1 and 2.

Lucene

https://lucene.apache.org/

Jetty

Get started here

https://www.eclipse.org/jetty/documentation/current/index.html

...

https://labs.carrotsearch.com/randomizedtesting.html

Gradle

Apache Solr Reference Guide

...