Re: Error: _version_field must exist in schema

2012-11-22 Thread Nick Zadrozny
On Wed, Oct 17, 2012 at 3:20 PM, Dotan Cohen dotanco...@gmail.com wrote:

 I do have a Solr 4 Beta index running on Websolr that does not have
 such a field. It works, but throws many Service Unavailable and
 Communication Error errors. Might the lack of the _version_ field be
 the reason?


Belated reply, but this is probably something you should let us know about
directly at supp...@onemorecloud.com if it happens again. Cheers.

-- 
Nick Zadrozny

Cofounder, One More Cloud

websolr.com https://websolr.com/home • bonsai.io http://bonsai.io/home

Hassle-free hosted full-text search,
powered by Apache Solr and ElasticSearch.


Re: Error: _version_field must exist in schema

2012-11-22 Thread Dotan Cohen
On Thu, Nov 22, 2012 at 9:26 PM, Nick Zadrozny n...@onemorecloud.com wrote:
 Belated reply, but this is probably something you should let us know about
 directly at supp...@onemorecloud.com if it happens again. Cheers.


Hi Nick. This particular issue was on a Solr 4 instance on AWS, not on
the Websolr account. But I commend you taking notice and taking an
interest. Thank you!

-- 
Dotan Cohen

http://gibberish.co.il
http://what-is-what.com


Re: Error: _version_field must exist in schema

2012-10-18 Thread Dotan Cohen
On Thu, Oct 18, 2012 at 12:25 AM, Rafał Kuć r@solr.pl wrote:
 Hello!

 You can some find information about requirements of SolrCloud at
 http://wiki.apache.org/solr/SolrCloud . I don't know if _version_ is
 mentioned elsewhere.

 As for Websolr - I'm afraid I can't say anything about the cause of
 those errors without seeing the exception.


I see, thanks. I don't think that I'm using the SolrCloud feature. Is
it enable because there exist solr/collection1 and also
multicore/core0?

-- 
Dotan Cohen

http://gibberish.co.il
http://what-is-what.com


Re: Error: _version_field must exist in schema

2012-10-18 Thread Rafał Kuć
Hello!

Look at your solrconfig.xml file, you should see something like that:

updateLog
 str name=dir${solr.data.dir:}/str
/updateLog

Just remove it and Solr shouldn't bother you with the version field
information. However remember that some features won't work (like the
real time get or partial documents update).

You can also add _version_ field to your schema and forget about it.
You don't need to do anything with it as it is used internally by
Solr. 

-- 
Regards,
 Rafał Kuć
 Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch - ElasticSearch

 On Thu, Oct 18, 2012 at 12:25 AM, Rafał Kuć r@solr.pl wrote:
 Hello!

 You can some find information about requirements of SolrCloud at
 http://wiki.apache.org/solr/SolrCloud . I don't know if _version_ is
 mentioned elsewhere.

 As for Websolr - I'm afraid I can't say anything about the cause of
 those errors without seeing the exception.


 I see, thanks. I don't think that I'm using the SolrCloud feature. Is
 it enable because there exist solr/collection1 and also
 multicore/core0?



Re: Error: _version_field must exist in schema

2012-10-18 Thread Dotan Cohen
On Thu, Oct 18, 2012 at 9:21 AM, Rafał Kuć r@solr.pl wrote:
 Hello!

 Look at your solrconfig.xml file, you should see something like that:

 updateLog
  str name=dir${solr.data.dir:}/str
 /updateLog

 Just remove it and Solr shouldn't bother you with the version field
 information. However remember that some features won't work (like the
 real time get or partial documents update).


Thank you. Is there any place where this is documented? It certainly
does not appear in the relevant wiki page:
http://wiki.apache.org/solr/SolrConfigXml


 You can also add _version_ field to your schema and forget about it.
 You don't need to do anything with it as it is used internally by
 Solr.


That is exactly my plan, but I would also like to understand more
about what is going on. I don't like cut-and-paste programming.

Thank you very much!


-- 
Dotan Cohen

http://gibberish.co.il
http://what-is-what.com


Re: Error: _version_field must exist in schema

2012-10-18 Thread Erick Erickson
I've updated the schema.xml page, see
http://wiki.apache.org/solr/SchemaXml#Recommended_fields

Care to change the schema.xml file to warn about this too and
submit a patch?

Best
Erick


On Thu, Oct 18, 2012 at 4:21 AM, Dotan Cohen dotanco...@gmail.com wrote:
 On Thu, Oct 18, 2012 at 9:21 AM, Rafał Kuć r@solr.pl wrote:
 Hello!

 Look at your solrconfig.xml file, you should see something like that:

 updateLog
  str name=dir${solr.data.dir:}/str
 /updateLog

 Just remove it and Solr shouldn't bother you with the version field
 information. However remember that some features won't work (like the
 real time get or partial documents update).


 Thank you. Is there any place where this is documented? It certainly
 does not appear in the relevant wiki page:
 http://wiki.apache.org/solr/SolrConfigXml


 You can also add _version_ field to your schema and forget about it.
 You don't need to do anything with it as it is used internally by
 Solr.


 That is exactly my plan, but I would also like to understand more
 about what is going on. I don't like cut-and-paste programming.

 Thank you very much!


 --
 Dotan Cohen

 http://gibberish.co.il
 http://what-is-what.com


