# Lucene 4.0 **URL:** \ **Category:** Elasticsearch\ **Created:** [October 11, 2012, 3:18pm UTC](https://discuss.elastic.co/t/lucene-4-0/9319 "2012-10-11T15:18:45Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [October 11, 2012, 3:18pm UTC](https://discuss.elastic.co/t/lucene-4-0/9319/1 "2012-10-11T15:18:45Z")
Heya fellows, ``` Lucene 4.0 is out the door, wanted to update you all about how we plan to upgrade to it on elasticsearch. The plan is to first release 0.20 version still using Lucene 3.6.x, this should happen in the next week or so. The reason is that we want to get 0.20 features at the hand of users as fast as possible, without waiting for the upgrade to 4.0. We will also start the process of upgrading the 4.0, which will be in the next major elasticsearch version. This will include upgrading to 4.0, and making use of the new features and exposing them to the users. This shouldn't take too long, though we do want to see 4.0.0 GA Lucene "out in the wild" a bit before releasing a formal release (0.21) of elasticsearch with it. ``` -shay.banon -- ---
**Author:** ![mattweber](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mattweber/32/44940_2.png) [@mattweber](https://discuss.elastic.co/u/mattweber)\ **Post date:** [October 11, 2012, 3:40pm UTC](https://discuss.elastic.co/t/lucene-4-0/9319/2 "2012-10-11T15:40:14Z")
Awesome, I can't wait! On Thu, Oct 11, 2012 at 8:18 AM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > Heya fellows, > > ``` > Lucene 4.0 is out the door, wanted to update you all about how we plan > > ``` > > to upgrade to it on elasticsearch. The plan is to first release 0.20 > version still using Lucene 3.6.x, this should happen in the next week or > so. The reason is that we want to get 0.20 features at the hand of users as > fast as possible, without waiting for the upgrade to 4.0. > > ``` > We will also start the process of upgrading the 4.0, which will be in > > ``` > > the next major elasticsearch version. This will include upgrading to 4.0, > and making use of the new features and exposing them to the users. This > shouldn't take too long, though we do want to see 4.0.0 GA Lucene "out in > the wild" a bit before releasing a formal release (0.21) of elasticsearch > with it. > > -shay.banon > > -- -- ---
**Author:** ![Eugene\_Strokin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eugene_strokin/32/1238_2.png) [@Eugene\_Strokin](https://discuss.elastic.co/u/Eugene_Strokin)\ **Post date:** [October 11, 2012, 6:20pm UTC](https://discuss.elastic.co/t/lucene-4-0/9319/3 "2012-10-11T18:20:35Z")
Shay, thanks for update. Just wander about back compatibility. If switching from 0.19 to 0.20 will it require reindexing, or we could just update the libs? And from 20 to 21, I guess it will require reindexing, but want to hear confirmation from you. Thank you On Thursday, October 11, 2012 11:18:46 AM UTC-4, kimchy wrote: > Heya fellows, > > ``` > Lucene 4.0 is out the door, wanted to update you all about how we plan > > ``` > > to upgrade to it on elasticsearch. The plan is to first release 0.20 > version still using Lucene 3.6.x, this should happen in the next week or > so. The reason is that we want to get 0.20 features at the hand of users as > fast as possible, without waiting for the upgrade to 4.0. > > ``` > We will also start the process of upgrading the 4.0, which will be in > > ``` > > the next major elasticsearch version. This will include upgrading to 4.0, > and making use of the new features and exposing them to the users. This > shouldn't take too long, though we do want to see 4.0.0 GA Lucene "out in > the wild" a bit before releasing a formal release (0.21) of elasticsearch > with it. > > -shay.banon -- ---
**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [October 11, 2012, 8:40pm UTC](https://discuss.elastic.co/t/lucene-4-0/9319/4 "2012-10-11T20:40:40Z")
Lucene is always backwards compatible within one version, so Lucene 4.0 code should be able to read a 3.x index. Writing indexes with a newer version and reading them in an older one is more problematic. That said, a new ES version is more than just a Lucene upgrade, so it might require a reindex. ES version incompatibility is always due to the internal communication API changing. -- Ivan On Thu, Oct 11, 2012 at 11:20 AM, Eugene Strokin [eugene@strokin.info](mailto:eugene@strokin.info)wrote: > Shay, thanks for update. > Just wander about back compatibility. > If switching from 0.19 to 0.20 will it require reindexing, or we could > just update the libs? > And from 20 to 21, I guess it will require reindexing, but want to hear > confirmation from you. > > Thank you > > On Thursday, October 11, 2012 11:18:46 AM UTC-4, kimchy wrote: > > > Heya fellows, > > > > ``` > > Lucene 4.0 is out the door, wanted to update you all about how we > > > > ``` > > > > plan to upgrade to it on elasticsearch. The plan is to first release 0.20 > > version still using Lucene 3.6.x, this should happen in the next week or > > so. The reason is that we want to get 0.20 features at the hand of users as > > fast as possible, without waiting for the upgrade to 4.0. > > > > ``` > > We will also start the process of upgrading the 4.0, which will be in > > > > ``` > > > > the next major elasticsearch version. This will include upgrading to 4.0, > > and making use of the new features and exposing them to the users. This > > shouldn't take too long, though we do want to see 4.0.0 GA Lucene "out in > > the wild" a bit before releasing a formal release (0.21) of elasticsearch > > with it. > > > > -shay.banon > > -- -- ---
**Author:** ![phill](https://avatars.discourse-cdn.com/v4/letter/p/779978/32.png) [@phill](https://discuss.elastic.co/u/phill)\ **Post date:** [October 11, 2012, 9:27pm UTC](https://discuss.elastic.co/t/lucene-4-0/9319/5 "2012-10-11T21:27:39Z")
On 10/11/2012 1:40 PM, Ivan Brusic wrote: > Lucene is always backwards compatible within one version, so Lucene > 4.0 code should be able to read a 3.x index. Writing indexes with a > newer version and reading them in an older one is more problematic. > That said, a new ES version is more than just a Lucene upgrade, so it > might require a reindex. Here is the statement from the release notes [http://lucene.apache.org/core/4\_0\_0-BETA/changes/Changes.html#4.0.0-alpha.changes\_in\_backwards\_compatibility\_policy](http://lucene.apache.org/core/4_0_0-BETA/changes/Changes.html#4.0.0-alpha.changes_in_backwards_compatibility_policy) "On upgrading to 4.0, if you do not fully reindex your documents, Lucene will emulate the new flex API on top of the old index, incurring some performance cost (up to ~10% slowdown, typically). To prevent this slowdown, use oal.index.IndexUpgrader to upgrade your indexes to latest file format (LUCENE-3082 [http://issues.apache.org/jira/browse/LUCENE-3082](http://issues.apache.org/jira/browse/LUCENE-3082))." Thus, as an app developer we don't have to do the work, we can trigger an upgrade of each Lucene index when we can using a conversion tool. [http://lucene.apache.org/core/4\_0\_0-BETA/core/org/apache/lucene/index/IndexUpgrader.html](http://lucene.apache.org/core/4_0_0-BETA/core/org/apache/lucene/index/IndexUpgrader.html) I'm sure this feature will be useful in ES. -Paul -- ---
**Author:** ![Eugene\_Strokin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eugene_strokin/32/1238_2.png) [@Eugene\_Strokin](https://discuss.elastic.co/u/Eugene_Strokin)\ **Post date:** [October 11, 2012, 11:56pm UTC](https://discuss.elastic.co/t/lucene-4-0/9319/6 "2012-10-11T23:56:06Z")
Thank you for the replies, It would be very nice feature if ES automatically or by some command would upgrade the index to v.4. Will be waiting for the new versions of ES. Thanks again. On Thursday, October 11, 2012 5:27:17 PM UTC-4, P Hill wrote: > On 10/11/2012 1:40 PM, Ivan Brusic wrote: > > > Lucene is always backwards compatible within one version, so Lucene > > 4.0 code should be able to read a 3.x index. Writing indexes with a > > newer version and reading them in an older one is more problematic. > > That said, a new ES version is more than just a Lucene upgrade, so it > > might require a reindex. > > Here is the statement from the release notes > > [Lucene Change Log](http://lucene.apache.org/core/4_0_0-BETA/changes/Changes.html#4.0.0-alpha.changes_in_backwards_compatibility_policy) > > "On upgrading to 4.0, if you do not fully reindex your documents, Lucene > will emulate the new flex API on top of the old index, incurring some > performance cost (up to ~10% slowdown, typically). To prevent this > slowdown, use oal.index.IndexUpgrader to upgrade your indexes to latest > file format (LUCENE-3082 > [http://issues.apache.org/jira/browse/LUCENE-3082](http://issues.apache.org/jira/browse/LUCENE-3082))." > > Thus, as an app developer we don't have to do the work, we can trigger > an upgrade of each Lucene index when we can using a conversion tool. > > [IndexUpgrader (Lucene 4.0.0 API)](http://lucene.apache.org/core/4_0_0-BETA/core/org/apache/lucene/index/IndexUpgrader.html) > > I'm sure this feature will be useful in ES. > > -Paul -- ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [October 12, 2012, 1:16am UTC](https://discuss.elastic.co/t/lucene-4-0/9319/7 "2012-10-12T01:16:42Z")
Heya, few points: Indexes in elasticsearch has been "backward" compatible, and when upgrading to Lucene 4.0, it will be backward compatible as well (both on the Lucene level, and on the ES level). You might need to do an "upgrade" to make use of newer versions, or to make sure there is no "emulation" layer on Lucene level. So, upgrading to 0.20 and 0.21 will be compatible index wise (no need to reindex), but you will need to do a full cluster restart (though we are working on eventually not needing that as well, first infrastructure for that is already going to be in upcoming 0.20). On Oct 11, 2012, at 4:56 PM, Eugene Strokin [eugene@strokin.info](mailto:eugene@strokin.info) wrote: > Thank you for the replies, It would be very nice feature if ES automatically or by some command would upgrade the index to v.4. > Will be waiting for the new versions of ES. > Thanks again. > > On Thursday, October 11, 2012 5:27:17 PM UTC-4, P Hill wrote: > On 10/11/2012 1:40 PM, Ivan Brusic wrote: > > > Lucene is always backwards compatible within one version, so Lucene > > 4.0 code should be able to read a 3.x index. Writing indexes with a > > newer version and reading them in an older one is more problematic. > > That said, a new ES version is more than just a Lucene upgrade, so it > > might require a reindex. > > Here is the statement from the release notes > > [Lucene Change Log](http://lucene.apache.org/core/4_0_0-BETA/changes/Changes.html#4.0.0-alpha.changes_in_backwards_compatibility_policy) > > "On upgrading to 4.0, if you do not fully reindex your documents, Lucene > will emulate the new flex API on top of the old index, incurring some > performance cost (up to ~10% slowdown, typically). To prevent this > slowdown, use oal.index.IndexUpgrader to upgrade your indexes to latest > file format (LUCENE-3082 > [http://issues.apache.org/jira/browse/LUCENE-3082](http://issues.apache.org/jira/browse/LUCENE-3082))." > > Thus, as an app developer we don't have to do the work, we can trigger > an upgrade of each Lucene index when we can using a conversion tool. > > [IndexUpgrader (Lucene 4.0.0 API)](http://lucene.apache.org/core/4_0_0-BETA/core/org/apache/lucene/index/IndexUpgrader.html) > > I'm sure this feature will be useful in ES. > > -Paul > > -- -- ---
**Author:** ![simonw\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simonw_2/32/1130_2.png) [@simonw\_2](https://discuss.elastic.co/u/simonw_2)\ **Post date:** [October 12, 2012, 8:26am UTC](https://discuss.elastic.co/t/lucene-4-0/9319/8 "2012-10-12T08:26:33Z")
On Thursday, October 11, 2012 10:40:53 PM UTC+2, Ivan Brusic wrote: > Lucene is always backwards compatible within one version, so Lucene 4.0 > code should be able to read a 3.x index. Writing indexes with a newer > version and reading them in an older one is more problematic. That said, a > new ES version is more than just a Lucene upgrade, so it might require a > reindex. this question has been asked a couple of times so let me elaborate on this a little for those who are interested what the main differences are between 4.0 and 3.x on the index level. It is correct in general that lucene 4.0 can read 3.0 indexes but this comes with a cost this time. in lucene 4.0 we changed the sort order from UTF-16 to UTF-8 on the lowest level so 3.x indices are sorted "differently". To make this still work with the 4.0 API we added a "re-mapping" layer for surrogate characters to maintain the correct sort order. This will have some cost in performance but it should not be dramatic. Yet, it is still a good idea to upgrade the index. The good news is lucene can by-itself do that in the background. If you merge a 3.x segment with 4.0 it will be merged into a 4.0 segment so you can "upgrade-over-time". Anyhow, in practice ES users should be need this knowledge and we will provide flexible ways to upgrade to an ES version that runs lucene 4.0. simon > ES version incompatibility is always due to the internal communication API > changing. > > -- > Ivan > > On Thu, Oct 11, 2012 at 11:20 AM, Eugene Strokin \ > > > wrote: > > > Shay, thanks for update. > > Just wander about back compatibility. > > If switching from 0.19 to 0.20 will it require reindexing, or we could > > just update the libs? > > And from 20 to 21, I guess it will require reindexing, but want to hear > > confirmation from you. > > > > Thank you > > > > On Thursday, October 11, 2012 11:18:46 AM UTC-4, kimchy wrote: > > > > > Heya fellows, > > > > > > ``` > > > Lucene 4.0 is out the door, wanted to update you all about how we > > > > > > ``` > > > > > > plan to upgrade to it on elasticsearch. The plan is to first release 0.20 > > > version still using Lucene 3.6.x, this should happen in the next week or > > > so. The reason is that we want to get 0.20 features at the hand of users as > > > fast as possible, without waiting for the upgrade to 4.0. > > > > > > ``` > > > We will also start the process of upgrading the 4.0, which will be > > > > > > ``` > > > > > > in the next major elasticsearch version. This will include upgrading to > > > 4.0, and making use of the new features and exposing them to the users. > > > This shouldn't take too long, though we do want to see 4.0.0 GA Lucene "out > > > in the wild" a bit before releasing a formal release (0.21) of > > > elasticsearch with it. > > > > > > -shay.banon > > > > -- -- ---
**Author:** ![Tanguy1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tanguy1/32/1749_2.png) [@Tanguy1](https://discuss.elastic.co/u/Tanguy1)\ **Post date:** [October 12, 2012, 9:05am UTC](https://discuss.elastic.co/t/lucene-4-0/9319/9 "2012-10-12T09:05:48Z")
Thank you Shay & Simon for giving us those details. Customers are already wondering when Lucene 4 will be available in ES. -- Tanguy @tlrx Le vendredi 12 octobre 2012 10:26:33 UTC+2, simonw a écrit : > On Thursday, October 11, 2012 10:40:53 PM UTC+2, Ivan Brusic wrote: > > > Lucene is always backwards compatible within one version, so Lucene 4.0 > > code should be able to read a 3.x index. Writing indexes with a newer > > version and reading them in an older one is more problematic. That said, a > > new ES version is more than just a Lucene upgrade, so it might require a > > reindex. > > this question has been asked a couple of times so let me elaborate on this > a little for those who are interested what the main differences are between > 4.0 and 3.x on the index level. It is correct in general that lucene 4.0 > can read 3.0 indexes but this comes with a cost this time. in lucene 4.0 we > changed the sort order from UTF-16 to UTF-8 on the lowest level so 3.x > indices are sorted "differently". To make this still work with the 4.0 API > we added a "re-mapping" layer for surrogate characters to maintain the > correct sort order. This will have some cost in performance but it should > not be dramatic. Yet, it is still a good idea to upgrade the index. The > good news is lucene can by-itself do that in the background. If you merge a > 3.x segment with 4.0 it will be merged into a 4.0 segment so you can > "upgrade-over-time". Anyhow, in practice ES users should be need this > knowledge and we will provide flexible ways to upgrade to an ES version > that runs lucene 4.0. > > simon > > > ES version incompatibility is always due to the internal communication > > API changing. > > > > -- > > Ivan > > > > On Thu, Oct 11, 2012 at 11:20 AM, Eugene Strokin [eug...@strokin.info](mailto:eug...@strokin.info)wrote: > > > > > Shay, thanks for update. > > > Just wander about back compatibility. > > > If switching from 0.19 to 0.20 will it require reindexing, or we could > > > just update the libs? > > > And from 20 to 21, I guess it will require reindexing, but want to hear > > > confirmation from you. > > > > > > Thank you > > > > > > On Thursday, October 11, 2012 11:18:46 AM UTC-4, kimchy wrote: > > > > > > > Heya fellows, > > > > > > > > ``` > > > > Lucene 4.0 is out the door, wanted to update you all about how we > > > > > > > > ``` > > > > > > > > plan to upgrade to it on elasticsearch. The plan is to first release 0.20 > > > > version still using Lucene 3.6.x, this should happen in the next week or > > > > so. The reason is that we want to get 0.20 features at the hand of users as > > > > fast as possible, without waiting for the upgrade to 4.0. > > > > > > > > ``` > > > > We will also start the process of upgrading the 4.0, which will be > > > > > > > > ``` > > > > > > > > in the next major elasticsearch version. This will include upgrading to > > > > 4.0, and making use of the new features and exposing them to the users. > > > > This shouldn't take too long, though we do want to see 4.0.0 GA Lucene "out > > > > in the wild" a bit before releasing a formal release (0.21) of > > > > elasticsearch with it. > > > > > > > > -shay.banon > > > > > > -- -- ---
**Author:** ![Clinton\_Gormley](https://avatars.discourse-cdn.com/v4/letter/c/50afbb/32.png) [@Clinton\_Gormley](https://discuss.elastic.co/u/Clinton_Gormley)\ **Post date:** [October 12, 2012, 9:25am UTC](https://discuss.elastic.co/t/lucene-4-0/9319/10 "2012-10-12T09:25:59Z")
> So, upgrading to 0.20 and 0.21 will be compatible index wise (no need > to reindex), but you will need to do a full cluster restart (though we > are working on eventually not needing that as well, first > infrastructure for that is already going to be in upcoming 0.20). This is excellent news! > -- ---
**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [October 12, 2012, 2:47pm UTC](https://discuss.elastic.co/t/lucene-4-0/9319/11 "2012-10-12T14:47:35Z")
Lucene 4.0 was officially released today. > **[Lucene™ Core News](https://lucene.apache.org/core/corenews.html)** > > Apache Lucene is a high-performance, full-featured search engine library written entirely in Java. It is a technology suitable for... On Thu, Oct 11, 2012 at 8:40 AM, Matt Weber [matt.weber@gmail.com](mailto:matt.weber@gmail.com) wrote: > Awesome, I can't wait! > > On Thu, Oct 11, 2012 at 8:18 AM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > > > Heya fellows, > > > > ``` > > Lucene 4.0 is out the door, wanted to update you all about how we > > > > ``` > > > > plan to upgrade to it on elasticsearch. The plan is to first release 0.20 > > version still using Lucene 3.6.x, this should happen in the next week or > > so. The reason is that we want to get 0.20 features at the hand of users as > > fast as possible, without waiting for the upgrade to 4.0. > > > > ``` > > We will also start the process of upgrading the 4.0, which will be in > > > > ``` > > > > the next major elasticsearch version. This will include upgrading to 4.0, > > and making use of the new features and exposing them to the users. This > > shouldn't take too long, though we do want to see 4.0.0 GA Lucene "out in > > the wild" a bit before releasing a formal release (0.21) of elasticsearch > > with it. > > > > -shay.banon > > > > -- > > -- -- ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [October 12, 2012, 3:54pm UTC](https://discuss.elastic.co/t/lucene-4-0/9319/12 "2012-10-12T15:54:29Z")
Hi Shay, Lucene 4 just got released 🙂 I would love to get some pointers what kind of help of the community is most welcome? For example, with Lucene 4.0, will there be an elasticsearch-index-spellcheck module? How about introducing modules for codecs? How will support for Lucene payloads look like in ES? Just to mention a few exciting things... Best regards, Jörg On Thursday, October 11, 2012 5:18:46 PM UTC+2, kimchy wrote: > Heya fellows, > > ``` > Lucene 4.0 is out the door, wanted to update you all about how we plan > > ``` > > to upgrade to it on elasticsearch. The plan is to first release 0.20 > version still using Lucene 3.6.x, this should happen in the next week or > so. The reason is that we want to get 0.20 features at the hand of users as > fast as possible, without waiting for the upgrade to 4.0. > > ``` > We will also start the process of upgrading the 4.0, which will be in > > ``` > > the next major elasticsearch version. This will include upgrading to 4.0, > and making use of the new features and exposing them to the users. This > shouldn't take too long, though we do want to see 4.0.0 GA Lucene "out in > the wild" a bit before releasing a formal release (0.21) of elasticsearch > with it. > > -shay.banon -- ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [October 12, 2012, 3:57pm UTC](https://discuss.elastic.co/t/lucene-4-0/9319/13 "2012-10-12T15:57:58Z")
The plan is the first get Lucene 4.0 integrated with elasticsearch, and then expose all the new features. We will take it feature by feature, but to your points, there will be a spellcheck builtin using the new "direct" spellcheck feature, you will be able to configure codecs in the mapping, and write a plugin that introduces new codes, and so on... On Oct 12, 2012, at 8:54 AM, Jörg Prante [joergprante@gmail.com](mailto:joergprante@gmail.com) wrote: > Hi Shay, > > Lucene 4 just got released 🙂 > > I would love to get some pointers what kind of help of the community is most welcome? > > For example, with Lucene 4.0, will there be an elasticsearch-index-spellcheck module? How about introducing modules for codecs? How will support for Lucene payloads look like in ES? Just to mention a few exciting things... > > Best regards, > > Jörg > > On Thursday, October 11, 2012 5:18:46 PM UTC+2, kimchy wrote: > Heya fellows, > > ``` > Lucene 4.0 is out the door, wanted to update you all about how we plan to upgrade to it on elasticsearch. The plan is to first release 0.20 version still using Lucene 3.6.x, this should happen in the next week or so. The reason is that we want to get 0.20 features at the hand of users as fast as possible, without waiting for the upgrade to 4.0. > > We will also start the process of upgrading the 4.0, which will be in the next major elasticsearch version. This will include upgrading to 4.0, and making use of the new features and exposing them to the users. This shouldn't take too long, though we do want to see 4.0.0 GA Lucene "out in the wild" a bit before releasing a formal release (0.21) of elasticsearch with it. > > ``` > > -shay.banon > > -- -- ---
**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [October 12, 2012, 4:17pm UTC](https://discuss.elastic.co/t/lucene-4-0/9319/14 "2012-10-12T16:17:28Z")
Lucid Imagination has an annotated version of the “Release Highlights” for Lucene/Solr 4.0 [http://searchhub.org/dev/2012/10/12/apache-solr-and-lucene-4-0-0-released/](http://searchhub.org/dev/2012/10/12/apache-solr-and-lucene-4-0-0-released/) Andrzej Białecki, Robert Muir, and Grant Ingersoll will be presenting a paper on the Lucene 4 architecture: [http://opensearchlab.otago.ac.nz/paper\_10.pdf](http://opensearchlab.otago.ac.nz/paper_10.pdf) Good reading if you like to understand the guts. -- Ivan On Fri, Oct 12, 2012 at 8:54 AM, Jörg Prante [joergprante@gmail.com](mailto:joergprante@gmail.com) wrote: > Hi Shay, > > Lucene 4 just got released 🙂 > > I would love to get some pointers what kind of help of the community is > most welcome? > > For example, with Lucene 4.0, will there be an > elasticsearch-index-spellcheck module? How about introducing modules for > codecs? How will support for Lucene payloads look like in ES? Just to > mention a few exciting things... > > Best regards, > > Jörg > > On Thursday, October 11, 2012 5:18:46 PM UTC+2, kimchy wrote: > > > Heya fellows, > > > > ``` > > Lucene 4.0 is out the door, wanted to update you all about how we > > > > ``` > > > > plan to upgrade to it on elasticsearch. The plan is to first release 0.20 > > version still using Lucene 3.6.x, this should happen in the next week or > > so. The reason is that we want to get 0.20 features at the hand of users as > > fast as possible, without waiting for the upgrade to 4.0. > > > > ``` > > We will also start the process of upgrading the 4.0, which will be in > > > > ``` > > > > the next major elasticsearch version. This will include upgrading to 4.0, > > and making use of the new features and exposing them to the users. This > > shouldn't take too long, though we do want to see 4.0.0 GA Lucene "out in > > the wild" a bit before releasing a formal release (0.21) of elasticsearch > > with it. > > > > -shay.banon > > -- -- ---
**Author:** ![banderon1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/banderon1/32/2689_2.png) [@banderon1](https://discuss.elastic.co/u/banderon1)\ **Post date:** [October 12, 2012, 9:54pm UTC](https://discuss.elastic.co/t/lucene-4-0/9319/15 "2012-10-12T21:54:56Z")
Shout out on techcrunch! > **[Open Source Search Engine Apache Lucene/Solr Gets Big Update | TechCrunch](https://techcrunch.com/2012/10/12/open-source-search-engine-apache-lucenesolr-gets-big-update/)** > > Today the Apache Foundation released a major update to the open source search engine building tools Lucene and Solr. Version 4.0 adds several new features aimed at making Solr easier to use, more scalable and more customizable. On Thursday, October 11, 2012 8:18:46 AM UTC-7, kimchy wrote: > Heya fellows, > > ``` > Lucene 4.0 is out the door, wanted to update you all about how we plan > > ``` > > to upgrade to it on elasticsearch. The plan is to first release 0.20 > version still using Lucene 3.6.x, this should happen in the next week or > so. The reason is that we want to get 0.20 features at the hand of users as > fast as possible, without waiting for the upgrade to 4.0. > > ``` > We will also start the process of upgrading the 4.0, which will be in > > ``` > > the next major elasticsearch version. This will include upgrading to 4.0, > and making use of the new features and exposing them to the users. This > shouldn't take too long, though we do want to see 4.0.0 GA Lucene "out in > the wild" a bit before releasing a formal release (0.21) of elasticsearch > with it. > > -shay.banon -- ---
**Author:** ![Nicolas\_Blanc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nicolas_blanc/32/2030_2.png) [@Nicolas\_Blanc](https://discuss.elastic.co/u/Nicolas_Blanc)\ **Post date:** [October 17, 2012, 7:28pm UTC](https://discuss.elastic.co/t/lucene-4-0/9319/16 "2012-10-17T19:28:50Z")
Can i expect to see the grouping feature in 0.20 ? Today i worked with a 0.19.4 version of ES, with Martijn code for grouping and some custom patchs to use more facet types than just terms string. And i really want to stop maintaining custom version of ES 🙂 Or need i to wait for the next 0.21 based on new Lucene 4.0 ? Thx in advance, -- Nicolas BLANC. -- ---
**Author:** ![Aaron\_Rosenthal](https://avatars.discourse-cdn.com/v4/letter/a/9e8a1a/32.png) [@Aaron\_Rosenthal](https://discuss.elastic.co/u/Aaron_Rosenthal)\ **Post date:** [October 23, 2012, 7:22pm UTC](https://discuss.elastic.co/t/lucene-4-0/9319/17 "2012-10-23T19:22:09Z")
We would like to plan for .21 whats a realistic time table, thx. great work! -- ---
**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [October 23, 2012, 7:48pm UTC](https://discuss.elastic.co/t/lucene-4-0/9319/18 "2012-10-23T19:48:33Z")
Still waiting for .20 to be released! 🙂 On Tue, Oct 23, 2012 at 12:22 PM, Aaron Rosenthal [dealertouch@gmail.com](mailto:dealertouch@gmail.com)wrote: > We would like to plan for .21 whats a realistic time table, thx. great > work! > > -- -- ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [October 23, 2012, 11:08pm UTC](https://discuss.elastic.co/t/lucene-4-0/9319/19 "2012-10-23T23:08:20Z")
0.20.0.RC1 was already released, working on the blog post now. On Oct 23, 2012, at 9:48 PM, Ivan Brusic [ivan@brusic.com](mailto:ivan@brusic.com) wrote: > Still waiting for .20 to be released! 🙂 > > On Tue, Oct 23, 2012 at 12:22 PM, Aaron Rosenthal [dealertouch@gmail.com](mailto:dealertouch@gmail.com) wrote: > We would like to plan for .21 whats a realistic time table, thx. great work! > > -- > > -- -- ---
**Author:** ![Robin\_Verlangen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/robin_verlangen/32/1542_2.png) [@Robin\_Verlangen](https://discuss.elastic.co/u/Robin_Verlangen)\ **Post date:** [October 24, 2012, 8:05am UTC](https://discuss.elastic.co/t/lucene-4-0/9319/20 "2012-10-24T08:05:27Z")
I'm really looking forward to this. Good job for you guys, keep moving forward! Best regards, Robin Verlangen _Software engineer_ \* \* W [http://www.robinverlangen.nl](http://www.robinverlangen.nl) E robin@us2.nl [http://goo.gl/Lt7BC](http://goo.gl/Lt7BC) Disclaimer: The information contained in this message and attachments is intended solely for the attention and use of the named addressee and may be confidential. If you are not the intended recipient, you are reminded that the information remains the property of the sender. You must not use, disclose, distribute, copy, print or rely on this e-mail. If you have received this message in error, please contact the sender immediately and irrevocably delete this message and any copies. 2012/10/24 [kimchy@gmail.com](mailto:kimchy@gmail.com) > 0.20.0.RC1 was already released, working on the blog post now. > > On Oct 23, 2012, at 9:48 PM, Ivan Brusic [ivan@brusic.com](mailto:ivan@brusic.com) wrote: > > Still waiting for .20 to be released! 🙂 > > On Tue, Oct 23, 2012 at 12:22 PM, Aaron Rosenthal [dealertouch@gmail.com](mailto:dealertouch@gmail.com)wrote: > > > We would like to plan for .21 whats a realistic time table, thx. great > > work! > > > > -- > > -- > > -- -- [Next page](https://discuss.elastic.co/t/lucene-4-0/9319.md?page=2)