Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of dionne@dionne-associates.com
 designates 69.89.20.235 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default;
 d=dionne-associates.com;
	h=Received:Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-Identified-User;
	b=YL72u6HsO/3FU/lgJtM4GkBLO8rrGBuMmCWKNtixPeeAFEec0eusik2HqzzJhKNIhaWri8ppt1HQXSIa54eJmlxKsYNbd5MK3IBrwaXa8DlHhxp6U3pIB7pAkGc2RQLV;
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1077)
Subject: Re: FTI engine by Joe
From: Robert Dionne <dionne@dionne-associates.com>
In-Reply-To: <45d8e23d0912091628tae62038sbae79d5ce34b2f15@mail.gmail.com>
Date: Thu, 10 Dec 2009 05:33:27 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <5B6D8B3C-14ED-45AE-B918-272DE14FF798@dionne-associates.com>
References: <45d8e23d0912091628tae62038sbae79d5ce34b2f15@mail.gmail.com>
To: user@couchdb.apache.org

I think so, and have already done some integration work [1] using an =
earlier version of some of this from the Erlang book. There are still =
lots of design questions such as what to index and how to specify what =
to index, how to store indices and how to interact with the view =
servers, etc..

There is also already very solid FTI support for couchdb using =
Lucene[2]. Lucene is very mature and proven and widely used so this fits =
many uses cases.

There are a lot of other goodies in this elib1, It's definitely worth a =
read for erlang programmers.

Cheers,

Bob


[1] http://github.com/bdionne/indexer=20
[2] http://github.com/rnewson/couchdb-lucene/


On Dec 9, 2009, at 7:28 PM, Senthilkumar Peelikkampatti wrote:

> I looked at the Joe's mail about suite of libraries and one of them is
> FTI. Will this fit in couchdb's full text requirement?
>=20
> ---------- Forwarded message ----------
> From: Joe Armstrong <erlang@gmail.com>
> Date: Wed, Dec 9, 2009 at 2:12 PM
> Subject: [erlang-questions] Announce: elib1
> To: Erlang <erlang-questions@erlang.org>
> Cc: zabrane3@gmail.com, dionne@dionne-associates.com
>=20
>=20
> Announcing elib1
>=20
> Elib1 was released today.
>=20
> Tomorrow I will present it at the Stockholm Erlounge.
>=20
> Elib1 is a library of Erlang modules and set of applications which use
> the modules.
>=20
> The Elib1 project now moves into phase 2
>=20
> The phases of the project are:
>=20
>    Phase 1: Define and implement a basic structure
>             and a small number of applications
>    Phase 2: Make project open source
>    Phase 3: Write books
>=20
> Each phase will take about 2-3 years.
>=20
> The first attempt at a library contains modules for the following:
>=20
>    xml parsing
>    fast tuple I/O (to disk)
>    full-text indexing
>    http parsing
>    telnet server
>    json parsing
>    porter stemming
>    mysql native interface
>    sha1
>    similar file locator
>    screen manipulation
>    miscellaneous missing functions (which should be in the standard =
libraries)
>    accurate tagging of Erlang so it can be turned into browsable HTML
>    (and more ...)
>=20
> The applications are divided it two areas. Supported and unsupported
>=20
> In supported:
>=20
>    indexer      - a full text indexing engine (this is the of near
> production quality)
>    irc          - and irc kit (includes a TCL wish interface)
> (somewhat incomplete)
>    tagger       - an application to turn erlang into browsable HTML
>    drivers      - example linked in and port drivers (currently =
broken)
>    midi_drivers - mac os X only
>    website      - a webserver (used internally)
>    versions     - a way of munging module names to make them secure
>=20
> In unsupported:
>=20
>   epeg     - a peg grammar and parser combinators
>   folding  - Javascript folding editor/organiser (needs some work,
> not erlang :-)
>   jpeg     - image transformation in Erlang
>   xml      - some xml stuff
>=20
> I have attempted to use "best practise" in making the library. Using
> the dialyzer, eunit and edoc.
>=20
> This code is far from perfect or polished - but the basic way things
> fit together
> is defined.
>=20
> Rather than have 500 small libraries each with a few users and a few
> routines I'd
> like to see one library with a much large number of tightly integrated =
routines.
>=20
> The code is available at:
>=20
> http://github.com/joearms/elib1
>=20
> /Joe Armstrong
>=20
> ________________________________________________________________
> erlang-questions mailing list. See http://www.erlang.org/faq.html
> erlang-questions (at) erlang.org
>=20
>=20
>=20
>=20
> --=20
> Regards,
> Senthilkumar Peelikkampatti,
> http://pmsenthilkumar.blogspot.com/