Version 0.9 is almost done. Most of the features I wanted to implement
(and there are many of them ) 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).
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?
Version 0.9 is almost done. Most of the features I wanted to implement
(and there are many of them ) 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).
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?
Version 0.9 is almost done. Most of the features I wanted to implement
(and there are many of them ) 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).
Version 0.9 is almost done. Most of the features I wanted to implement
(and there are many of them ) 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).
Version 0.9 is almost done. Most of the features I wanted to implement
(and there are many of them ) 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).
Version 0.9 is almost done. Most of the features I wanted to implement
(and there are many of them ) 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).
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.
Version 0.9 is almost done. Most of the features I wanted to
implement (and there are many of them ) 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).
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
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.
Version 0.9 is almost done. Most of the features I wanted to
implement (and there are many of them ) 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).
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
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.
Version 0.9 is almost done. Most of the features I wanted to
implement (and there are many of them ) 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).
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
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.
Version 0.9 is almost done. Most of the features I wanted to
implement (and there are many of them ) 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).
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.
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.
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.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.
) are done, with the only feature left is to
) are done, with the only feature left is to