You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by "Shawn Heisey (JIRA)" <ji...@apache.org> on 2015/02/21 00:26:13 UTC

[jira] [Closed] (SOLR-7133) Solr is required to be restarted after updating with flume

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

Shawn Heisey closed SOLR-7133.
------------------------------
    Resolution: Invalid

In the unlikely event that this does turn out to be a bug, the issue can be re-opened.

> Solr is required to be restarted after updating with flume
> ----------------------------------------------------------
>
>                 Key: SOLR-7133
>                 URL: https://issues.apache.org/jira/browse/SOLR-7133
>             Project: Solr
>          Issue Type: Bug
>          Components: Data-driven Schema
>    Affects Versions: 4.10.3
>         Environment: Oracle Linux 6.6
> solr 4.10.3
> flume-1.4.0
>            Reporter: DeepakVohra
>
> After updating Solr with Flume the Solr is required to be restarted before the updates get listed with /select query. Shouldn't the updates get listed with /select query without restarting Solr as with updating from the Solr Admin Console?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org