[
https://issues.apache.org/jira/browse/SOLR-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13632524#comment-13632524
]
Robert Muir commented on SOLR-3251:
-----------------------------------
{quote}
On a normal search-side request, yes. Some things may need the latest schema
though... like a codec provider, perhaps realtime-get, the future code to add
new fields on demand (aka type guessing), etc.
{quote}
But my problem is with the API: an IndexSearcher is absolutely the worst place
to have a getter for a moving target: because its all about search.
If for example, realtime-get wants to get the 'latest', it should get it from
request.getCore().getCurrentSchema() (please, name it in such a way that its
not confusing).
Otherwise in general things should use request.getSchema(). SolrIndexSearcher
should not expose the schema: there need not be 3 different ways, 2 of which
have "current" semantics and one of which is immutable across the request. And
its own internal use of "moving target" should be carefully contained.
> 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
> Fix For: 4.3
>
> Attachments: SOLR-3251.patch, SOLR-3251.patch, 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
