lucene-pylucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andi Vajda <>
Subject Re: PyLucene use JCC shared object by default
Date Tue, 17 Apr 2012 23:39:24 GMT

  Hi Caleb,

On Tue, 17 Apr 2012, Caleb Burns wrote:

> I've finished the process at my organization of re-implementing SOLR's
> faceting algorithm (in C++).
> We would like the public at large to have access to the work we've done and
> plan to do. In order for this to be a real possibility the code needs to be
> built against and use the same JVM as the PyLucene installation does. The
> most logical way we feel to have this accomplished is by having PyLucenes'
> default installation use JCC as a Shared Object.
> We have yet more plans to extend and provide utilities that work with
> PyLucene, but this all hinges on having the shared object. The only
> alternative methodology would require the bundling of our source with the
> PyLucene project itself as a fork.
> We are eager to start open sourcing our work, so please let us know what
> would be the best way to integrate our work.

Ok, so what is your question ?
PyLucene's shared mode also depends on JCC's shared library.
Is your question about what the default should be ?


> -- 
> Caleb Burns
> Developer | Riders Discount
> 866.931.6644 x851 | <>
> [image: image.png] <> [image:
> image.png] <!/ridersdiscount>
> Deal of the Day <!/rd_dealoftheday>

View raw message