Re: Error: _version_field must exist in schema

2012-10-18 Thread Dotan Cohen
On Thu, Oct 18, 2012 at 1:06 PM, Erick Erickson erickerick...@gmail.com wrote:
 I've updated the schema.xml page, see
 http://wiki.apache.org/solr/SchemaXml#Recommended_fields


Great, thanks!


 Care to change the schema.xml file to warn about this too and
 submit a patch?


If you are referring to the example schema.xml file provided with
Solr, then I'd love to. I'm signing up for the dev list now. Thanks.

-- 
Dotan Cohen

http://gibberish.co.il
http://what-is-what.com


Re: Error: _version_field must exist in schema

2012-10-17 Thread Rafał Kuć
Hello!

The _version_ field is needed by some of Solr 4.0 functionality like
transaction log or partial documents update. If you want to use them,
just update your schema.xml and put the _version_ field definition
there.

However if you don't want those, you can remove the transaction log
configuration in your solrconfig.xml. However please remember that
when using SolrCloud you'll need that field. 

-- 
Regards,
 Rafał Kuć
 Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch - ElasticSearch

 On a stock Solr 4 install, I can run the server fine if I don't change
 any config files. When I replace the example
 solr/collection1/conf/schema.xml I get the following error:
 collection1:
 org.apache.solr.common.SolrException:org.apache.solr.common.SolrException:
 Unable to use updateLog: _version_field must exist in schema, using
 indexed=true stored=true and multiValued=false (_version_ does
 not exist)

 Here is the replacement schema:
 ?xml version=1.0 encoding=UTF-8?
 schema name=discoapiRecent version=0.3
 types
 fieldType name=string class=solr.StrField
omitNorms=true/
 /types
 fields
 field name=id type=string stored=true
 multiValued=false indexed=true required=true/
 field name=text type=string stored=true
 multiValued=false indexed=true/
 /fields
 defaultSearchFieldtext/defaultSearchField
 solrQueryParser defaultOperator=AND/
 uniqueKeyid/uniqueKey
 /schema


 I see that the original schema.xml had a _version_ field, but how does
 Solr know that? I did remove the original index thinking that maybe
 the extant documents were crying for the _version_ field, but removing
 that index did not help. Grepping for _version_ doesn't show it
 existing anywhere else in the collection1 index:

 ~/apache-solr-4.0.0/example$ grep -ir _version_ *
 multicore/core1/conf/schema.xml:  field name=_version_ type=long
 indexed=true  stored=true/
 multicore/core0/conf/schema.xml:  field name=_version_ type=long
indexed=true  stored=true/
 solr/collection1/conf/schema.xml.ORIGINAL:  trailing underscores
 (e.g. _version_) are reserved.
 solr/collection1/conf/schema.xml.ORIGINAL:   field name=_version_
 type=long indexed=true stored=true/

 Where might the problem lie? And other than the index and schema.xml
 (and possibly solrconfig.xml) what else should I purge to get a
 clean index?

 Thanks.



Re: Error: _version_field must exist in schema

2012-10-17 Thread Dotan Cohen
On Thu, Oct 18, 2012 at 12:09 AM, Rafał Kuć r@solr.pl wrote:
 Hello!

 The _version_ field is needed by some of Solr 4.0 functionality like
 transaction log or partial documents update. If you want to use them,
 just update your schema.xml and put the _version_ field definition
 there.

 However if you don't want those, you can remove the transaction log
 configuration in your solrconfig.xml. However please remember that
 when using SolrCloud you'll need that field.


Thanks. Where is that bit documented? I don't see it on the Solr wiki:
http://wiki.apache.org/solr/SchemaXml

I do have a Solr 4 Beta index running on Websolr that does not have
such a field. It works, but throws many Service Unavailable and
Communication Error errors. Might the lack of the _version_ field be
the reason?

Thanks.

-- 
Dotan Cohen

http://gibberish.co.il
http://what-is-what.com


Re: Error: _version_field must exist in schema

2012-10-17 Thread Rafał Kuć
Hello!

You can some find information about requirements of SolrCloud at
http://wiki.apache.org/solr/SolrCloud . I don't know if _version_ is
mentioned elsewhere.

As for Websolr - I'm afraid I can't say anything about the cause of
those errors without seeing the exception. 


-- 
Regards,
 Rafał Kuć
 Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch - ElasticSearch

 On Thu, Oct 18, 2012 at 12:09 AM, Rafał Kuć r@solr.pl wrote:
 Hello!

 The _version_ field is needed by some of Solr 4.0 functionality like
 transaction log or partial documents update. If you want to use them,
 just update your schema.xml and put the _version_ field definition
 there.

 However if you don't want those, you can remove the transaction log
 configuration in your solrconfig.xml. However please remember that
 when using SolrCloud you'll need that field.


 Thanks. Where is that bit documented? I don't see it on the Solr wiki:
 http://wiki.apache.org/solr/SchemaXml

 I do have a Solr 4 Beta index running on Websolr that does not have
 such a field. It works, but throws many Service Unavailable and
 Communication Error errors. Might the lack of the _version_ field be
 the reason?

 Thanks.