lucene-solr-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 YonikSeeley
Date Fri, 01 Apr 2011 17:29:34 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 YonikSeeley.
The comment on this change is: fix broken links, de-clutter by moving out TODOs, remove JIRA
references.
http://wiki.apache.org/solr/SchemaXml?action=diff&rev1=44&rev2=45

--------------------------------------------------

  The schema.xml file contains all of the details about which fields your documents can contain,
and how those fields should be dealt with when adding documents to the index, or when querying
those fields.
  
  A [[http://svn.apache.org/viewvc/lucene/dev/trunk/solr/example/solr/conf/schema.xml?view=markup|sample
Solr schema.xml with detailed comments]] can be found in the Source Repository.
- 
- /!\ :TODO: /!\ we should try to make a DTD for the schema
  
  <<TableOfContents>>
  
@@ -25, +23 @@

  
  `TextField`s can also support Analyzers with highly configurable [[AnalyzersTokenizersTokenFilters|Tokenizers
and Token Filters]].
  
- /!\ :TODO: /!\ do omitNorms and positionIncrementGap have any meaning for non !TextFields?
- 
  Field types that store text (`TextField`, `StrField`) support compression of stored contents:
  
   * `compressed=true|false`
@@ -35, +31 @@

  `compressThreshold` is the minimum length required for text compression to be invoked. 
This applies only if `compressed=true`; a common pattern is to set `compressThreshold` on
the field type definition, and turn compression on and off in the individual field definitions.
  
  === Poly Field Types ===
- /!\ Solr1.5 /!\ See https://issues.apache.org/jira/browse/SOLR-1131.  This discusses uncommitted
code.
- 
  Some !FieldTypes can be "poly" field types.  A Poly !FieldType is one that can potentially
create multiple Fields per "declared" field.  The primary example in Solr is the PointType.
 Depending on the dimension specified, one or more Fields will be created.  For example:
  
  {{{
@@ -133, +127 @@

  === The Default Search Field ===
  The `<defaultSearchField>` is used by Solr when parsing queries to identify which
field name should be searched in queries where an explicit field name has not been used.
  
- /!\ :TODO: /!\ check whether this option is also used by the DisMaxRequestHandler and not
only by the StandardRequestHandler
+ 
  
  === Default query parser operator ===
  The default operator used by Solr's query parser ([[http://lucene.apache.org/solr/docs/api/org/apache/solr/search/SolrQueryParser.html|SolrQueryParser]])
can be configured with <solrQueryParser defaultOperator="AND|OR"/>.  The default operator
is "OR" if unspecified.
@@ -156, +150 @@

  === Similarity ===
  A `<similarity>` declaration can be used to specify the subclass of Similarity that
you want Solr to use when dealing with your index.  If no Similarity class is specified, the
Lucene !DefaultSimilarity is used.  Please see SolrPlugins for information on how to ensure
that your own custom Similarity can be loaded into Solr.
  
+ === TODO ===
+ * Perhaps make a DTD for the schema.
+ * Talk about omitNorms and positionIncrementGap wrt text fields
+ * check whether defaultSearchField is also used by the DisMaxRequestHandler and not only
by the StandardRequestHandler
+ 

Mime
View raw message