Lucene version for each ES release

Elastic Stack Elasticsearch
1

Hi Shay,

As I'm creating my own Spanish analyzer, I'd like to know where I can find
information about which version of Lucene ships with which version of ES.

For instance, I just built the latest master from Git to get the new
'analyzeWildcard()' functionality and I saw within your code that you make
references to Lucene 3.1, whilst I'm working with 3.0.3.

Thanks.

2

Hi,

ES is now running on top of Lucene 3.0.3 (
https://github.com/elasticsearch/elasticsearch/blob/master/modules/elasticsearch/build.gradle#L40),
you can also check release notes for each version to find out if it upgrades
Lucene library. For example ES 0.9.0 switched to Lucene 3.0.2 (
Elasticsearch Platform — Find real-time answers at scale | Elastic) and ES 0.13.1
switched to Lucene 3.0.3 (
Elasticsearch Platform — Find real-time answers at scale | Elastic)

Once Lucene 3.1 stable is released and tested with ES then I think Shay will
integrate it as soon as possible. You can now find some references to Lucene
3.1 in code comments in some parts in ES now because some Lucene analyzers
stuff was back ported from Lucene trunk to enable functionality that is not
available in Lucene 3.0.3 (but I believe references to 3.1 are more like a
hints for ES developers to keep in mind that they can drop or refactor some
classes once switching to 3.1)

Regards,
Lukas

On Fri, Mar 18, 2011 at 10:29 AM, Enrique Medina Montenegro <
e.medina.m@gmail.com> wrote:

Hi Shay,

As I'm creating my own Spanish analyzer, I'd like to know where I can find
information about which version of Lucene ships with which version of ES.

For instance, I just built the latest master from Git to get the new
'analyzeWildcard()' functionality and I saw within your code that you make
references to Lucene 3.1, whilst I'm working with 3.0.3.

Thanks.

3

Thanks a lot.

My concern was about the fact that I'm using now the very latest code from
master, so there are no available "release notes" yet, as obvious.

On Fri, Mar 18, 2011 at 11:11 AM, Lukáš Vlček lukas.vlcek@gmail.com wrote:

Hi,

ES is now running on top of Lucene 3.0.3 (
https://github.com/elasticsearch/elasticsearch/blob/master/modules/elasticsearch/build.gradle#L40),
you can also check release notes for each version to find out if it upgrades
Lucene library. For example ES 0.9.0 switched to Lucene 3.0.2 (
Elasticsearch Platform — Find real-time answers at scale | Elastic) and ES 0.13.1
switched to Lucene 3.0.3 (
Elasticsearch Platform — Find real-time answers at scale | Elastic)

Once Lucene 3.1 stable is released and tested with ES then I think Shay
will integrate it as soon as possible. You can now find some references to
Lucene 3.1 in code comments in some parts in ES now because some Lucene
analyzers stuff was back ported from Lucene trunk to enable functionality
that is not available in Lucene 3.0.3 (but I believe references to 3.1 are
more like a hints for ES developers to keep in mind that they can drop or
refactor some classes once switching to 3.1)

Regards,
Lukas

On Fri, Mar 18, 2011 at 10:29 AM, Enrique Medina Montenegro <
e.medina.m@gmail.com> wrote:

Hi Shay,

As I'm creating my own Spanish analyzer, I'd like to know where I can find
information about which version of Lucene ships with which version of ES.

For instance, I just built the latest master from Git to get the new
'analyzeWildcard()' functionality and I saw within your code that you make
references to Lucene 3.1, whilst I'm working with 3.0.3.

Thanks.

4

Hi,

there are some release notes for master here

Though not always up to date you can also check closed issues on GitHub
(switching to new Lucene 3.1 would certainly have a ticket as it will be a
significant update and code refactoring).

Note: Personally, I think that Lucene 3.1 will probably not be integrated
into 0.16.0 (current master) because it will be a big change so having an
easy option for people to switch to ES that is using previous Lucene version
will be useful. But do not take me for granted on this.

Regards,
Lukas

On Fri, Mar 18, 2011 at 1:17 PM, Enrique Medina Montenegro <
e.medina.m@gmail.com> wrote:

Thanks a lot.

My concern was about the fact that I'm using now the very latest code from
master, so there are no available "release notes" yet, as obvious.

On Fri, Mar 18, 2011 at 11:11 AM, Lukáš Vlček lukas.vlcek@gmail.comwrote:

Hi,

ES is now running on top of Lucene 3.0.3 (
https://github.com/elasticsearch/elasticsearch/blob/master/modules/elasticsearch/build.gradle#L40),
you can also check release notes for each version to find out if it upgrades
Lucene library. For example ES 0.9.0 switched to Lucene 3.0.2 (
http://www.elasticsearch.org/download/2010/07/26/0.9.0.html) and ES
0.13.1 switched to Lucene 3.0.3 (
Elasticsearch Platform — Find real-time answers at scale | Elastic)

Once Lucene 3.1 stable is released and tested with ES then I think Shay
will integrate it as soon as possible. You can now find some references to
Lucene 3.1 in code comments in some parts in ES now because some Lucene
analyzers stuff was back ported from Lucene trunk to enable functionality
that is not available in Lucene 3.0.3 (but I believe references to 3.1 are
more like a hints for ES developers to keep in mind that they can drop or
refactor some classes once switching to 3.1)

Regards,
Lukas

On Fri, Mar 18, 2011 at 10:29 AM, Enrique Medina Montenegro <
e.medina.m@gmail.com> wrote:

Hi Shay,

As I'm creating my own Spanish analyzer, I'd like to know where I can
find information about which version of Lucene ships with which version of
ES.

For instance, I just built the latest master from Git to get the new
'analyzeWildcard()' functionality and I saw within your code that you make
references to Lucene 3.1, whilst I'm working with 3.0.3.

Thanks.

5

Noted. Thanks.

On Fri, Mar 18, 2011 at 2:05 PM, Lukáš Vlček lukas.vlcek@gmail.com wrote:

Hi,

there are some release notes for master here
Elasticsearch Platform — Find real-time answers at scale | Elastic
Though not always up to date you can also check closed issues on GitHub
(switching to new Lucene 3.1 would certainly have a ticket as it will be a
significant update and code refactoring).

Note: Personally, I think that Lucene 3.1 will probably not be integrated
into 0.16.0 (current master) because it will be a big change so having an
easy option for people to switch to ES that is using previous Lucene version
will be useful. But do not take me for granted on this.

Regards,
Lukas

On Fri, Mar 18, 2011 at 1:17 PM, Enrique Medina Montenegro <
e.medina.m@gmail.com> wrote:

Thanks a lot.

My concern was about the fact that I'm using now the very latest code from
master, so there are no available "release notes" yet, as obvious.

On Fri, Mar 18, 2011 at 11:11 AM, Lukáš Vlček lukas.vlcek@gmail.comwrote:

Hi,

ES is now running on top of Lucene 3.0.3 (
https://github.com/elasticsearch/elasticsearch/blob/master/modules/elasticsearch/build.gradle#L40),
you can also check release notes for each version to find out if it upgrades
Lucene library. For example ES 0.9.0 switched to Lucene 3.0.2 (
Elasticsearch Platform — Find real-time answers at scale | Elastic) and ES
0.13.1 switched to Lucene 3.0.3 (
Elasticsearch Platform — Find real-time answers at scale | Elastic)

Once Lucene 3.1 stable is released and tested with ES then I think Shay
will integrate it as soon as possible. You can now find some references to
Lucene 3.1 in code comments in some parts in ES now because some Lucene
analyzers stuff was back ported from Lucene trunk to enable functionality
that is not available in Lucene 3.0.3 (but I believe references to 3.1 are
more like a hints for ES developers to keep in mind that they can drop or
refactor some classes once switching to 3.1)

Regards,
Lukas

On Fri, Mar 18, 2011 at 10:29 AM, Enrique Medina Montenegro <
e.medina.m@gmail.com> wrote:

Hi Shay,

As I'm creating my own Spanish analyzer, I'd like to know where I can
find information about which version of Lucene ships with which version of
ES.

For instance, I just built the latest master from Git to get the new
'analyzeWildcard()' functionality and I saw within your code that you make
references to Lucene 3.1, whilst I'm working with 3.0.3.

Thanks.