Background:
We have around 100 web sites of various sizes (in terms of indexable content)
and I'm trying to come up with the best architectural design from a performance
perspective.
- Each of the sites has a need for DEV, TEST and LIVE indices.
- The content on the sites divided into 5 group
This is question is probably better set on the Drupal groups page for Apache
Solr http://groups.drupal.org/lucene-nutch-and-solr
As this is more of a Drupal issue than a Solr issue
On 18 Apr 2012, at 16:11, Valentin, AJ wrote:
> I have Apache Solr installed with my Drupal 7 site and noticed s
This pages gives you everything you need
http://wiki.apache.org/solr/CoreAdmin#CREATE
Regards,
Dave
On 9 May 2012, at 08:32, pprabhcisco123 wrote:
> Hi,
>
>
> I am trying to create core dynamically. what are the configuration
> steps that needs to be followed to do the same. Please l
Hi,
I am testing index time synonyms, stemming etc and it would be great to be able
to view the raw indexed data is there a way to do this using either Lucene
tools or the admin Solr admin interface
Regards,
David
search_returns_too_many_.2BAC8_too_little_.2BAC8_unexpected_results.2C_how_to_debug.3F
>
>
> 2011/4/19 Dave Stuart
>
>> Hi,
>>
>> I am testing index time synonyms, stemming etc and it would be great to be
>> able to view the raw indexed data is there a way to
Hi Daniel,
Yes there is a one-to-one relationship between Solr indices and cores. The one
to many comes when you look at the relationship between cores and tomcat/jetty
webapps instances. This gives you the ability to clone, add and swap cores
around.
See for for core manipulation functions:
h
It looks as though you have a password set on your unix server. you will need
to either remove this or ti add the password into the connection string
e.g. readonly:[yourpassword]@'10.86.29.32'
>> 'readonly'@'10.86.29.32'
>> (using password: NO)"
On 30 Oct 2012, at 09:08, kunal sachdeva wrote:
Hi Joe,
I have a suspect that this is a drupal thing as opposed to Solr specifically.
Probably the best approach would be to add a extra field that is the raw data
for display instead of using the content field which get a fair amount of
processing.
I would recommend opening a issue on the apa
