lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Rowe (JIRA)" <>
Subject [jira] [Commented] (SOLR-9150) Add configuration option to strip type postfix from dynamic field name on document indexing
Date Wed, 25 May 2016 18:44:13 GMT


Steve Rowe commented on SOLR-9150:

bq. Am I right assuming that Solr does not simply rely on the field naming to know the type
of a dynamic field? Or does it?

Solr *does* simply rely on the field name to know the field type for a dynamic field.  Dynamic
field names are of the form {{\*suffix}} or {{prefix\*}} - i.e. a glob that matches field
names that include a fixed suffix or prefix\[1].  There is a single fieldtype associated with
each dynamic field, so once a match is made, the fieldtype is also known.

bq. This does not necessarily has to be implemented in the core engine: I would be happy with
any solution, that allowed me to create fields without having to query the current schema
of a collection and then issue massive number of schema change requests.

Note that you can send a single request that contains any number of changes, though if any
one fails, none are applied.

\[1] There can also be a {{\*}} dynamic field, which matches all field names. 

> Add configuration option to strip type postfix from dynamic field name on document indexing
> -------------------------------------------------------------------------------------------
>                 Key: SOLR-9150
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message