# Replicated index with masked fields

**URL:** <https://discuss.elastic.co/t/replicated-index-with-masked-fields/220329>\
**Category:** Elasticsearch\
**Tags:** ccr-cross-cluster-replication\
**Created:** [February 21, 2020, 10:09am UTC](https://discuss.elastic.co/t/replicated-index-with-masked-fields/220329 "2020-02-21T10:09:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![paulcarey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/paulcarey/32/34624_2.png) [@paulcarey](https://discuss.elastic.co/u/paulcarey)\
**Post date:** [February 21, 2020, 10:09am UTC](https://discuss.elastic.co/t/replicated-index-with-masked-fields/220329/1 "2020-02-21T10:09:35Z")

</div>

Hi

I'd like to replicate an index to a remote cluster, but with the source documents modified by either masking or removing a small selection of fields.

Combining CCR with an pre-processing pipeline / ingest node looks like it would be ideal, but as far as I can see this isn't supported.

An alternative approach would be to combine an incremental reindex from remote with an ingest node, calling `_reindex` on a regular basis e.g. every 5 minutes and specifying a query that would return only the documents ingested since the last call to `_reindex`.

Does this approach seem reasonable? If so, are there any edge cases I should consider, or are there different approaches I should consider?

Many thanks

Paul

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 20, 2020, 10:14am UTC](https://discuss.elastic.co/t/replicated-index-with-masked-fields/220329/2 "2020-03-20T10:14:38Z")

</div>

Closed on March 20, 2020, 10:14am UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.