Re: [jira] Updated: (SOLR-619) Register copyField at runtime

[Georgios Stamatis <ge...@arisem.com>]

Ryan McKinley (JIRA) wrote:
>      [ https://issues.apache.org/jira/browse/SOLR-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Ryan McKinley updated SOLR-619:
> -------------------------------
>
>     Attachment: SOLR-619-RuntimeSchema.patch
>
> updated patch that includes tests and better javadocs describing when each call is safe to make.  This also adds a function: refreshAnalyzers() that reloads the anylyzers.  This is necessary if you modify the schema fields returned from getFields()
>
> This does not add any synchronization, it just relies on things being called within inform()
>
>
>
>   
>> Register copyField at runtime
>> -----------------------------
>>
>>                 Key: SOLR-619
>>                 URL: https://issues.apache.org/jira/browse/SOLR-619
>>             Project: Solr
>>          Issue Type: New Feature
>>            Reporter: Ryan McKinley
>>            Assignee: Ryan McKinley
>>            Priority: Minor
>>             Fix For: 1.3
>>
>>         Attachments: SOLR-619-RuntimeSchema.patch, SOLR-619-RuntimeSchema.patch, SOLR-619.patch
>>
>>
>> In order to enable runtime schema manipulation, it would be nice to register copy fields manually rather then requiring them to be registered via schema.xml.
>>     
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>   

Hello,

I recently saw this issue and have some questions:

   1.

      What is the vision of this issue, will copy fields continue to
      exist in schema.xml?

   2.

      Is it possible to add (merge) SOLR-538 [copy field max length] to
      this issue? If yes I can provide a patch that merges the SOLR-538
      to SOLR-619.

Thanks in advance,

Georgios.