: How about another approach - expose all Solr admin data via HTTP/XML,
: just like it's done with search requests?
: That way one can build some overarching/external Admin console, talk to
: Solr remotely via HTTP to get some admin info (e.g. cache, stats, etc.)
: as XML, transforming it locally
Hi Hoss,
How about another approach - expose all Solr admin data via HTTP/XML, just like
it's done with search requests?
That way one can build some overarching/external Admin console, talk to Solr
remotely via HTTP to get some admin info (e.g. cache, stats, etc.) as XML,
transforming it local
: now I have simple Lucene Indexes that basically re-created once daily and
: that simply isn't doing the job for about 30% of my content.
do you mean it takes to long to index all your content so you can only do
part of it, or do you mean it's not indexing some of your conent "well" ?
: For in
Nah, he didn't write any DB -> JDBC -> Lucene examples in Lucene in Action, and
neither did Erik. Lazy guys, I tell you!
Btw. your situation/problem is very common. Just treat your DB as "the truth",
and your Solr/Lucene instance as a mechanism to quickly find bits of that
truth. Design your
