F22 System Wide Change: Elasticsearch
zbyszek at in.waw.pl
Wed Dec 17 17:55:40 UTC 2014
> ----- Original Message -----
> > From: "Josh Boyer" <jwboyer at fedoraproject.org>
> > To: "Development discussions related to Fedora" <devel at lists.fedoraproject.org>
> > Sent: Wednesday, December 17, 2014 4:25:35 PM
> > Subject: Re: F22 System Wide Change: Elasticsearch
> > On Wed, Dec 17, 2014 at 9:03 AM, Jaroslav Reznik <jreznik at redhat.com> wrote:
> > > = Proposed System Wide Change: Elasticsearch =
> > > https://fedoraproject.org/wiki/Changes/Elasticsearch
> > >
> > > Change owner(s): Jiri Vanek <jvanek at rehat.com>
> > >
> > > Goal of this change is to pack Elasticsearch into main Fedora repo.
> > >
> > > == Detailed Description ==
> > > The Elasticsearch  is fully-featured self-standing opensource 
> > > indexing
> > > server. Many people and many tools do use it. And many people do want it in
> > > Fedora. Aim of this Change is to make elastic search available by simple
> > > yum
> > > install elasticsearch, and of course enable it as dependence. To build a
> > > custom indexing tool on top of elastic search is more easy than current
> > > upstream install and download.
> > >
> > > * Other developers:
> > > ** '''This is crucial part of this proposal'''
> > > ** Elastic search is extremely tuned application, and like it, its
> > > dependencies must be strictly kept in correct versions
> > > ** Currently known troublemakers:
> > > *** lucene
> > > *** netty3
> > > *** sigar
> > > *** compress-lzf
> > > *** guava (currently needed 18, avaiable 17)
> > So from what I can tell, the dependency issues are the only thing that
> > is preventing this from being a self-contained Change. Is that
> > correct?
Actually only guava 18 and sigar java binding are missing, iiuc .
The first requires somebody to create the update, the second
one already has a patch so should not be a problem. Especially if anything
else requires a version bump, please file bugs on specific packages,
so it's easier to see what is going on.
> > If so, perhaps pursuing a bundling exception would be a more
> > straightforward approach.
On Wed, Dec 17, 2014 at 09:39:50AM -0500, Aleksandar Kurtakov top-posted:
> Not a bundling but creating a compat packages for older version
where needed. Nothing stops people from creating them now.
We should strive to simply update all dependencies and packages using
them to the latest version. Only when this fails we should start discussing
> > > == Scope ==
> > > * Proposal owners:
> > > ** pack Elasticsearch - nearly done - see RHBZ#902086
> > > ** make it somehow works
> > > ** verify it works
> > > ** tune list of crucial dependencies
> > > ** enable Elasticsearch as service - something what have to be decided
So there really are two parts to this Change. The first is packaging
of elasticsearch and its dependencies. This part seems to be going well.
The second is enabling elasticsearch by default and making use of it in other
packages. This part of the proposal needs some fleshing-out: I don't see
why it should be enabled by default, unless it is used by other things
which are on by default, and cannot express the dependency otherwise.
What would it be used by and for? Please expand on that.
More information about the devel