lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (JIRA) <>
Subject [jira] [Commented] (SOLR-3619) Rename 'example' dir to 'server'
Date Sat, 14 Jul 2012 23:55:34 GMT


Jan Høydahl commented on SOLR-3619:

Sure it would be nice to be GSAish. Everything with nice GUIs, point it to your content and
things just work with great relevancy. Point it on your employee LDAP and you get a super
person finder. Point it at your webshop and you sell more...

But it's all about use cases. When I worked @ FAST, we created some 5 different blueprint
templates as starting point depending on whether it was a web crawl, e-commerce, yellow-page,
intranet etc. One size does not fit all. For our Solr example we have chosen to demonstrate
a simple product search, and that is exactly what it is (even if it's a rather non-impressive
one). If newbies try to shuffle in some office docs of their own, chances are they won't have
a clue of how to get that done, but if they should happen to get them in, then they won't
show up in /browse without tweaking, facets will be wrong etc.

bq. I think that rather than trying to put the burden on the user right away (don't think
this is gonna be easy buster!)...
Getting started with our example(s) should be dead simple, also tweaking to do very similar
use cases. But we mislead our users by pretending that one size is meant to fit all. Let's
make the entry threshold really low - no argue about that - but for one or more chosen use
cases, and then point them in the right direction on how to incrementally tweak things to
become a great™ search.
> Rename 'example' dir to 'server'
> --------------------------------
>                 Key: SOLR-3619
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>             Fix For: 4.0, 5.0
>         Attachments: SOLR-3619.patch, server-name-layout.png

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message