Best way to do it is on the client side I believe. You could probably abuse transforms to just blow up when you see something you don't like. I don't _think_ they have the ability to manipulate the operation (to make it noop) though. If they do there certainly aren't any tests to make sure that that doesn't break.
Nik On Fri, Dec 12, 2014 at 5:11 PM, Konstantin Erman <kon...@gmail.com> wrote: > > I noticed that occasionally I need to shield my ES cluster from some > documents, which are too many or too big or otherwise poison ES. > Usually I can formulate pretty easy query or criteria to detect those > documents and I'm looking for a way to block them from entering the index. > > Is there such pre-indexing filtering mechanism? May be Transforms can be > used for that purpose? > > Thank you! > Konstantin > > > -- > 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+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/1bd11432-fd57-412f-8a22-52cf5249ddf1%40googlegroups.com > <https://groups.google.com/d/msgid/elasticsearch/1bd11432-fd57-412f-8a22-52cf5249ddf1%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAPmjWd0Ag1%3Dg_ZfqXia4LWk8brkp5EQnZJHg-%2BHuGkMR8RCjbA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
