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

Erick Erickson commented on SOLR-9150:
--------------------------------------

Shawn actually brings up a couple of points that, IMO, shoot down the idea. I 
don't see a reasonable way to support two _different_ types that have the 
suffix stripped later in the process. If 'foo_s' and 'foo_i' would both map to 
'foo'. From there it's all a mess.

All the code in Solr that tries to resolve field names would have to be visited 
unless, as Shawn mentions, managed schemas would have to be updated.

This would get messy really quickly and there still hasn't been a clear case 
made for why this would be worth the complexity.

> Add configuration option to strip type postfix from dynamic field name on 
> document indexing
> -------------------------------------------------------------------------------------------
>
>                 Key: SOLR-9150
>                 URL: https://issues.apache.org/jira/browse/SOLR-9150
>             Project: Solr
>          Issue Type: New Feature
>          Components: Server
>    Affects Versions: 6.0
>            Reporter: Peter Horvath
>
> In some cases, incorporating field type indication to the name of a dynamic 
> field is not desirable. 
> It would be great if there was a configuration option (global, instance level 
> or collection-level), which instructed Solr to create dynamic fields with the 
> type postfix stripped. 
> For example, suppose the schema contained a dynamic field with a name of 
> "*_i". If the user attempts to index a document with a "cost_i" field, but no 
> explicit "cost_i" field is defined in the schema, then a "cost" field 
> (without "_i" postfix) would be created with the field type and analysis 
> defined for "*_i". As a result queries could be executed against the dynamic 
> field being referred to without the type indicator postfix: "cost:10"
> To retain backward compatibility, this feature should have to be enabled 
> explicitly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to