Embedded usage

Hi.

I came across ElasticSearch some weeks ago and it looks great. My
company is now in the process of embedding a Lucene search into our
product. Now it's time to figure out how to best cluster a beast like
Lucene. ElasticSearch seems to be the best candidate.

But, anyone has any experience on embedding it? Is it possible to
integrate with different cluster messaging transports? Need to
coordinate the settings with different parts of the system.

Regards,
Sten Roger Sandvik

Hi,

Elasticsearch is very customizable and should be easily embeddable. If you
can give more details or specific requirements, I can try and help with some
examples. What do you mean by different cluster messaging transports?

cheers,
shay.banon

On Sun, May 9, 2010 at 2:49 PM, Sten Roger stenrs@gmail.com wrote:

Hi.

I came across Elasticsearch some weeks ago and it looks great. My
company is now in the process of embedding a Lucene search into our
product. Now it's time to figure out how to best cluster a beast like
Lucene. Elasticsearch seems to be the best candidate.

But, anyone has any experience on embedding it? Is it possible to
integrate with different cluster messaging transports? Need to
coordinate the settings with different parts of the system.

Regards,
Sten Roger Sandvik

Elasticsearch is very customizable and should be easily embeddable. If you
can give more details or specific requirements, I can try and help with some
examples. What do you mean by different cluster messaging transports?

Well, what I need is some way to patch into the cluster discovery
mechanism or to use the same as wee do (JGroups).

/srs

JGroups is used in elasticsearch already, though as a plugin from the next
release since it is replaced with a custom built discovery module. You can
have a look at the JGroupsDiscovery class. Do you want to share the same
channel?

cheers,
shay.banon

On Sun, May 9, 2010 at 8:15 PM, Sten Roger stenrs@gmail.com wrote:

Elasticsearch is very customizable and should be easily embeddable. If
you
can give more details or specific requirements, I can try and help with
some
examples. What do you mean by different cluster messaging transports?

Well, what I need is some way to patch into the cluster discovery
mechanism or to use the same as wee do (JGroups).

/srs

On May 9, 7:17 pm, Shay Banon shay.ba...@elasticsearch.com wrote:

JGroups is used in elasticsearch already, though as a plugin from the next
release since it is replaced with a custom built discovery module. You can
have a look at the JGroupsDiscovery class. Do you want to share the same
channel?

Cool. I will have a look at JGroupsDiscovery class. Yes, want to share
the same channel so it's easier for customers to configure the whole
application.

/srs

Sharing the same channel will require some work to filter out messages that
are not required. I will be happy to include a generic solution for this in
JgroupsDiscovery if you do change it in Elasticsearch.

cheers,
shay.banon

On Sun, May 9, 2010 at 8:25 PM, Sten Roger stenrs@gmail.com wrote:

On May 9, 7:17 pm, Shay Banon shay.ba...@elasticsearch.com wrote:

JGroups is used in elasticsearch already, though as a plugin from the
next
release since it is replaced with a custom built discovery module. You
can
have a look at the JGroupsDiscovery class. Do you want to share the same
channel?

Cool. I will have a look at JGroupsDiscovery class. Yes, want to share
the same channel so it's easier for customers to configure the whole
application.

/srs