You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Ryan McKinley (JIRA)" <ji...@apache.org> on 2007/04/29 01:26:15 UTC
[jira] Assigned: (SOLR-181) Support for "Required" field Property
[ https://issues.apache.org/jira/browse/SOLR-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan McKinley reassigned SOLR-181:
----------------------------------
Assignee: Ryan McKinley
> Support for "Required" field Property
> -------------------------------------
>
> Key: SOLR-181
> URL: https://issues.apache.org/jira/browse/SOLR-181
> Project: Solr
> Issue Type: Improvement
> Components: update
> Reporter: Greg Ludington
> Assigned To: Ryan McKinley
> Priority: Minor
> Attachments: solr-181-required-fields.patch, solr-181-required-fields.patch
>
>
> In certain situations, it can be helpful to require every document in your index has a value for a given field. While ideally the indexing client(s) should be responsible enough to add all necessary fields, this patch allows it to be enforced in the Solr schema, by adding a required property to a field entry. For example, with this in the schema:
> <field name="name" type="nametext" indexed="true" stored="true" required="true"/>
> A request to index a document without a name field will result in this response:
> <result status="1">org.apache.solr.core.SolrException: missing required fields: name
> (and then, of course, the stack trace)
> </result>
> The meat of this patch is that DocumentBuilder.getDoc() throws a SolrException if not all required fields have values; this may not work well as is with SOLR-139, Support updateable/modifiable documents, and may have to be changed depending on that issue's final disposition.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.