Hi guys,
While working with a custom native scorer, we identified the need to run
code upon search completion. We would basically have a life cycle where we
can detect (read: run code) on search start and search end in order to
initialize and finalize/dispose some internal data structures.
Looking at the docs, I cannot seem to find anything indicating such
features have been implemented. We are using AbstractLongSearchScript at
the moment, but are open for change if you guys can point us in another
direction allowing for more of a life cycle-ish approach within a plugin.
The javadocs are slightly bare when it comes to ExecutableScript and its
relatives.
Thanks for your time.
--
Any luck on this? if you have a solution post it please.
On Tuesday, January 22, 2013 2:49:20 PM UTC+4, Didde Brockman wrote:
Hi guys,
While working with a custom native scorer, we identified the need to run
code upon search completion. We would basically have a life cycle where we
can detect (read: run code) on search start and search end in order to
initialize and finalize/dispose some internal data structures.
Looking at the docs, I cannot seem to find anything indicating such
features have been implemented. We are using AbstractLongSearchScript at
the moment, but are open for change if you guys can point us in another
direction allowing for more of a life cycle-ish approach within a plugin.
The javadocs are slightly bare when it comes to ExecutableScript and its
relatives.
Thanks for your time.
--
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.