We increasingly faced with the requirement to maintain separate Elasticsearch indexes for our Couchbase documents of a certain bucket that contains roughly 240 million documents.
The current Elasticsearch Connector (4.2.2-SNAPSHOT)  does not allow Couchbase documents to be filtered before written to Elasticsearch, except the following example: 
[[elasticsearch.type]] # Index can be inferred from document ID by including a capturing group # named "index". This example matches IDs that start with one or more # characters followed by "::". It directs "user::alice" to index "user", # and "foo::bar::123" to index "foo". regex = '(?<index>.+?)::.*'
We mostly have randomized document IDs, for example, 32 character long alphabetical strings. Other document classes are stored in the document itself. For example
interestGroup and such.
It would be nice to have filters like
type="News" AND interestGroup="Group57" - not expressed exactly like this in the configuration file at , but simple AND + OR and exact matching would be great!
- Is there anything like this ever been considered?
- There is a slight chance I think that we missed something, and there is something like this, isn’t there?
- If to anywhere, I would probably place the filter right here,  and not let it to go to the
eventSink. What do you think? @david.nault