Very cool Ben, thanks for sharing! On Tue, Oct 30, 2018 at 6:14 PM Ben Slater <ben.sla...@instaclustr.com> wrote:
> For anyone who is interested, we’ve published a blog with some more > background on this and some more detail of our ongoing plans: > https://www.instaclustr.com/instaclustr-support-cassandra-lucene-index/ > > Cheers > Ben > > On Fri, 19 Oct 2018 at 09:42 kurt greaves <k...@instaclustr.com> wrote: > >> Hi all, >> >> We've had confirmation from Stratio that they are no longer maintaining >> their Lucene plugin for Apache Cassandra. We've thus decided to fork the >> plugin to continue maintaining it. At this stage we won't be making any >> additions to the plugin in the short term unless absolutely necessary, and >> as 4.0 nears we'll begin making it compatible with the new major release. >> We plan on taking the existing PR's and issues from the Stratio repository >> and getting them merged/resolved, however this likely won't happen until >> early next year. Having said that, we welcome all contributions and will >> dedicate time to reviewing bugs in the current versions if people lodge >> them and can help. >> >> I'll note that this is new ground for us, we don't have much existing >> knowledge of the plugin but are determined to learn. If anyone out there >> has established knowledge about the plugin we'd be grateful for any >> assistance! >> >> You can find our fork here: >> https://github.com/instaclustr/cassandra-lucene-index >> At the moment, the only difference is that there is a 3.11.3 branch which >> just has some minor changes to dependencies to better support 3.11.3. >> >> Cheers, >> Kurt >> > -- > > > *Ben Slater* > > *Chief Product Officer <https://www.instaclustr.com/>* > > <https://www.facebook.com/instaclustr> <https://twitter.com/instaclustr> > <https://www.linkedin.com/company/instaclustr> > > Read our latest technical blog posts here > <https://www.instaclustr.com/blog/>. > > This email has been sent on behalf of Instaclustr Pty. Limited (Australia) > and Instaclustr Inc (USA). > > This email and any attachments may contain confidential and legally > privileged information. If you are not the intended recipient, do not copy > or disclose its content, but please reply to this email immediately and > highlight the error to the sender and then immediately delete the message. > -- Jon Haddad http://www.rustyrazorblade.com twitter: rustyrazorblade
