[Hadoop][Storm] Aim of EsSpout

Hi,

I try to use the new spout added in the last version (2.1 snapshot) but I am not sure to understand the aim of this spout.

As far as I know, a storm topology runs forever but an elasticsearch request has a finite number of responses. If we use the storm spout EsSpout in a topology, this topology will continue to ask the spout for the next tuple even when there will be no more responses from elasticsearch.

So, I am wondering if this spout is useful only for one-shot topology (we push the topology with a request, all responses are processed and then we kill the topology manually) or if this spout can be used in a storm topology which runs forever ?

As I understand the code, this spout should be used for one-shot topology but maybe I miss something (and the documentation is not clear about that). I don't think we can change the request on the fly or replay it so, when all responses are processed, the spout becomes useless. Is that correct ?

Thanks,

Christophe


Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/C2A8FF33BA0AE04EBD0881F5D152F7BE9B8A922755%40FRSPX100.fr01.awl.atosorigin.net.
For more options, visit https://groups.google.com/d/optout.

Hi,

EsSpout returns the results of a query which currently it's a one time event since Elastic is a storage not a queue. So
in this regard is useful for short-lived topologies that require the query data for processing.
There are plans to extend this in the future for things like changes/changelog (give me the updates that occurred since
X) but that will take a while.

On 10/9/14 4:31 PM, Carre Christophe wrote:

Hi,

I try to use the new spout added in the last version (2.1 snapshot) but I am not sure to understand the aim of this spout.

As far as I know, a storm topology runs forever but an elasticsearch request has a finite number of responses. If we use
the storm spout EsSpout in a topology, this topology will continue to ask the spout for the next tuple even when there
will be no more responses from elasticsearch.

So, I am wondering if this spout is useful only for one-shot topology (we push the topology with a request, all
responses are processed and then we kill the topology manually) or if this spout can be used in a storm topology which
runs forever ?

As I understand the code, this spout should be used for one-shot topology but maybe I miss something (and the
documentation is not clear about that). I don't think we can change the request on the fly or replay it so, when all
responses are processed, the spout becomes useless. Is that correct ?

Thanks,

Christophe


Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut
également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la
responsabilité de Worldline ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts
soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard
et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be
privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity
cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the
sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is
virus-free and will not be liable for any damages resulting from any virus transmitted.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
elasticsearch+unsubscribe@googlegroups.com mailto:elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/C2A8FF33BA0AE04EBD0881F5D152F7BE9B8A922755%40FRSPX100.fr01.awl.atosorigin.net
https://groups.google.com/d/msgid/elasticsearch/C2A8FF33BA0AE04EBD0881F5D152F7BE9B8A922755%40FRSPX100.fr01.awl.atosorigin.net?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout.

--
Costin

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/5436AF88.3000108%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Ok. Thank you for your response.

Christophe

-----Message d'origine-----
De : elasticsearch@googlegroups.com [mailto:elasticsearch@googlegroups.com] De la part de Costin Leau
Envoyé : jeudi 9 octobre 2014 17:54
À : elasticsearch@googlegroups.com
Objet : Re: [Hadoop][Storm] Aim of EsSpout

Hi,

EsSpout returns the results of a query which currently it's a one time event since Elastic is a storage not a queue. So in this regard is useful for short-lived topologies that require the query data for processing.
There are plans to extend this in the future for things like changes/changelog (give me the updates that occurred since
X) but that will take a while.

On 10/9/14 4:31 PM, Carre Christophe wrote:

Hi,

I try to use the new spout added in the last version (2.1 snapshot) but I am not sure to understand the aim of this spout.

As far as I know, a storm topology runs forever but an elasticsearch
request has a finite number of responses. If we use the storm spout
EsSpout in a topology, this topology will continue to ask the spout for the next tuple even when there will be no more responses from elasticsearch.

So, I am wondering if this spout is useful only for one-shot topology
(we push the topology with a request, all responses are processed and
then we kill the topology manually) or if this spout can be used in a storm topology which runs forever ?

As I understand the code, this spout should be used for one-shot
topology but maybe I miss something (and the documentation is not
clear about that). I don't think we can change the request on the fly or replay it so, when all responses are processed, the spout becomes useless. Is that correct ?

Thanks,

Christophe



Ce message et les pièces jointes sont confidentiels et réservés à
l'usage exclusif de ses destinataires. Il peut également être protégé
par le secret professionnel. Si vous recevez ce message par erreur,
merci d'en avertir immédiatement l'expéditeur et de le détruire.
L'intégrité du message ne pouvant être assurée sur Internet, la
responsabilité de Worldline ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended
solely for the addressee; it may also be privileged. If you receive
this e-mail in error, please notify the sender immediately and destroy
it. As its integrity cannot be secured on the Internet, the Worldline
liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to
elasticsearch+unsubscribe@googlegroups.com mailto:elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/C2A8FF33BA0AE04EBD0881
F5D152F7BE9B8A922755%40FRSPX100.fr01.awl.atosorigin.net
https://groups.google.com/d/msgid/elasticsearch/C2A8FF33BA0AE04EBD0881F5D152F7BE9B8A922755%40FRSPX100.fr01.awl.atosorigin.net?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout.

--
Costin

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/5436AF88.3000108%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/C2A8FF33BA0AE04EBD0881F5D152F7BE9B8A9227E2%40FRSPX100.fr01.awl.atosorigin.net.
For more options, visit https://groups.google.com/d/optout.