[
https://issues.apache.org/jira/browse/SOLR-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14269832#comment-14269832
]
Timothy Potter commented on SOLR-6933:
--------------------------------------
bq. leving both of those commands alone
+1
So a couple of basic questions shake out of this. First, what does the usage
(bin/solr create -help) say? Options like -shards, -maxShardsPerNode,
-replicationFactor don't apply when creating a core. I think the help should be
explicit about cores vs. collections. Second, if the user tries to pass one of
the collection specific options (say -shards 10) when Solr is running on cloud
mode, I think the script should error out and tell the user that option is only
when running in cloud mode. So if you're with me so far, then take a step back,
now the 2-modes of Solr are still very much in the forefront of the experience
around bin/solr create, which isn't all that different from what we have now
with create_core and create_collection, except for the most basic usage of that
action, ie.
{code}
bin/solr create -n foo
{code}
So if we think there's real benefit to having a "create" alias that's smart
about the mode Solr is in, then I'll add it. But I still think the cores vs.
collections problem doesn't go away with this create action.
> bin/solr script should just have a single create action that creates a core
> or collection depending on the mode solr is running in
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-6933
> URL: https://issues.apache.org/jira/browse/SOLR-6933
> Project: Solr
> Issue Type: Improvement
> Components: scripts and tools
> Reporter: Timothy Potter
> Assignee: Timothy Potter
>
> instead of create_core and create_collection, just have create that creates a
> core or a collection based on which mode Solr is running in.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
