[erlang-questions] DB for Full Text Search

Kannan <>
Thu Sep 3 22:19:40 CEST 2015


Thanks for all for your valuable inputs. I am looking forward for some more
variations.

Hi Joe, I hope the story below answers all your questions. Hardware is not
a limiting factor.

We are in the process of building a global business-customer
discovery/social/engagement platform, out from the cloud. If we succeed, it
will be a big platform.

Contents of the documents will be plain text, and CRUD operations will be
performed on the contents. Size - on average, 1MB each. The whole contents
of the document must be searchable. There will be replication of static
indexes. Security is to be applied on the wires, at the ingress and on
sensitive data. Sensitive data will be kept separately, encrypted.

Regards,
Theepan










On Thu, Sep 3, 2015 at 7:05 PM, Joe Armstrong <> wrote:

> On Thu, Sep 3, 2015 at 1:21 AM, Kannan <> wrote:
> > Team,
> >
> > We are evaluating to select a database that natively supports "full text
> > search". Do you have any inputs? The following are key:
> >
> > * Erlang integration
> > * Document orientation
> > * Weights for different keys or keys at different depths (in a JSON
> > document)
> > * Performance -- In-memory should be fine.
> > * Scalability
>
>
>
> Sorry but I have to ask:
>
> How much memory have to got?
> (in-memory might be fine, but it's vague, are we talking GBytes,
> Mbytes, TeraBytes?)
> How many document/second do you want to index/search?
> How many words per document?
> How big in the corpus?
> What do you want to retrieve (name of file(s) where words occur?)
> Is the index write append only or must it be updatable
> Is the index replicated?
> Security?
> What at the input documents (text, html, pdf, ...)?
> What languages are the input documents in?
>
> Without stating your requirement it is impossible to give a good answer
> there is an incredible spectrum of answers.
>
> /Joe
>
> >
> > Thanks,
> > Theepan
> >
> > _______________________________________________
> > erlang-questions mailing list
> > 
> > http://erlang.org/mailman/listinfo/erlang-questions
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20150904/02512e98/attachment.html>


More information about the erlang-questions mailing list