There definitely is a need for local in-process search technology that is not REST based. .NET developers have plenty of options there: Solr, ElasticSearch, Azure Search (on MSFT cloud). The network latency, https protocol and serialization/deserialization together are never going to be faster than in-process search.
Lucene 4.x has some great improvements in search and faceting that would be great to have. I see this request come up a lot. [Image]<http://azure.microsoft.com/> Bart Czernicki Cloud Solution Architect | Azure SaaS ISV Solutions 609.519.2060 | [email protected]<mailto:[email protected]> | Why Azure?<http://www.windowsazure.com/en-us/overview/case-studies/> From: Michael D Gorsich [mailto:[email protected]] Sent: Tuesday, January 26, 2016 8:50 AM To: [email protected] Subject: Re: Next sync release Lucene.net Could it be it works so well there just isn't much broad-based need for change? Don't the newer changes to Lucene tend to cover more specialized needs, with correspondingly fewer developers willing to work on it, or needing the functions? I know for our org's needs Lucene 3.0.3 seems perfect as-is. Michael Gorsich Senior Developer, DTE Energy - ITS [cid:[email protected]]734.586.1531 (Fermi 2) [cid:[email protected]][email protected]<mailto:[email protected]> [Inactive hide details for "Michael O'Shea" ---2016.01.26 08:28:28---I managed to integrate Lucene.Net into a content post-proce]"Michael O'Shea" ---2016.01.26 08:28:28---I managed to integrate Lucene.Net into a content post-processing system on an Azure worker process. From: "Michael O'Shea" <[email protected]<mailto:[email protected]>> To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: 2016.01.26 08:28 Subject: Re: Next sync release Lucene.net ________________________________ I managed to integrate Lucene.Net into a content post-processing system on an Azure worker process. I would be sad to see Lucene.Net go but it is true that there seems to be very little uptake for the project. Weird. Michael On Tue, Jan 26, 2016 at 12:24 PM, Erik Hatcher <[email protected]<mailto:[email protected]>> wrote: > Or via HTTP? Solr! :) > > > On Jan 26, 2016, at 06:08, Allan, Brad (Bracknell) > > <[email protected]<mailto:[email protected]>> > wrote: > > > > This question sparked a thought.... > > I wonder if it's time to think about an alternate way to make Lucene > available to the .NET community - some sort of JNI wrapper? > > > > > > -----Original Message----- > > From: Nimesh Dhruve [mailto:[email protected]] > > Sent: 25 January 2016 18:17 > > To: [email protected]<mailto:[email protected]> > > Subject: Next sync release Lucene.net > > > > Hi, > > > > I am wondering if there is any active development for Lucene.net going > on to keep it sync with Java Lucene and if so when is the next release for > Lucene.net planned? > > > > Regards, > > Nimesh > > > > > > > > ________________________________ > > > > CheckFree Solutions Limited (trading as Fiserv) > > Registered Office: Eversheds House, 70 Great Bridgewater Street, > Manchester, M15 ES > > Registered in England: No. 2694333 >
