lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Gerlowski (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-8246) create_core command gives confusing messages if broken config is given, fixed, given again
Date Mon, 16 Nov 2015 20:13:10 GMT

    [ https://issues.apache.org/jira/browse/SOLR-8246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15007239#comment-15007239
] 

Jason Gerlowski commented on SOLR-8246:
---------------------------------------

Sure, {{Throwables}} doesn't add a ton.  I'll take it out.

> create_core command gives confusing messages if broken config is given, fixed, given
again
> ------------------------------------------------------------------------------------------
>
>                 Key: SOLR-8246
>                 URL: https://issues.apache.org/jira/browse/SOLR-8246
>             Project: Solr
>          Issue Type: Improvement
>          Components: scripts and tools
>    Affects Versions: 5.3.1
>            Reporter: Alexandre Rafalovitch
>            Priority: Minor
>              Labels: usability
>         Attachments: SOLR-8246.patch
>
>
> If the config used to create a core, the command complains and aborts:
> Example:
> {code}
> $ bin/solr create_core -c minicore -d ../miniconf/
> Creating new core 'minicore' using command:
> http://localhost:8983/solr/admin/cores?action=CREATE&name=minicore&instanceDir=minicore
> ERROR: Error CREATEing SolrCore 'minicore': Unable to create core [minicore] Caused by:
The element type "dynamicField" must be terminated by the matching end-tag "</dynamicField>".
> {code}
> However, after fixing the problem, trying to re-run the command gives the same error,
causing all sorts of confusion.
> What actually happened is that config has been copied to the destination directory and
then when the command is run the second time, it does not recopy fresh - and fixed - files,
but just reuses the previously copied - broken - ones. 
> The workaround is to manually delete created destination directory and rerun the command.
But it is far from obvious.
> The fix would be either undoing the copy - a delete. The minimal fix would be a log statement
that the directory was copied (which would help example logs too). And perhaps an extra message
when the create command failed that files were copied and may need to be manually deleted.



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


Mime
View raw message