[ 
https://issues.apache.org/jira/browse/SOLR-4894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708567#comment-13708567
 ] 

Steve Rowe commented on SOLR-4894:
----------------------------------

bq. Is there a plan to support specifying fieldType alongside with field name?

That's (indirectly/partially) possible now, in two ways:

# Using dynamic fields, which encode fieldType via a field name prefix or 
suffix.
# Using AddSchemaFieldsUpdateProcessor and sending doc updates via JSON - its 
typed values are mapped to fieldTypes in the ASFUPF config in solrconfig.xml.

That said, it might be useful to include the capability you describe in the 
future.  Though I haven't made plans to do so myself, patches are welcome!
                
> Add a new update processor factory that will dynamically add fields to the 
> schema if an input document contains unknown fields
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-4894
>                 URL: https://issues.apache.org/jira/browse/SOLR-4894
>             Project: Solr
>          Issue Type: New Feature
>          Components: update
>            Reporter: Steve Rowe
>            Assignee: Steve Rowe
>            Priority: Minor
>             Fix For: 5.0, 4.4
>
>         Attachments: SOLR-4894.patch
>
>
> Previous {{ParseFooUpdateProcessorFactory}}-s (see SOLR-4892) in the same 
> chain will detect, parse and convert unknown fields’ {{String}}-typed values 
> to the appropriate Java object type.
> This factory will take as configuration a set of mappings from Java object 
> type to schema field type.
> {{ManagedIndexSchema.addFields()}} adds new fields to the schema.
> If schema addition fails for any field, addition is re-attempted only for 
> those that don’t match any schema field.  This process is repeated, either 
> until all new fields are successfully added, or until there are no new fields 
> (because the fields that were new when this update chain started its work 
> were subsequently added by a different update request, possibly on a 
> different node).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to