You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Erick Erickson (JIRA)" <ji...@apache.org> on 2016/05/23 17:08:12 UTC
[jira] [Commented] (SOLR-9150) Add configuration option to strip
type postfix from dynamic field name on document indexing
[ https://issues.apache.org/jira/browse/SOLR-9150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15296658#comment-15296658 ]
Erick Erickson commented on SOLR-9150:
--------------------------------------
I'm not big fan of this idea at first blush, it seems like unnecessary complexity in the _engine_ to support... I'm not sure what.
"Not desirable" because of what? Convenience at the app layer? Some UI that has a pick list? It'd be useful to have a statement of what problem this capability is attempting to solve before jumping in and making changes, there might be other approaches already in place. There's already "field aliasing" to allow display of a different field name than it actually is for instance.
I'm not totally against the idea, I just don't see a clear problem statement here.
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org