[
https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14088106#comment-14088106
]
Timothy Potter commented on SOLR-3619:
--------------------------------------
+1 on the named configsets approach (working on that now)
bq. I'm not sure I'm sold on that as the default ... without a sensible
production default as well.
I guess I was optimizing for a quick and easy getting started experience. Solr
doesn't have a getting to production problem, it's the getting started path
that's way too complicated, esp. for a new user population that knows they need
search and just wants to kick the tires on Solr for a few minutes / hours.
There's something very powerful about being able to: 1) start solr, 2) send in
a few JSON docs, 3) query for your data.
Of course we all know that adding some data and firing off a few queries is a
long way from production, but if we lose the user in the first 5 minutes,
getting to production is no longer relevant. So I think we need a low-barrier
to entry configset for this user population and if we want to have another more
structured configset, that's great too.
> 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
> Assignee: Timothy Potter
> Fix For: 4.9, 5.0
>
> Attachments: SOLR-3619.patch, SOLR-3619.patch, server-name-layout.png
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
