lucene-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Solr Wiki] Update of "SchemaXml" by ShawnHeisey
Date Mon, 19 May 2014 19:49:39 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.

The "SchemaXml" page has been changed by ShawnHeisey:
https://wiki.apache.org/solr/SchemaXml?action=diff&rev1=71&rev2=72

Comment:
Added recommendations for characters to use in field names.

  
  
  == Fields ==
- The `<fields>` section is where you list the individual `<field>` declarations
you wish to use in your documents.  Each `<field>` has a `name` that you will use to
reference it when adding documents or executing searches, and an associated `type` which identifies
the name of the fieldtype you wish to use for this field. There are various field options
that apply to a field. These can be set in the field type declarations, and can also be overridden
at an individual field's declaration.
+ The `<fields>` section is where you list the individual `<field>` declarations
you wish to use in your documents.  Each `<field>` has a `name` that you will use to
reference it when adding documents or executing searches, and an associated `type` which identifies
the name of the fieldtype you wish to use for this field. There are various field options
that apply to a field. These can be set in the field type declarations, and can also be overridden
at an individual field's declaration.  Field names should consist of alphanumeric or underscore
characters only and not start with a digit.  This is not currently strictly enforced, but
other field names will not have first class support from all components and back compatibility
is not guaranteed.  Names with both leading and trailing underscores (e.g. _version_) are
reserved.
  
  === Recommended fields ===
  While these fields aren't strictly mandatory (Solr will run if you remove them fully), Bad
Things happen in some situations if they aren't defined. We recommend that you leave these
fields alone. If you don't use them, there's no appreciable penalty.
-  * id - Almost all Solr installations have this field defined as the <uniqueKey> (see
below). 
+  * id - Almost all Solr installations have this field defined as the <uniqueKey> (see
below).
   * _version_ <!> [[Solr4.0]] - This field is used for optimistic locking in [[http://wiki.apache.org/solr/SolrCloud|SolrCloud]]
and it enables [[http://wiki.apache.org/solr/RealTimeGet|Real Time Get]]. If you remove it
you must also remove the transaction logging from solrconfig.xml, see [[http://wiki.apache.org/solr/RealTimeGet|Real
Time Get]].
  
  === Common field options ===
@@ -202, +202 @@

  
  === Schema version attribute in the root node ===
  
- For the up-to-date documentation, see example [[http://svn.apache.org/viewvc/lucene/dev/trunk/solr/example/solr/collection1/conf/schema.xml?view=markup|example
schema]] shipped with Solr 
+ For the up-to-date documentation, see example [[http://svn.apache.org/viewvc/lucene/dev/trunk/solr/example/solr/collection1/conf/schema.xml?view=markup|example
schema]] shipped with Solr
  
  {{{
  <schema name="example" version="1.5">
    <!-- attribute "name" is the name of this schema and is only used for display purposes.
-        version="x.y" is Solr's version number for the schema syntax and 
+        version="x.y" is Solr's version number for the schema syntax and
         semantics.  It should not normally be changed by applications.
  
-        1.0: multiValued attribute did not exist, all fields are multiValued 
+        1.0: multiValued attribute did not exist, all fields are multiValued
              by nature
-        1.1: multiValued attribute introduced, false by default 
+        1.1: multiValued attribute introduced, false by default
-        1.2: omitTermFreqAndPositions attribute introduced, true by default 
+        1.2: omitTermFreqAndPositions attribute introduced, true by default
              except for text fields.
         1.3: removed optional field compress feature
         1.4: autoGeneratePhraseQueries attribute introduced to drive QueryParser
-             behavior when a single string produces multiple tokens.  Defaults 
+             behavior when a single string produces multiple tokens.  Defaults
              to off for version >= 1.4
-        1.5: omitNorms defaults to true for primitive field types 
+        1.5: omitNorms defaults to true for primitive field types
              (int, float, boolean, string...)
       -->
  }}}

Mime
View raw message