lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-5376) Add a demo search server
Date Wed, 30 Apr 2014 14:49:15 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-5376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13985583#comment-13985583
] 

Michael McCandless commented on LUCENE-5376:
--------------------------------------------

Thanks James!

bq. If user doesn't specify a handler, or an invalid one, return a list of valid handlers,
possibly with a little param documentation instead of the current IllegalArgumentException

+1: it's really important that all errors that come back from the server are transparent/clear
as possible.  Maybe point to the live docs handler?

bq. Allow commands like "createIndex" be execute as GET and not require POST. Maybe let users
pass parameters on the URL and not always expect an incoming JSON document? And/or have a
parameter "json" for such a document?

I think this makes sense as long as the GET API is just a mirror of what you could do via
JSON?  E.g., maybe take all CGI args, turn into the corresponding JSON struct, and pretend
that JSON had arrived via POST?  Something like that ...

> Add a demo search server
> ------------------------
>
>                 Key: LUCENE-5376
>                 URL: https://issues.apache.org/jira/browse/LUCENE-5376
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>         Attachments: lucene-demo-server.tgz
>
>
> I think it'd be useful to have a "demo" search server for Lucene.
> Rather than being fully featured, like Solr, it would be minimal, just wrapping the existing
Lucene modules to show how you can make use of these features in a server setting.
> The purpose is to demonstrate how one can build a minimal search server on top of APIs
like SearchManager, SearcherLifetimeManager, etc.
> This is also useful for finding rough edges / issues in Lucene's APIs that make building
a server unnecessarily hard.
> I don't think it should have back compatibility promises (except Lucene's index back
compatibility), so it's free to improve as Lucene's APIs change.
> As a starting point, I'll post what I built for the "eating your own dog food" search
app for Lucene's & Solr's jira issues http://jirasearch.mikemccandless.com (blog: http://blog.mikemccandless.com/2013/05/eating-dog-food-with-lucene.html
). It uses Netty to expose basic indexing & searching APIs via JSON, but it's very rough
(lots nocommits).



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message