Version 0.9 Planning


(Shay Banon) #1

Hi,

Version 0.9 is almost done. Most of the features I wanted to implement
(and there are many of them :wink: ) are done, with the only feature left is to
reimplement the cloud plugin, initially only to support amazon (rackspace
will come in a later version). I am working on implementing it (funnily
enough, no amazon cloud library is good enough to do what I want, not even
amazon formal one) and once its done 0.9 will be released.

In the meantime, and because of the scope of the release, I would love
people to start using 0.9 and see if they can help flush any problems with
it. Mainly focusing on things that might broke from 0.8, but also, if
possible, testdrive the new features like facets, new Java API, reuse of
work directory (to name a few).

Thanks,
shay.banon


(Stephen-2) #2

Hey Shay,

Sorry I haven't been following the development of 0.9 until very
recently (and rereading all the old forum posts would take way too
much time), but I'm not sure where to start looking to start using the
new API. Where would be a good place to start? Do you have any
documentation written besides JavaDoc?

Thanks,

Stephen.

On Jul 14, 1:32 pm, Shay Banon shay.ba...@elasticsearch.com wrote:

Hi,

Version 0.9 is almost done. Most of the features I wanted to implement
(and there are many of them :wink: ) are done, with the only feature left is to
reimplement the cloud plugin, initially only to support amazon (rackspace
will come in a later version). I am working on implementing it (funnily
enough, no amazon cloud library is good enough to do what I want, not even
amazon formal one) and once its done 0.9 will be released.

In the meantime, and because of the scope of the release, I would love
people to start using 0.9 and see if they can help flush any problems with
it. Mainly focusing on things that might broke from 0.8, but also, if
possible, testdrive the new features like facets, new Java API, reuse of
work directory (to name a few).

Thanks,
shay.banon


(Lukáš Vlček) #3

Hi,

there is a nice summary of changes and updates in release notes on wiki:

I think this is a very good document you can start with for now.
http://wiki.github.com/elasticsearch/elasticsearch/release-notesJust note
that this document itself is still a draft and is a subject to change.

Regards,
Lukas

On Thu, Jul 15, 2010 at 2:16 PM, Stephen scstarkey@gmail.com wrote:

Hey Shay,

Sorry I haven't been following the development of 0.9 until very
recently (and rereading all the old forum posts would take way too
much time), but I'm not sure where to start looking to start using the
new API. Where would be a good place to start? Do you have any
documentation written besides JavaDoc?

Thanks,

Stephen.

On Jul 14, 1:32 pm, Shay Banon shay.ba...@elasticsearch.com wrote:

Hi,

Version 0.9 is almost done. Most of the features I wanted to implement
(and there are many of them :wink: ) are done, with the only feature left is
to
reimplement the cloud plugin, initially only to support amazon (rackspace
will come in a later version). I am working on implementing it (funnily
enough, no amazon cloud library is good enough to do what I want, not
even
amazon formal one) and once its done 0.9 will be released.

In the meantime, and because of the scope of the release, I would love
people to start using 0.9 and see if they can help flush any problems
with
it. Mainly focusing on things that might broke from 0.8, but also, if
possible, testdrive the new features like facets, new Java API, reuse of
work directory (to name a few).

Thanks,
shay.banon


(Franz Allan Valencia See) #4

If I switch from 0.8 to 0.9 (assuming same configuration), do I have to
reindex everything again?

On Thu, Jul 15, 2010 at 2:32 AM, Shay Banon shay.banon@elasticsearch.comwrote:

Hi,

Version 0.9 is almost done. Most of the features I wanted to implement
(and there are many of them :wink: ) are done, with the only feature left is to
reimplement the cloud plugin, initially only to support amazon (rackspace
will come in a later version). I am working on implementing it (funnily
enough, no amazon cloud library is good enough to do what I want, not even
amazon formal one) and once its done 0.9 will be released.

In the meantime, and because of the scope of the release, I would love
people to start using 0.9 and see if they can help flush any problems with
it. Mainly focusing on things that might broke from 0.8, but also, if
possible, testdrive the new features like facets, new Java API, reuse of
work directory (to name a few).

Thanks,
shay.banon

--
Franz Allan Valencia See | Java Software Engineer
franz.see@gmail.com
LinkedIn: http://www.linkedin.com/in/franzsee
Twitter: http://www.twitter.com/franz_see


(Shay Banon) #5

Yep.

On Fri, Jul 16, 2010 at 6:20 AM, Franz Allan Valencia See <
franz.see@gmail.com> wrote:

If I switch from 0.8 to 0.9 (assuming same configuration), do I have to
reindex everything again?

