otisg
(Otis Gospodnetić)
June 22, 2013, 12:52am
1
Hi,
What is the right place to hook into ES aggregator node and:
intercept and look at the response
do some other work (e.g. look up some external data, run another query,
etc.)
and then modify the original response before returning it to the caller
?
Thanks,
Otis
Search Analytics - http://sematext.com/search-analytics/index.html
Performance Monitoring - http://sematext.com/spm/index.html
--
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 .
For more options, visit https://groups.google.com/groups/opt_out .
otisg
(Otis Gospodnetić)
June 28, 2013, 4:01pm
2
Hi,
Jörg wrote about a custom rest action on
http://jprante.github.io/lessons/2012/03/27/Writing-a-simple-plugin-for-Elasticsearch.html
, but is there really nothing else that can be done to plug some custom
logic/code that acts on data in the response and adds something to it?
Thanks,
Otis
Search Analytics - Cloud Monitoring Tools & Services | Sematext
Performance Monitoring - Sematext Monitoring | Infrastructure Monitoring Service
On Friday, June 21, 2013 8:52:36 PM UTC-4, Otis Gospodnetic wrote:
Hi,
What is the right place to hook into ES aggregator node and:
intercept and look at the response
do some other work (e.g. look up some external data, run another query,
etc.)
and then modify the original response before returning it to the caller
?
Thanks,
Otis
Search Analytics - Cloud Monitoring Tools & Services | Sematext
Performance Monitoring - Sematext Monitoring | Infrastructure Monitoring Service
--
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 .
For more options, visit https://groups.google.com/groups/opt_out .
Ivan
(Ivan Brusic)
June 28, 2013, 5:03pm
3
From what I can tell, new query types (request/response) are pluggable, but
nothing like Solr's request handlers. Still hoping for a facet refactor and
that said refactor leads to some overall query side refactor.
--
Ivan
On Fri, Jun 28, 2013 at 9:01 AM, Otis Gospodnetic <
otis.gospodnetic@gmail.com > wrote:
Hi,
Jörg wrote about a custom rest action on
http://jprante.github.io/lessons/2012/03/27/Writing-a-simple-plugin-for-Elasticsearch.html , but is there really nothing else that can be done to plug some custom
logic/code that acts on data in the response and adds something to it?
Thanks,
Otis
Search Analytics - http://sematext.com/search-**analytics/index.html http://sematext.com/search-analytics/index.html
Performance Monitoring - Sematext Monitoring | Infrastructure Monitoring Service http://sematext.com/spm/index.html
On Friday, June 21, 2013 8:52:36 PM UTC-4, Otis Gospodnetic wrote:
Hi,
What is the right place to hook into ES aggregator node and:
intercept and look at the response
do some other work (e.g. look up some external data, run another query,
etc.)
and then modify the original response before returning it to the caller
?
Thanks,
Otis
Search Analytics - http://sematext.com/search-**analytics/index.html http://sematext.com/search-analytics/index.html
Performance Monitoring - Sematext Monitoring | Infrastructure Monitoring Service http://sematext.com/spm/index.html
--
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 .
For more options, visit https://groups.google.com/groups/opt_out .
--
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 .
For more options, visit https://groups.google.com/groups/opt_out .