From Fedora Project Wiki
m
Line 153: Line 153:
 
<!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
 
<!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
 
* https://bugzilla.redhat.com/show_bug.cgi?id=902086 and  specfiles linked from here
 
* https://bugzilla.redhat.com/show_bug.cgi?id=902086 and  specfiles linked from here
* usptream pages http://www.elasticsearch.com/products/elasticsearch  
+
* upstream pages http://www.elasticsearch.com/products/elasticsearch  
* usptream git  https://github.com/elasticsearch/elasticsearch/
+
* upstream git  https://github.com/elasticsearch/elasticsearch/
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
  

Revision as of 11:40, 22 November 2014


Elasticsearch

Summary

Goal of this change is to pack Elasticsearch into main fedora repo.

Owner

  • Name: Jiri Vanek
  • Email: jvanek@rehat.com
    • #fedora-java
    • #fedora-devel
  • Release notes owner:

Current status

Detailed Description

The Elasticsearch is fully-featured self-standing opensource indexing server. Many people and many tools do use it. And many people do wont 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 then current upstream install and download.

Benefit to Fedora

Users of fedora will be able yum install elasticsearch, will be able to use it as dependence and use it in current project without fighting with monolithic upstream installation.

Scope

  • Proposal owners:
    • pack Elasticsearch - nearly done - see RHBZ#902086
    • make it somehow works
    • verify it works
    • tune list of crucial depnedences
    • enable Elasticsearch as service - something what have to be decided
  • Other developers:
    • This is crucial part of this proposal
    • Elastic search is extremely tuned application, and like it, its dependences must be strictly kept in correct versions
    • Currently known troublemakers:
      • lucene
      • netty3
      • sigar
      • compress-lzf
      • guava (currently needed 18, avaiable 17)
  • Release engineering:
    • Nothing I'm aware about.
  • Policies and guidelines:
    • Nothing I'm aware about.
    • maybe... fedora is going by way - keep as updated as possible, if it breaks something, that something have to be fixed. This is not best for ES. Maybe ES can et some helping exception?

Upgrade/compatibility impact

  • when Elasticsearch is updated, all its dependencies must be aligned to exact versions it needs
  • Non of its dependencies can be updated, unless Elasticsearch is known to work on it
  • The list of such restricted despondencies must evolve - see currently known "troublemakers" section


How To Test

  • yum install elasticsearch
    • start it/use its service
  • send json request, accept reply

User Experience

Users are able to use packed Elasticsearch after custom run on some port, or as sevice on known port.

Dependencies

No known project is aiming to be packed with Elasticsource as dependence in close future, but the grow of packages requesting it can be expected. Currently known third party users who will welcome this packed are NSA (yes, that NSA) and Searchisko (Search and content delivery platform behind jboss.org web site).

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?)
    • Although I'm initiator of this, I hope from help from other people around bug 902086 and people around Searchisko.
    • Considering the status of the build, the only expected failure is in despondences - that we will not be able to agree on versions
    • Another failure may raise when some capital dependence change owener and he will not be aware about Elasticsearch boundaries
  • Contingency deadline: Ugh... You tell me...
  • Blocks release? no
  • Blocks product? no

Documentation


Release Notes