You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Alexandre Rafalovitch (Jira)" <ji...@apache.org> on 2020/09/11 13:11:00 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=17194264#comment-17194264 ]
Alexandre Rafalovitch commented on SOLR-9150:
---------------------------------------------
Way late to the conversation, but the use case (of user interface using different field name from stored) can probably be addressed by eDisMax field name aliasing: [https://lucene.apache.org/solr/guide/8_6/the-extended-dismax-query-parser.html#field-aliasing-using-per-field-qf-overrides]
And that's something that can be configured via schema API, so can be done dynamically. Though possibly not from URP.
Either way, this case can be probably closed, there are just too many technical objections for it to be viable.
> 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
> Priority: Major
>
> 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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org