> I am reading similar issues and it says "initial join implementation is
O(nterms)".. What does this mean?
It enumerates all par_id terms every time. As an alternative for some of
field types you can add {!join ... score=none ...}.. to trigger Lucene's
join algorithm with O(fromDocs) ie if
First of all, Solr is a _search_ engine, it wasn't built to be an
RDBMS. Whenever I see this question (paraphrasing) "I've indexed my
tables and want to use Solr just like a DB" I cringe.
The join performance goes up with the number of unique values for the
join field. High-cardinality fields are
I am facing a performance problem and could narrow it down to a join query
that we are using. The join is on a unique field.
We have a person profile stored in RDB in a relational way. Like person
name table , address table etc. SOLR indexes are build using this RDB
data,Each children is stored
