Wicked...you fixed it!
Thanks very much.
Pretty simple in the end I guess...but I thought it might be.
Cheers.
Jeff Newburn wrote:
>
> The important info you are looking for is "undefined field sku at". It
> looks like there may be a copyfield in the schema looking for a field
> named
> s
Well here are the first 10/15 lines:
HTTP Status 500 - Severe errors in solr configuration. Check your log files
for more detailed information on what may be wrong. If you want solr to
continue after configuration errors, change:
false in null
-
The important info you are looking for is "undefined field sku at". It
looks like there may be a copyfield in the schema looking for a field named
sku which does not exist. Just search "sku" in the file and see what comes
up.
On 1/23/09 11:15 AM, "Johnny X" wrote:
>
> Well here are the first
The first 10-15 lines of the jargon might help. Additionally, the full
exceptions will be in the webserver logs (ie tomcat or jetty logs).
On 1/23/09 10:40 AM, "Johnny X" wrote:
>
> Ah, gotcha.
>
> Where do I go to find the log messages? Obviously it prints a lot of jargon
> on the admin pag
Ah, gotcha.
Where do I go to find the log messages? Obviously it prints a lot of jargon
on the admin page reporting the error, but is that what you want?
Jeff Newburn wrote:
>
> Are there any error log messages?
>
> The difference between a string and text is that string is basically
> store
Are there any error log messages?
The difference between a string and text is that string is basically stored
with no modification (it is the solr.StrField). The text type is actually
defined in the fieldtype section and usually contains a tokenizer and some
analyzers (usually stemming, lowercasi
