[
https://issues.apache.org/jira/browse/SOLR-17495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18123805#comment-18123805
]
ASF subversion and git services commented on SOLR-17495:
--------------------------------------------------------
Commit 79e23dc0dc1b8e7643cf6d4798b829a7ebbf0fb4 in solr's branch
refs/heads/jira/SOLR-17697-picocli from Jan Høydahl
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=79e23dc0dc1 ]
SOLR-17697 Align delete command docs with the SOLR-18321 behaviour
Correct the stale "--delete-config ... default is true" wording: SOLR-17495
made config deletion opt-in but never updated the description. Keep the
now-no-op --force documented, so existing scripts find out it has no effect.
Regenerate the CLI ref-guide page.
> Change CLI DeleteTool deleting of configs to opt in instead of default
> behavior
> -------------------------------------------------------------------------------
>
> Key: SOLR-17495
> URL: https://issues.apache.org/jira/browse/SOLR-17495
> Project: Solr
> Issue Type: Sub-task
> Components: cli
> Affects Versions: 10.0
> Reporter: Eric Pugh
> Assignee: Eric Pugh
> Priority: Major
> Labels: pull-request-available
> Fix For: 10.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> In discussion on SOLR-17488 we identified that the --delete-config option,
> which by default is true, is an odd user experience. You need to do a
> --delete-config false to not delete a config.
>
> However, i think deleting a collection and deleting a config are two seperate
> conceptual things in reality.
>
> So in 10, lets make --delete-config something you opt into otherwise configs
> are NOT deleted.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
