Hmmm, that's the second time somebody's had that problem. It's
assigned to me now anyway, thanks for creating it!
Erick
On Mon, May 27, 2013 at 10:11 AM, André Widhani
wrote:
> I created SOLR-4862 ... I found no way to assign the ticket to somebody
> though (I guess it is is under "Workflow", b
I created SOLR-4862 ... I found no way to assign the ticket to somebody though
(I guess it is is under "Workflow", but the button is greyed out).
Thanks,
André
I'm beginning to hate solr.xml
That stuff should definitely be persisted, please raise a JIRA and
assign it to me.
Thanks,
Erick
On Thu, May 23, 2013 at 5:10 PM, André Widhani wrote:
> When I create a core with Core admin handler using these request parameters:
>
> action=
g, 23. Mai 2013 23:13
An: solr-user@lucene.apache.org
Betreff: AW: Core admin action "CREATE" fails for existing core
Ok - yes, will do so tomorrow.
Thanks,
André
Von: Mark Miller [markrmil...@gmail.com]
Gesendet: Donnerstag, 23. Mai 2013
Ok - yes, will do so tomorrow.
Thanks,
André
Von: Mark Miller [markrmil...@gmail.com]
Gesendet: Donnerstag, 23. Mai 2013 22:46
An: solr-user@lucene.apache.org
Betreff: Re: Core admin action "CREATE" fails for existing core
Your right - that do
When I create a core with Core admin handler using these request parameters:
action=CREATE
&name=core-tex69bbum21ctk1kq6lmkir-index3
&schema=/etc/opt/dcx/solr/conf/schema.xml
&instanceDir=/etc/opt/dcx/solr/
&config=/etc/opt/dcx/solr/conf/solrconfig.xml
&dataDir=/v
hanks for explaining and updating the wiki.
>
> When reloading the core using action=CREATE with Solr 4.1 I could specify the
> path to schema and config. In fact I used this to reconfigure the core to use
> a specific one of two prepared config files depending on some external index
Mark, Alan,
thanks for explaining and updating the wiki.
When reloading the core using action=CREATE with Solr 4.1 I could specify the
path to schema and config. In fact I used this to reconfigure the core to use a
specific one of two prepared config files depending on some external index
t;>>
>>> Sorry about the inconvenience.
>>>
>>> - Mark
>>>
>>> On May 23, 2013, at 10:45 AM, André Widhani
>>> wrote:
>>>
>>>> It seems to me that the behavior of the Core admin action "CREATE" has
orce people who might still be doing what is likely quite a
>> buggy operation to switch to the correct code.
>>
>> Sorry about the inconvenience.
>>
>> - Mark
>>
>> On May 23, 2013, at 10:45 AM, André Widhani wrote:
>>
>>> It seems to me
:45 AM, André Widhani wrote:
>
>> It seems to me that the behavior of the Core admin action "CREATE" has
>> changed when going from Solr 4.1 to 4.3.
>>
>> With 4.1, I could re-configure an existing core (changing path/name to
>> solrconfig.xml for ex
dhani wrote:
> It seems to me that the behavior of the Core admin action "CREATE" has
> changed when going from Solr 4.1 to 4.3.
>
> With 4.1, I could re-configure an existing core (changing path/name to
> solrconfig.xml for example). In 4.3, I get
It seems to me that the behavior of the Core admin action "CREATE" has changed
when going from Solr 4.1 to 4.3.
With 4.1, I could re-configure an existing core (changing path/name to
solrconfig.xml for example). In 4.3, I get an error message:
SEVERE: org.apache.solr.common.Sol
r example, some sort of request:
> http://localhost:8080/solr/admin/cores?action=CREATE&name=MajorIndex&instanceDir=cores/major&property=???
>
> Thanks!
>
>
>
dmin/cores?action=CREATE&name=MajorIndex&instanceDir=cores/major&property=???
Thanks!
Thanks for the reply, I was wondering if I wrote it such that no one was ever
going to reply.
:: Shouldn't all the parameters be added to the solr.xml core2 that were
:
:yep .. it does in fact look like a bug in the solr.xml persistence code.
:please file a bug in Jira.
Will do.
:: passed i
: Shouldn't all the parameters be added to the solr.xml core2 that were
yep .. it does in fact look like a bug in the solr.xml persistence code.
please file a bug in Jira.
: passed in from the URL? And why did the config="solrconfig.xml" get
: removed from the core1 definition?
i believe t
%3e/solrcores>. I see
the link for Admin core1 and everything is running fine. I then enter the URL:
http:///solrcores/admin/cores?action=CREATE&name=core2&instanceDir=/opt/solrcores&config=solrconfig.xml&schema=schema-core2.xml&dataDir=/data1/core2&properties=conf/
18 matches
Mail list logo