[
https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14067791#comment-14067791
]
Alexandre Rafalovitch commented on SOLR-3619:
---------------------------------------------
Rereading the comment. Did you mean the following sequence of steps?
1) Download
2) Unzip
3) Start server
4) Visit Admin UI
5) Create new collection (using one of provided configsets, which is basically
renamed examples)
6) Index?
That could work. And a good differentiation from ES, as we ship AdminUI in the
box (theirs is separate and is free for development only).
We'd need UI support for configsets (and I don't actually know how extensive
they are), but that's probably a good idea anyway. On the other hand, asking
users to create a directory in a right location, copy schema and solrconfig
files there (from where?) and then do AdminUI (or command line) call to create
collection - is NOT going to work.
> Rename 'example' dir to 'server' and pull examples into an 'examples'
> directory
> -------------------------------------------------------------------------------
>
> Key: SOLR-3619
> URL: https://issues.apache.org/jira/browse/SOLR-3619
> Project: Solr
> Issue Type: Improvement
> Reporter: Mark Miller
> Fix For: 4.9, 5.0
>
> Attachments: SOLR-3619.patch, server-name-layout.png
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
