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

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

bq. i removed the tika plugin (for now). is this ok? we can make it a separate 
module?

That's fine ... let's leave it for later?

bq. which json parser to keep? jackson is only used rarely, i assume this is 
the one to remove? We just have to change the indexing code now to remove those 
jars.

I had to add jackson for streaming / incremental parsing for the bulk APIs ... 
I think (not sure!) that we should just move to jackson for everything, but I 
haven't started that yet.  I'll look into it.

bq. forbidden-apis was angry about the SOPs. i tried to figure out which ones 
were intentional and which ones were not. you can see the list of files 
exempted in build.xml.

Thanks for fixing!

bq. javadocs-lint is working but angry because mostly all javadocs 
(package.html's, class docs) are missing. this seems to need some help.

I'll work on this.

bq. TestPlugins is disabled, but i think we can fix it if we build a .zip 
on-the-fly, pulling in MockPlugin.class and other files with 
.getResourceAsStream? Uwe will love this.

That sounds great!

Thanks Rob.

> 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.1.5#6160)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to