[ https://issues.apache.org/jira/browse/SOLR-16800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748203#comment-17748203 ]
Houston Putman commented on SOLR-16800: --------------------------------------- To be clear, my excitement was over the whole "/solr" part being required in the url. I think that should go away in both SolrJ and the SolrCLI. Using bin/solr for remote collections has really never made sense to me. If I'm remote, why wouldn't I use the API or the Admin UI? But I'm not going to speak for all Solr users, this is just my experience. > Allow create and delete to use -url instead of -c and work with remote solr. > ---------------------------------------------------------------------------- > > Key: SOLR-16800 > URL: https://issues.apache.org/jira/browse/SOLR-16800 > Project: Solr > Issue Type: Sub-task > Components: cli > Affects Versions: main (10.0), 9.3 > Reporter: Eric Pugh > Priority: Minor > Time Spent: 40m > Remaining Estimate: 0h > > We have a mix of commands that take a -url and others that take a -c > parameter. > Only work locally (and that makes sense to me): > start, stop, restart, status, version, auth > assert (though maybe?) > package > Only work locally (and that DOESN'T make sense to me): > create, create_core, create_collection, delete > Works with remote Solr: > healthcheck - requires a -c and a werid -z parameter! > zk > config, though it has -c, -p and -solrUrl.. Which seems like we could > simplify to -solrUrl? > export > api -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org