Mailing-List: contact dev-help@metamodel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@metamodel.apache.org
Received-SPF: pass (nike.apache.org: domain of ardlema@gmail.com designates
 209.85.220.178 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CA+U3tt-buZJ0ge6VJyiSqQquLMAX_KEns8hf7kqjeUMuz9yahA@mail.gmail.com>
References: 
 <CA+U3tt-buZJ0ge6VJyiSqQquLMAX_KEns8hf7kqjeUMuz9yahA@mail.gmail.com>
Date: Fri, 13 Feb 2015 12:48:41 +0100
Message-ID: 
 <CAMjNSoybdZvpXrqYRVyjLK0i4egV0SCPJSpbNyGbCPPynAkDrA@mail.gmail.com>
Subject: Re: ElasticSearch connection via REST protocol
From: Alberto Rodriguez <ardlema@gmail.com>
To: "dev@metamodel.apache.org" <dev@metamodel.apache.org>
Content-Type: multipart/alternative; boundary=20cf3071c7da61df6c050ef6d121

--20cf3071c7da61df6c050ef6d121
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Kasper,

There is an open source project that might match our needs. Have a look:
Jest <https://github.com/searchbox-io/Jest>

If you think that we can integrate it in MM I would be more than happy to
help you out.

Kind regards,

2015-02-11 8:44 GMT+01:00 Kasper S=C3=B8rensen <i.am.kasper.sorensen@gmail.=
com>:

> Hi all,
>
> I have a scenario where a potential customer of ours has a hosted
> ElasticSearch setup. This setup only allows connectivity through ES's RES=
T
> protocol and that means we currently cannot connect to it with MetaModel =
(I
> think) ... I think we only support the TransportClient and NodeClient
> protocols. Did anyone of you try to connect via REST protocol anyhow? Any
> clue of the effort needed if we wanted to bring REST support to MetaModel=
's
> elasticsearch module?
>
> Kasper
>

--20cf3071c7da61df6c050ef6d121--