You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Johnny X <jo...@gmail.com> on 2009/01/23 18:52:51 UTC

Solr schema causing an error

Hi there,


I just configured my Solr schema file to support the data types I wish to
submit for indexing. However, as soon as try and start the Solr server I get
an error trying to reach the admin page.

I know this only has something to do with my definitions in the schema,
because when I tried to revert back to the default schema it worked again.

In my new schema I took out only the example definitions I was told to and
input the below. Can someone tell me what's wrong?

   <field name="Message-ID" type="string" indexed="false" stored="true"/>
   <field name="Date" type="string" indexed="false" stored="true"/>
   <field name="From" type="string" indexed="false" stored="true"/>
   <field name="To" type="string" indexed="false" stored="true"/>
   <field name="Subject" type="string" indexed="false" stored="true"/>
   <field name="Mime-Version" type="string" indexed="false" stored="true"/>		 
   <field name="Content-Type" type="string" indexed="false" stored="true"/>
   <field name="Content-Transfer-Encoding" type="string" indexed="false"
stored="true"/>
   <field name="X-From" type="string" indexed="false" stored="true"/>
   <field name="X-To" type="string" indexed="false" stored="true"/>
   <field name="X-cc" type="string" indexed="false" stored="true"/>
   <field name="X-bcc" type="string" indexed="false" stored="true"/>
   <field name="X-Folder" type="string" indexed="false" stored="true"/>		 
   <field name="X-Origin" type="string" indexed="false" stored="true"/>
   <field name="X-FileName" type="string" indexed="false" stored="true"/>
   <field name="Content" type="string" indexed="true" stored="true"/>


Also, what's the difference between text/string (I tried with both). And am
I right in thinking that I could set the type to "StrField" to prevent any
analysis pre-index?


Cheers for the help!


-- 
View this message in context: http://www.nabble.com/Solr-schema-causing-an-error-tp21629485p21629485.html
Sent from the Solr - User mailing list archive at Nabble.com.


Re: Solr schema causing an error

