You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Erick Erickson (Jira)" <ji...@apache.org> on 2020/09/14 22:29:00 UTC

[jira] [Resolved] (SOLR-14867) Avoiding a Reload using managed schema api

     [ https://issues.apache.org/jira/browse/SOLR-14867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Erick Erickson resolved SOLR-14867.
-----------------------------------
    Resolution: Fixed

Please raise questions like this on the user's list, we try to reserve JIRAs for known bugs/enhancements rather than usage questions. The JIRA system is not a support portal.

See: 
http://lucene.apache.org/solr/community.html#mailing-lists-irc there are links to both Lucene and Solr mailing lists there.

A _lot_ more people will see your question on that list and may be able to help more quickly.

If it's determined that this really is a code issue or enhancement to Lucene or Solr and not a configuration/usage problem, we can raise a new JIRA or reopen this one.

 But to answer your question, no, there's no way to avoid the reload when you modify the schema. 

And yes, dynamic fields are a completely different beast and do _not_ require reloads. Also, dynamic fields aren't any different than explicitly-defined fields in terms of efficiency etc. when searching...

> Avoiding a Reload using managed schema api
> ------------------------------------------
>
>                 Key: SOLR-14867
>                 URL: https://issues.apache.org/jira/browse/SOLR-14867
>             Project: Solr
>          Issue Type: Wish
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Kevin Van Lieshout
>            Priority: Major
>
> Hi I am a user of Solr in my application and I am trying to avoid needed to reload collections after many different collections are in my solr instance. I use the schema api to add fields and copy fields to my schema based on the data being indexed which needs a reload, but this reload is very tasking as data grows. Is there anyway around this? or if i use a standard schema and use dynamic fields instead, can I avoid the use of reloading collections each time I index a dataset? Let me know if this makes sense



--
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