lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Woodward (JIRA)" <>
Subject [jira] [Commented] (LUCENE-8766) Add Luwak as a lucene module
Date Tue, 16 Apr 2019 09:02:00 GMT


Alan Woodward commented on LUCENE-8766:

I've spent a bit of time cleaning up the API and reducing its surface area - there's still
some work to be done to get it passing precommit, and I need to write package javadocs, but
it's close.  The important remaining questions for me are:
1) Acknowledging contributors: the original commit history is going to be lost here, including
the names of various people who have done significant work on the project.  I'm not sure if
there's a general Apache policy here that can be applied, but I was planning on adding a 'contributors'
file with everyone's name in it that is marked as valid up the point that the code is merged
to master.
2) The name: it's called luwak because of project naming conventions at Flax, but it's not
obvious what it means - perhaps something more descriptive, like 'monitor' or 'stored-queries'?

> Add Luwak as a lucene module
> ----------------------------
>                 Key: LUCENE-8766
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Alan Woodward
>            Assignee: Alan Woodward
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
> Luwak [] is a stored query engine, allowing users
to efficiently match a stream of documents against a large set of queries.  It's only dependency
is lucene, and most recent updates have just been upgrading the version of lucene against
which it can run.
> It's a generally useful piece of software, and already licensed as Apache 2.  The maintainers
would like to donate it to the ASF, and merge it in to the lucene-solr project.

This message was sent by Atlassian JIRA

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

View raw message