Posted by Johnny X <jo...@gmail.com>.
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
> 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" <jo...@gmail.com> wrote:
> 
>> 
>> 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:
>> <abortOnConfigurationError>false</abortOnConfigurationError> in null
>> -------------------------------------------------------------
>> org.apache.solr.common.SolrException: undefined field sku at
>> org.apache.solr.schema.IndexSchema.getField(IndexSchema.java:994) at
>> org.apache.solr.schema.IndexSchema.registerCopyField(IndexSchema.java:652)
>> at org.apache.solr.schema.IndexSchema.readSchema(IndexSchema.java:613) at
>> org.apache.solr.schema.IndexSchema.<init>(IndexSchema.java:92) at
>> org.apache.solr.core.SolrCore.<init>(SolrCore.java:412) at
>> org.apache.solr.core.CoreContainer$Initializer.initialize(CoreContainer.java:1
>> 19)
>> at
>> org.apache.solr.servlet.SolrDispatchFilter.init(SolrDispatchFilter.java:69)
>> at
>> org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterCo
>> nfig.java:275)
>> at
>> org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilte
>> rConfig.java:397)
>> at
>> org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfi
>> g.java:108)
>> at
>> 
> org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3709>
> )
>> at
>> org.apache.catalina.core.StandardContext.start(StandardContext.java:4363)
>> at
>> 
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791>
> )
>> at
>> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
>> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
>> at
>> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:830) at
>> org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:719) at
>> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490) at
>> org.apache.catalina.startup.HostConfig.start(HostConfig.java:1149) at
>> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
>> at
>> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.
>> java:117)
>> at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
>> at
>> org.apache.catalina.core.StandardHost.start(StandardHost.java:719) at
>> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at
>> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at
>> org.apache.catalina.core.StandardService.start(StandardService.java:516)
>> at
>> org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at
>> org.apache.catalina.startup.Catalina.start(Catalina.java:578) at
>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
>> sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at
>> java.lang.reflect.Method.invoke(Unknown Source) at
>> org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at
>> org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
>> 
>> 
>> 
>> Jeff Newburn wrote:
>>> 
>>> 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" <jo...@gmail.com> wrote:
>>> 
>>>> 
>>>> 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
>>>>> 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, lowercasing, deduping).
>>>>> 
>>>>> 
>>>>> On 1/23/09 9:52 AM, "Johnny X" <jo...@gmail.com> wrote:
>>>>> 
>>>>>> 
>>>>>> Hi there,
>>>>>> 
>>>>>> 
>>>>>> I just configured my Solr schema file to support the data types I
>>>>>> wish
>>>>>> to
>>>>>> submit for indexing. However, as soon as try and start the Solr
>>>>>> server
>>>>>> I
>>>>>> get
>>>>>> an error trying to reach the admin page.
>>>>>> 
>>>>>> I know this only has something to do with my definitions in the
>>>>>> schema,
>>>>>> because when I tried to revert back to the default schema it worked
>>>>>> again.
>>>>>> 
>>>>>> In my new schema I took out only the example definitions I was told
>>>>>> to
>>>>>> and
>>>>>> input the below. Can someone tell me what's wrong?
>>>>>> 
>>>>>>    <field name="Message-ID" type="string" indexed="false"
>>>>>> stored="true"/>
>>>>>>    <field name="Date" type="string" indexed="false" stored="true"/>
>>>>>>    <field name="From" type="string" indexed="false" stored="true"/>
>>>>>>    <field name="To" type="string" indexed="false" stored="true"/>
>>>>>>    <field name="Subject" type="string" indexed="false"
>>>>>> stored="true"/>
>>>>>>    <field name="Mime-Version" type="string" indexed="false"
>>>>>> stored="true"/>
>>>>>>    <field name="Content-Type" type="string" indexed="false"
>>>>>> stored="true"/>
>>>>>>    <field name="Content-Transfer-Encoding" type="string"
>>>>>> indexed="false"
>>>>>> stored="true"/>
>>>>>>    <field name="X-From" type="string" indexed="false" stored="true"/>
>>>>>>    <field name="X-To" type="string" indexed="false" stored="true"/>
>>>>>>    <field name="X-cc" type="string" indexed="false" stored="true"/>
>>>>>>    <field name="X-bcc" type="string" indexed="false" stored="true"/>
>>>>>>    <field name="X-Folder" type="string" indexed="false"
>>>>>> stored="true"/>
>>>>>>    <field name="X-Origin" type="string" indexed="false"
>>>>>> stored="true"/>
>>>>>>    <field name="X-FileName" type="string" indexed="false"
>>>>>> stored="true"/>
>>>>>>    <field name="Content" type="string" indexed="true" stored="true"/>
>>>>>> 
>>>>>> 
>>>>>> Also, what's the difference between text/string (I tried with both).
>>>>>> And
>>>>>> am
>>>>>> I right in thinking that I could set the type to "StrField" to
>>>>>> prevent
>>>>>> any
>>>>>> analysis pre-index?
>>>>>> 
>>>>>> 
>>>>>> Cheers for the help!
>>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>> 
>>> 
>>> 
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Solr-schema-causing-an-error-tp21629485p21631084.html
Sent from the Solr - User mailing list archive at Nabble.com.


Re: Solr schema causing an error

Posted by Jeff Newburn <jn...@zappos.com>.
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" <jo...@gmail.com> wrote:

