lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <>
Subject [jira] [Commented] (SOLR-7789) Introduce a ConfigSet management API
Date Fri, 28 Aug 2015 14:55:46 GMT


Mark Miller commented on SOLR-7789:

I just hit one of those fails on a normal 'ant test' run. I think we may have to raise this
180 second timeout to be something that is a little more hearty.

   [junit4] FAILURE  181s J1  | TestConfigSetsAPIExclusivity.testAPIExclusivity <<<
   [junit4]    > Throwable #1: java.lang.AssertionError: Unexpected exception: org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException:
Error from server at create the configset time out:180s expected:<0>
but was:<2>
   [junit4]    > 	at __randomizedtesting.SeedInfo.seed([36DBA95D885A778C:4BAEB0A6D1FECEC5]:0)
   [junit4]    > 	at
   [junit4]    > 	at
   [junit4]   2> 361809 INFO  (SUITE-TestConfigSetsAPIExclusivity-seed#[36DBA95D885A778C]-worker)
[    ] o.a.s.SolrTestCaseJ4 ###deleteCore

> Introduce a ConfigSet management API
> ------------------------------------
>                 Key: SOLR-7789
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Gregory Chanan
>            Assignee: Gregory Chanan
>             Fix For: Trunk, 5.4
>         Attachments: SOLR-7789.patch, SOLR-7789.patch, SOLR-7789.patch, SOLR-7789.patch,
> SOLR-5955 describes a feature to automatically create a ConfigSet, based on another one,
from a collection API call (i.e. one step collection creation).  Discussion there yielded
SOLR-7742, Immutable ConfigSet support.  To close the loop, we need support for a ConfigSet
management API.
> The simplest ConfigSet API could have one operation:
> create a new config set, based on an existing one, possible modifying the ConfigSet properties.
 Note you need to be able to modify the ConfigSet properties at creation time because otherwise
Immutable could not be changed.
> Another logical operation to support is ConfigSet deletion; that may be more complicated
to implement than creation because you need to handle the case where a collection is already
using the configuration.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message