So, is there any method other than Luke to get the index information of all
the cores?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Luke-using-shards-tp3865816p4334603.html
Sent from the Solr - User mailing list archive at Nabble.com.
I have this method: http://localhost:8983/solr/core1/select?wt=csv
This gives all the field names found in the core.
But when I do a shards like this:
http://localhost:8983/solr/core1/select?wt=csv&shards=localhost:8983/solr/core1,localhost:8983/solr/core2,
I get no output. Have you any idea to
On 5/11/2017 4:32 AM, jawaharsam wrote:
> Since it has been 5 years, is there any way to view the index information
> from all the cores of Solr?
Both the Luke program (separate from Solr) and the Luke support included
inside Solr can only operate on a single core (Lucene index). These
tools are
Since it has been 5 years, is there any way to view the index information
from all the cores of Solr?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Luke-using-shards-tp3865816p4334598.html
Sent from the Solr - User mailing list archive at Nabble.com.
> (http://localhost:8983/solr/admin/luke?shards=localhost:8983/solr,localhost:7574/solr)
If luke did distributed search, it would go into an infinite loop :)
On Thu, Mar 29, 2012 at 5:03 AM, Dmitry Kan wrote:
> One option to try here (not verified) is to set up a Solr front that will
> point to
One option to try here (not verified) is to set up a Solr front that will
point to these two shards. Then try accessing its luke interface via admin
as you did on one of the shards.
But as Erick already pointed out, Luke operates on a lower level than Solr,
so this does not necessarily work.
Dmit
I very much doubt that you can persuade Luke to reach across shards. Shards
are really a higher-level notion, the automatic distribution of requests
across shards is really a Solr-level construct (making use of the lower-
level Lucene capabilities, to be sure). With Luke, you point
it at index file