> 
> 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:
> <abortOnConfigurationError>false</abortOnConfigurationError> in null
> -------------------------------------------------------------
> org.apache.solr.common.SolrException: undefined field sku at
> org.apache.solr.schema.IndexSchema.getField(IndexSchema.java:994) at
> org.apache.solr.schema.IndexSchema.registerCopyField(IndexSchema.java:652)
> at org.apache.solr.schema.IndexSchema.readSchema(IndexSchema.java:613) at
> org.apache.solr.schema.IndexSchema.<init>(IndexSchema.java:92) at
> org.apache.solr.core.SolrCore.<init>(SolrCore.java:412) at
> org.apache.solr.core.CoreContainer$Initializer.initialize(CoreContainer.java:1
> 19)
> at
> org.apache.solr.servlet.SolrDispatchFilter.init(SolrDispatchFilter.java:69)
> at
> org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterCo
> nfig.java:275)
> at
> org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilte
> rConfig.java:397)
> at
> org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfi
> g.java:108)
> at
> 
org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3709>
)
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:4363)
> at
> 
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791>
)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) at
> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:830) at
> org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:719) at
> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490) at
> org.apache.catalina.startup.HostConfig.start(HostConfig.java:1149) at
> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
> at
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.
> java:117)
> at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at
> org.apache.catalina.core.StandardHost.start(StandardHost.java:719) at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at
> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at
> org.apache.catalina.core.StandardService.start(StandardService.java:516) at
> org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at
> org.apache.catalina.startup.Catalina.start(Catalina.java:578) at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at
> java.lang.reflect.Method.invoke(Unknown Source) at
> org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at
> org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
> 
> 
> 
> Jeff Newburn wrote:
>> 
>> 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" <jo...@gmail.com> wrote:
>> 
>>> 
>>> 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
>>>> 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, lowercasing, deduping).
>>>> 
>>>> 
>>>> On 1/23/09 9:52 AM, "Johnny X" <jo...@gmail.com> wrote:
>>>> 
>>>>> 
>>>>> Hi there,
>>>>> 
>>>>> 
>>>>> I just configured my Solr schema file to support the data types I wish
>>>>> to
>>>>> submit for indexing. However, as soon as try and start the Solr server
>>>>> I
>>>>> get
>>>>> an error trying to reach the admin page.
>>>>> 
>>>>> I know this only has something to do with my definitions in the schema,
>>>>> because when I tried to revert back to the default schema it worked
>>>>> again.
>>>>> 
>>>>> In my new schema I took out only the example definitions I was told to
>>>>> and
>>>>> input the below. Can someone tell me what's wrong?
>>>>> 
>>>>>    <field name="Message-ID" type="string" indexed="false"
>>>>> stored="true"/>
>>>>>    <field name="Date" type="string" indexed="false" stored="true"/>
>>>>>    <field name="From" type="string" indexed="false" stored="true"/>
>>>>>    <field name="To" type="string" indexed="false" stored="true"/>
>>>>>    <field name="Subject" type="string" indexed="false" stored="true"/>
>>>>>    <field name="Mime-Version" type="string" indexed="false"
>>>>> stored="true"/>
>>>>>    <field name="Content-Type" type="string" indexed="false"
>>>>> stored="true"/>
>>>>>    <field name="Content-Transfer-Encoding" type="string"
>>>>> indexed="false"
>>>>> stored="true"/>
>>>>>    <field name="X-From" type="string" indexed="false" stored="true"/>
>>>>>    <field name="X-To" type="string" indexed="false" stored="true"/>
>>>>>    <field name="X-cc" type="string" indexed="false" stored="true"/>
>>>>>    <field name="X-bcc" type="string" indexed="false" stored="true"/>
>>>>>    <field name="X-Folder" type="string" indexed="false" stored="true"/>
>>>>>    <field name="X-Origin" type="string" indexed="false" stored="true"/>
>>>>>    <field name="X-FileName" type="string" indexed="false"
>>>>> stored="true"/>
>>>>>    <field name="Content" type="string" indexed="true" stored="true"/>
>>>>> 
>>>>> 
>>>>> Also, what's the difference between text/string (I tried with both).
>>>>> And
>>>>> am
>>>>> I right in thinking that I could set the type to "StrField" to prevent
>>>>> any
>>>>> analysis pre-index?
>>>>> 
>>>>> 
>>>>> Cheers for the help!
>>>>> 
>>>> 
>>>> 
>>>> 
>> 
>> 
>> 


Re: Solr schema causing an error

Posted by Johnny X <jo...@gmail.com>.
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:
<abortOnConfigurationError>false</abortOnConfigurationError> in null
-------------------------------------------------------------
org.apache.solr.common.SolrException: undefined field sku at
org.apache.solr.schema.IndexSchema.getField(IndexSchema.java:994) at
org.apache.solr.schema.IndexSchema.registerCopyField(IndexSchema.java:652)
at org.apache.solr.schema.IndexSchema.readSchema(IndexSchema.java:613) at
org.apache.solr.schema.IndexSchema.<init>(IndexSchema.java:92) at
org.apache.solr.core.SolrCore.<init>(SolrCore.java:412) at
org.apache.solr.core.CoreContainer$Initializer.initialize(CoreContainer.java:119)
at
org.apache.solr.servlet.SolrDispatchFilter.init(SolrDispatchFilter.java:69)
at
org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275)
at
org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:397)
at
org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:108)
at
org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3709)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4363)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) at
org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:830) at
org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:719) at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490) at
org.apache.catalina.startup.HostConfig.start(HostConfig.java:1149) at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at
org.apache.catalina.core.StandardHost.start(StandardHost.java:719) at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at
org.apache.catalina.core.StandardService.start(StandardService.java:516) at
org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at
org.apache.catalina.startup.Catalina.start(Catalina.java:578) at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at
sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at
java.lang.reflect.Method.invoke(Unknown Source) at
org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at
org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)



