Handling of gigantic unsearchable fields


I was wondering what good methods for handling gigantic fields are?

Let's say a document has an array field for unique visitors of a post, so it will save the ip or the username in this array.
If the post now gets 10 000 views, the field has to have 10 000 entries into this one field inside 1 document.
Preferably, this field should only be accessed when trying to increase the views. When checking if the user has already seen the post or not. Other than that, it shouldn't be searchable, and shouldn't be returned during a normal query.

I was thinking maybe to use the nested type, and include_in_parent: false but I found very little information regarding this.

How would such a scenario be set up?

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