On Thu, Jul 15, 2010 at 2:32 AM, Shay Banon shay.banon@elasticsearch.comwrote:

Hi,

Version 0.9 is almost done. Most of the features I wanted to implement
(and there are many of them :wink: ) are done, with the only feature left is to
reimplement the cloud plugin, initially only to support amazon (rackspace
will come in a later version). I am working on implementing it (funnily
enough, no amazon cloud library is good enough to do what I want, not even
amazon formal one) and once its done 0.9 will be released.

In the meantime, and because of the scope of the release, I would love
people to start using 0.9 and see if they can help flush any problems with
it. Mainly focusing on things that might broke from 0.8, but also, if
possible, testdrive the new features like facets, new Java API, reuse of
work directory (to name a few).

Thanks,
shay.banon

--
Franz Allan Valencia See | Java Software Engineer
franz.see@gmail.com
LinkedIn: http://www.linkedin.com/in/franzsee
Twitter: http://www.twitter.com/franz_see


(Lukáš Vlček) #6

Hi,

is there any other reason for data reindexing then gateway refactoring:
http://github.com/elasticsearch/elasticsearch/issues/232 (and there is a
note that only manual update of metadata is needed, not complete reindexing)
or is it due to upgrading the Lucene jar to higher version? Or any other
reason? I think this should be explicitly mentioned in release notes
http://wiki.github.com/elasticsearch/elasticsearch/release-notes and if any
details are available (ticket #) then let's attach reference to it.

Regards,
Lukas

On Fri, Jul 16, 2010 at 1:16 PM, Shay Banon shay.banon@elasticsearch.comwrote:

Yep.

On Fri, Jul 16, 2010 at 6:20 AM, Franz Allan Valencia See <
franz.see@gmail.com> wrote:

If I switch from 0.8 to 0.9 (assuming same configuration), do I have to
reindex everything again?

On Thu, Jul 15, 2010 at 2:32 AM, Shay Banon <shay.banon@elasticsearch.com

wrote:

Hi,

Version 0.9 is almost done. Most of the features I wanted to implement
(and there are many of them :wink: ) are done, with the only feature left is to
reimplement the cloud plugin, initially only to support amazon (rackspace
will come in a later version). I am working on implementing it (funnily
enough, no amazon cloud library is good enough to do what I want, not even
amazon formal one) and once its done 0.9 will be released.

In the meantime, and because of the scope of the release, I would love
people to start using 0.9 and see if they can help flush any problems with
it. Mainly focusing on things that might broke from 0.8, but also, if
possible, testdrive the new features like facets, new Java API, reuse of
work directory (to name a few).

Thanks,
shay.banon

--
Franz Allan Valencia See | Java Software Engineer
franz.see@gmail.com
LinkedIn: http://www.linkedin.com/in/franzsee
Twitter: http://www.twitter.com/franz_see


(Shay Banon) #7

I mentioned the reasons on several posts I made to the mailing list. The
reason behind it is the "reuse work directory when recovering from gateway"
feature.

-shay.banon

On Fri, Jul 16, 2010 at 2:30 PM, Lukáš Vlček lukas.vlcek@gmail.com wrote:

Hi,

is there any other reason for data reindexing then gateway refactoring:
http://github.com/elasticsearch/elasticsearch/issues/232 (and there is a
note that only manual update of metadata is needed, not complete reindexing)
or is it due to upgrading the Lucene jar to higher version? Or any other
reason? I think this should be explicitly mentioned in release notes
http://wiki.github.com/elasticsearch/elasticsearch/release-notes and if
any details are available (ticket #) then let's attach reference to it.

Regards,
Lukas

On Fri, Jul 16, 2010 at 1:16 PM, Shay Banon shay.banon@elasticsearch.comwrote:

Yep.

On Fri, Jul 16, 2010 at 6:20 AM, Franz Allan Valencia See <
franz.see@gmail.com> wrote:

If I switch from 0.8 to 0.9 (assuming same configuration), do I have to
reindex everything again?

On Thu, Jul 15, 2010 at 2:32 AM, Shay Banon <
shay.banon@elasticsearch.com> wrote:

Hi,

Version 0.9 is almost done. Most of the features I wanted to
implement (and there are many of them :wink: ) are done, with the only feature
left is to reimplement the cloud plugin, initially only to support amazon
(rackspace will come in a later version). I am working on implementing it
(funnily enough, no amazon cloud library is good enough to do what I want,
not even amazon formal one) and once its done 0.9 will be released.

In the meantime, and because of the scope of the release, I would
love people to start using 0.9 and see if they can help flush any problems
with it. Mainly focusing on things that might broke from 0.8, but also, if
possible, testdrive the new features like facets, new Java API, reuse of
work directory (to name a few).

Thanks,
shay.banon

--
Franz Allan Valencia See | Java Software Engineer
franz.see@gmail.com
LinkedIn: http://www.linkedin.com/in/franzsee
Twitter: http://www.twitter.com/franz_see


(Lukáš Vlček) #8

So when switching from 0.8 to 0.9 then one must "convert" metadata via
manual update (described in the issue 232) but data in index must be
comletely reindexed.
Lukas

On Fri, Jul 16, 2010 at 1:32 PM, Shay Banon shay.banon@elasticsearch.comwrote:

I mentioned the reasons on several posts I made to the mailing list. The
reason behind it is the "reuse work directory when recovering from gateway"
feature.

-shay.banon

On Fri, Jul 16, 2010 at 2:30 PM, Lukáš Vlček lukas.vlcek@gmail.comwrote:

Hi,

is there any other reason for data reindexing then gateway refactoring:
http://github.com/elasticsearch/elasticsearch/issues/232 (and there is a
note that only manual update of metadata is needed, not complete reindexing)
or is it due to upgrading the Lucene jar to higher version? Or any other
reason? I think this should be explicitly mentioned in release notes
http://wiki.github.com/elasticsearch/elasticsearch/release-notes and if
any details are available (ticket #) then let's attach reference to it.

Regards,
Lukas

On Fri, Jul 16, 2010 at 1:16 PM, Shay Banon <shay.banon@elasticsearch.com

wrote:

Yep.

On Fri, Jul 16, 2010 at 6:20 AM, Franz Allan Valencia See <
franz.see@gmail.com> wrote:

If I switch from 0.8 to 0.9 (assuming same configuration), do I have to
reindex everything again?

On Thu, Jul 15, 2010 at 2:32 AM, Shay Banon <
shay.banon@elasticsearch.com> wrote:

Hi,

Version 0.9 is almost done. Most of the features I wanted to
implement (and there are many of them :wink: ) are done, with the only feature
left is to reimplement the cloud plugin, initially only to support amazon
(rackspace will come in a later version). I am working on implementing it
(funnily enough, no amazon cloud library is good enough to do what I want,
not even amazon formal one) and once its done 0.9 will be released.

In the meantime, and because of the scope of the release, I would
love people to start using 0.9 and see if they can help flush any problems
with it. Mainly focusing on things that might broke from 0.8, but also, if
possible, testdrive the new features like facets, new Java API, reuse of
work directory (to name a few).

Thanks,
shay.banon

--
Franz Allan Valencia See | Java Software Engineer
franz.see@gmail.com
LinkedIn: http://www.linkedin.com/in/franzsee
Twitter: http://www.twitter.com/franz_see


(Shay Banon) #9

If you reindex, then you probably create the indices already, so no need to
bother with the cluster metadata.

On Fri, Jul 16, 2010 at 2:39 PM, Lukáš Vlček lukas.vlcek@gmail.com wrote:

So when switching from 0.8 to 0.9 then one must "convert" metadata via
manual update (described in the issue 232) but data in index must be
comletely reindexed.
Lukas

On Fri, Jul 16, 2010 at 1:32 PM, Shay Banon shay.banon@elasticsearch.comwrote:

I mentioned the reasons on several posts I made to the mailing list. The
reason behind it is the "reuse work directory when recovering from gateway"
feature.

-shay.banon

On Fri, Jul 16, 2010 at 2:30 PM, Lukáš Vlček lukas.vlcek@gmail.comwrote:

Hi,

is there any other reason for data reindexing then gateway refactoring:
http://github.com/elasticsearch/elasticsearch/issues/232 (and there is a
note that only manual update of metadata is needed, not complete reindexing)
or is it due to upgrading the Lucene jar to higher version? Or any other
reason? I think this should be explicitly mentioned in release notes
http://wiki.github.com/elasticsearch/elasticsearch/release-notes and if
any details are available (ticket #) then let's attach reference to it.

Regards,
Lukas

On Fri, Jul 16, 2010 at 1:16 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:

Yep.

On Fri, Jul 16, 2010 at 6:20 AM, Franz Allan Valencia See <
franz.see@gmail.com> wrote:

If I switch from 0.8 to 0.9 (assuming same configuration), do I have to
reindex everything again?

On Thu, Jul 15, 2010 at 2:32 AM, Shay Banon <
shay.banon@elasticsearch.com> wrote:

Hi,

Version 0.9 is almost done. Most of the features I wanted to
implement (and there are many of them :wink: ) are done, with the only feature
left is to reimplement the cloud plugin, initially only to support amazon
(rackspace will come in a later version). I am working on implementing it
(funnily enough, no amazon cloud library is good enough to do what I want,
not even amazon formal one) and once its done 0.9 will be released.

In the meantime, and because of the scope of the release, I would
love people to start using 0.9 and see if they can help flush any problems
with it. Mainly focusing on things that might broke from 0.8, but also, if
possible, testdrive the new features like facets, new Java API, reuse of
work directory (to name a few).

Thanks,
shay.banon

--
Franz Allan Valencia See | Java Software Engineer
franz.see@gmail.com
LinkedIn: http://www.linkedin.com/in/franzsee
Twitter: http://www.twitter.com/franz_see


(Lukáš Vlček) #10

Ah... good point. I added note to release notes (so that I do not have to
ask again the next time :slight_smile:

On Fri, Jul 16, 2010 at 8:05 PM, Shay Banon shay.banon@elasticsearch.comwrote:

If you reindex, then you probably create the indices already, so no need to
bother with the cluster metadata.

On Fri, Jul 16, 2010 at 2:39 PM, Lukáš Vlček lukas.vlcek@gmail.comwrote:

So when switching from 0.8 to 0.9 then one must "convert" metadata via
manual update (described in the issue 232) but data in index must be
comletely reindexed.
Lukas

On Fri, Jul 16, 2010 at 1:32 PM, Shay Banon <shay.banon@elasticsearch.com

wrote:

I mentioned the reasons on several posts I made to the mailing list. The
reason behind it is the "reuse work directory when recovering from gateway"
feature.

-shay.banon

On Fri, Jul 16, 2010 at 2:30 PM, Lukáš Vlček lukas.vlcek@gmail.comwrote:

Hi,

is there any other reason for data reindexing then gateway refactoring:
http://github.com/elasticsearch/elasticsearch/issues/232 (and there is
a note that only manual update of metadata is needed, not complete
reindexing) or is it due to upgrading the Lucene jar to higher version? Or
any other reason? I think this should be explicitly mentioned in release
notes http://wiki.github.com/elasticsearch/elasticsearch/release-notes and
if any details are available (ticket #) then let's attach reference to it.

Regards,
Lukas

On Fri, Jul 16, 2010 at 1:16 PM, Shay Banon <
shay.banon@elasticsearch.com> wrote:

Yep.

On Fri, Jul 16, 2010 at 6:20 AM, Franz Allan Valencia See <
franz.see@gmail.com> wrote:

If I switch from 0.8 to 0.9 (assuming same configuration), do I have
to reindex everything again?

On Thu, Jul 15, 2010 at 2:32 AM, Shay Banon <
shay.banon@elasticsearch.com> wrote:

Hi,

Version 0.9 is almost done. Most of the features I wanted to
implement (and there are many of them :wink: ) are done, with the only feature
left is to reimplement the cloud plugin, initially only to support amazon
(rackspace will come in a later version). I am working on implementing it
(funnily enough, no amazon cloud library is good enough to do what I want,
not even amazon formal one) and once its done 0.9 will be released.

In the meantime, and because of the scope of the release, I would
love people to start using 0.9 and see if they can help flush any problems
with it. Mainly focusing on things that might broke from 0.8, but also, if
possible, testdrive the new features like facets, new Java API, reuse of
work directory (to name a few).

Thanks,
shay.banon

--
Franz Allan Valencia See | Java Software Engineer
franz.see@gmail.com
LinkedIn: http://www.linkedin.com/in/franzsee
Twitter: http://www.twitter.com/franz_see


(Jack Key) #11

Hello, Shay.

The new "facet" features of 9.0 (terms especially) are turning out to be incredibly useful.
I have been working from snapshots of 9.0, but I was wondering how close you are to a 9.0 release.

Regards, Jack


(Shay Banon) #12

Having a bit of a snag with the cloud plugin. Due to all the other features
in elasticsearch, I might release 0.9 and with a special notice that the
cloud plugin is in alpha stage, and I will address it for 0.9.1. Hopefully
0.9 will be released in a few days.

-shay.banon

On Tue, Jul 20, 2010 at 9:49 PM, Jack Key joeandrewkey@gmail.com wrote:

Hello, Shay.

The new "facet" features of 9.0 (terms especially) are turning out to be
incredibly useful.
I have been working from snapshots of 9.0, but I was wondering how close
you
are to a 9.0 release.

Regards, Jack

--
View this message in context:
http://elasticsearch-users.115913.n3.nabble.com/Version-0-9-Planning-tp967339p982204.html
Sent from the ElasticSearch Users mailing list archive at Nabble.com.


(system) #13