Hi Jörg,
Following our conversation, I implemented a data validation filter. I
describe my approach at this address:
http://templth.wordpress.com/2014/03/07/implementing-data-validation-in-elasticsearch/.
I'd be pleased to have your feedback and comments on this! Thanks very much!
Thierry
I think, if this must be server side, this could be done in a REST
filter plugin, not in the mappings. Matching values against patterns
do not relate to field mappings.
Still, the best method to filter out unwanted values is at client
side, either at JSON construction time in the official clients, or in
the XContentBuilder calls in Java. Reason is to avoid extra load on
the data nodes that is not related to index or search.
Jörg
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAKdsXoF6RcbsLsMewFiFgFSdHT%3Dq%2BP%2BteaHBjRSXDk8Or-JXrQ%40mail.gmail.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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/5319F19D.8070107%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
