No we will not use RPC. We need this to enrich the data. Also we want to
block write operations for a certain time. This interception mechanism will
be useful for this purpose too. I understood the cost of deserializing.
Maybe we need to think again for enrichment. But it will be a very good
improvement for other needs.
On Wed, Mar 16, 2011 at 9:39 PM, Shay Banon shay.banon@elasticsearch.comwrote:
This is certainly possible, though at a cost. Th proper place to do that
is actually on the primary shard using some sort of callback (so you know it
only happens once).The cost associated is the fact that the document source will need to be
parsed and represented in memory, then allow to callback to munge it, and
then serialized again. This is because the way elasticsearch parses the
document is using pull parsing.Open an issue for that. Also, what kind of changes are you going to do?
Will you need to RPC call other systems to do it?-shay.banon
On Wednesday, March 16, 2011 at 9:57 AM, Mustafa Sener wrote:
Hi,
Is it possible to intercept transport client actions? Basically we want to
intercept action such as index to make some modifications on data before
inserted. There will be many client around ES and we don't want to take care
of this in every client. This will be beneficial for some other reasons too.--
Mustafa Sener
www.ifountain.com
--
Mustafa Sener
www.ifountain.com