[
https://issues.apache.org/jira/browse/SOLR-9150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297226#comment-15297226
]
Kevin Risden edited comment on SOLR-9150 at 5/23/16 10:24 PM:
--------------------------------------------------------------
I haven't put too much thought into this, but how about an alternative idea
that may solve the same problem. Field name aliases ie: foo would point to
foo_i when querying. I have no idea what kind of impact this would have
querying to resolve this. This would enable dynamic fields but have a defined
alias mapping added later. Basically agree with what [~erickerickson] is saying.
I can see the case where querying and needing to know the _type would be a
pain, but at indexing time the _type would be known.
was (Author: risdenk):
I haven't put too much thought into this, but how about an alternative idea
that may solve the same problem. Field name aliases ie: foo would point to
foo_i when querying. I have no idea what kind of impact this would have
querying to resolve this. This would enable dynamic fields but have a defined
alias mapping added later.
I can see the case where querying and needing to know the _type would be a
pain, but at indexing time the _type would be known.
> 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: [email protected]
For additional commands, e-mail: [email protected]