Jeff Newburn wrote:
> 
> 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" <jo...@gmail.com> wrote:
> 
>> 
>> 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
>>> 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, lowercasing, deduping).
>>> 
>>> 
>>> On 1/23/09 9:52 AM, "Johnny X" <jo...@gmail.com> wrote:
>>> 
>>>> 
>>>> Hi there,
>>>> 
>>>> 
>>>> I just configured my Solr schema file to support the data types I wish
>>>> to
>>>> submit for indexing. However, as soon as try and start the Solr server
>>>> I
>>>> get
>>>> an error trying to reach the admin page.
>>>> 
>>>> I know this only has something to do with my definitions in the schema,
>>>> because when I tried to revert back to the default schema it worked
>>>> again.
>>>> 
>>>> In my new schema I took out only the example definitions I was told to
>>>> and
>>>> input the below. Can someone tell me what's wrong?
>>>> 
>>>>    <field name="Message-ID" type="string" indexed="false"
>>>> stored="true"/>
>>>>    <field name="Date" type="string" indexed="false" stored="true"/>
>>>>    <field name="From" type="string" indexed="false" stored="true"/>
>>>>    <field name="To" type="string" indexed="false" stored="true"/>
>>>>    <field name="Subject" type="string" indexed="false" stored="true"/>
>>>>    <field name="Mime-Version" type="string" indexed="false"
>>>> stored="true"/>
>>>>    <field name="Content-Type" type="string" indexed="false"
>>>> stored="true"/>
>>>>    <field name="Content-Transfer-Encoding" type="string"
>>>> indexed="false"
>>>> stored="true"/>
>>>>    <field name="X-From" type="string" indexed="false" stored="true"/>
>>>>    <field name="X-To" type="string" indexed="false" stored="true"/>
>>>>    <field name="X-cc" type="string" indexed="false" stored="true"/>
>>>>    <field name="X-bcc" type="string" indexed="false" stored="true"/>
>>>>    <field name="X-Folder" type="string" indexed="false" stored="true"/>
>>>>    <field name="X-Origin" type="string" indexed="false" stored="true"/>
>>>>    <field name="X-FileName" type="string" indexed="false"
>>>> stored="true"/>
>>>>    <field name="Content" type="string" indexed="true" stored="true"/>
>>>> 
>>>> 
>>>> Also, what's the difference between text/string (I tried with both).
>>>> And
>>>> am
>>>> I right in thinking that I could set the type to "StrField" to prevent
>>>> any
>>>> analysis pre-index?
>>>> 
>>>> 
>>>> Cheers for the help!
>>>> 
>>> 
>>> 
>>> 
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Solr-schema-causing-an-error-tp21629485p21630937.html
Sent from the Solr - User mailing list archive at Nabble.com.


Re: Solr schema causing an error

Posted by Jeff Newburn <jn...@zappos.com>.
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" <jo...@gmail.com> wrote:

> 
> 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
>> 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, lowercasing, deduping).
>> 
>> 
>> On 1/23/09 9:52 AM, "Johnny X" <jo...@gmail.com> wrote:
>> 
>>> 
>>> Hi there,
>>> 
>>> 
>>> I just configured my Solr schema file to support the data types I wish to
>>> submit for indexing. However, as soon as try and start the Solr server I
>>> get
>>> an error trying to reach the admin page.
>>> 
>>> I know this only has something to do with my definitions in the schema,
>>> because when I tried to revert back to the default schema it worked
>>> again.
>>> 
>>> In my new schema I took out only the example definitions I was told to
>>> and
>>> input the below. Can someone tell me what's wrong?
>>> 
>>>    <field name="Message-ID" type="string" indexed="false" stored="true"/>
>>>    <field name="Date" type="string" indexed="false" stored="true"/>
>>>    <field name="From" type="string" indexed="false" stored="true"/>
>>>    <field name="To" type="string" indexed="false" stored="true"/>
>>>    <field name="Subject" type="string" indexed="false" stored="true"/>
>>>    <field name="Mime-Version" type="string" indexed="false"
>>> stored="true"/>
>>>    <field name="Content-Type" type="string" indexed="false"
>>> stored="true"/>
>>>    <field name="Content-Transfer-Encoding" type="string" indexed="false"
>>> stored="true"/>
>>>    <field name="X-From" type="string" indexed="false" stored="true"/>
>>>    <field name="X-To" type="string" indexed="false" stored="true"/>
>>>    <field name="X-cc" type="string" indexed="false" stored="true"/>
>>>    <field name="X-bcc" type="string" indexed="false" stored="true"/>
>>>    <field name="X-Folder" type="string" indexed="false" stored="true"/>
>>>    <field name="X-Origin" type="string" indexed="false" stored="true"/>
>>>    <field name="X-FileName" type="string" indexed="false" stored="true"/>
>>>    <field name="Content" type="string" indexed="true" stored="true"/>
>>> 
>>> 
>>> Also, what's the difference between text/string (I tried with both). And
>>> am
>>> I right in thinking that I could set the type to "StrField" to prevent
>>> any
>>> analysis pre-index?
>>> 
>>> 
>>> Cheers for the help!
>>> 
>> 
>> 
>> 


