[
https://issues.apache.org/jira/browse/SOLR-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13623986#comment-13623986
]
Steve Rowe commented on SOLR-3251:
----------------------------------
{quote}
bq. Similarly, we could disallow new field additions for field types that
specify per-field similarity, docvalues format, or postings format.
AFAIK, at the Lucene level, a field that hasn't been used yet is the same as a
field that doesn't exist (since we don't pre-define fields).
If so, adding a new field at the solr level and using a field for the first
time should be indistinguishable to Lucene? Any issues would seem to be limited
to the interface between Lucene and Solr (such as SchemaCodecFactory).
{quote}
Yeah, similarity is not used at index time, so forget I mentioned that :).
But for the docvalues and postings formats, I was talking about
SchemaCodecFactory, so it is exactly the interface issues I meant to say we
could avoid by not allowing those features for newly added fields. Or maybe I
don't get what you're saying?
My thought was that for schema-less/type-guessing, field types will be fairly
basic, and unlikely to need per-field codec settings.
> dynamically add field to schema
> -------------------------------
>
> Key: SOLR-3251
> URL: https://issues.apache.org/jira/browse/SOLR-3251
> Project: Solr
> Issue Type: New Feature
> Reporter: Yonik Seeley
> Assignee: Steve Rowe
> Attachments: SOLR-3251.patch, SOLR-3251.patch, SOLR-3251.patch
>
>
> One related piece of functionality needed for SOLR-3250 is the ability to
> dynamically add a field to the schema.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