Re: Solr schema causing an error

Posted by Johnny X <jo...@gmail.com>.
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
> 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, lowercasing, deduping).
> 
> 
> On 1/23/09 9:52 AM, "Johnny X" <jo...@gmail.com> wrote:
> 
>> 
>> Hi there,
>> 
>> 
>> I just configured my Solr schema file to support the data types I wish to
>> submit for indexing. However, as soon as try and start the Solr server I
>> get
>> an error trying to reach the admin page.
>> 
>> I know this only has something to do with my definitions in the schema,
>> because when I tried to revert back to the default schema it worked
>> again.
>> 
>> In my new schema I took out only the example definitions I was told to
>> and
>> input the below. Can someone tell me what's wrong?
>> 
>>    <field name="Message-ID" type="string" indexed="false" stored="true"/>
>>    <field name="Date" type="string" indexed="false" stored="true"/>
>>    <field name="From" type="string" indexed="false" stored="true"/>
>>    <field name="To" type="string" indexed="false" stored="true"/>
>>    <field name="Subject" type="string" indexed="false" stored="true"/>
>>    <field name="Mime-Version" type="string" indexed="false"
>> stored="true"/>  
>>    <field name="Content-Type" type="string" indexed="false"
>> stored="true"/>
>>    <field name="Content-Transfer-Encoding" type="string" indexed="false"
>> stored="true"/>
>>    <field name="X-From" type="string" indexed="false" stored="true"/>
>>    <field name="X-To" type="string" indexed="false" stored="true"/>
>>    <field name="X-cc" type="string" indexed="false" stored="true"/>
>>    <field name="X-bcc" type="string" indexed="false" stored="true"/>
>>    <field name="X-Folder" type="string" indexed="false" stored="true"/>  
>>    <field name="X-Origin" type="string" indexed="false" stored="true"/>
>>    <field name="X-FileName" type="string" indexed="false" stored="true"/>
>>    <field name="Content" type="string" indexed="true" stored="true"/>
>> 
>> 
>> Also, what's the difference between text/string (I tried with both). And
>> am
>> I right in thinking that I could set the type to "StrField" to prevent
>> any
>> analysis pre-index?
>> 
>> 
>> Cheers for the help!
>> 
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Solr-schema-causing-an-error-tp21629485p21630425.html
Sent from the Solr - User mailing list archive at Nabble.com.


Re: Solr schema causing an error

Posted by Jeff Newburn <jn...@zappos.com>.
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, lowercasing, deduping).


On 1/23/09 9:52 AM, "Johnny X" <jo...@gmail.com> wrote:

> 
> Hi there,
> 
> 
> I just configured my Solr schema file to support the data types I wish to
> submit for indexing. However, as soon as try and start the Solr server I get
> an error trying to reach the admin page.
> 
> I know this only has something to do with my definitions in the schema,
> because when I tried to revert back to the default schema it worked again.
> 
> In my new schema I took out only the example definitions I was told to and
> input the below. Can someone tell me what's wrong?
> 
>    <field name="Message-ID" type="string" indexed="false" stored="true"/>
>    <field name="Date" type="string" indexed="false" stored="true"/>
>    <field name="From" type="string" indexed="false" stored="true"/>
>    <field name="To" type="string" indexed="false" stored="true"/>
>    <field name="Subject" type="string" indexed="false" stored="true"/>
>    <field name="Mime-Version" type="string" indexed="false" stored="true"/>  
>    <field name="Content-Type" type="string" indexed="false" stored="true"/>
>    <field name="Content-Transfer-Encoding" type="string" indexed="false"
> stored="true"/>
>    <field name="X-From" type="string" indexed="false" stored="true"/>
>    <field name="X-To" type="string" indexed="false" stored="true"/>
>    <field name="X-cc" type="string" indexed="false" stored="true"/>
>    <field name="X-bcc" type="string" indexed="false" stored="true"/>
>    <field name="X-Folder" type="string" indexed="false" stored="true"/>  
>    <field name="X-Origin" type="string" indexed="false" stored="true"/>
>    <field name="X-FileName" type="string" indexed="false" stored="true"/>
>    <field name="Content" type="string" indexed="true" stored="true"/>
> 
> 
> Also, what's the difference between text/string (I tried with both). And am
> I right in thinking that I could set the type to "StrField" to prevent any
> analysis pre-index?
> 
> 
> Cheers for the help!
>