[Question] support for native field selection?

[GalacticHypernova]

I couldn't find any definitive answer in the docs, nor in the configuration options.

I was wondering if monstache supports native field selection for indexing?

My use case is I store a subset of fields relevant to the search in elasticsearch, while the entire document is stored in MongoDB. Since elasticsearch is memory intensive, I figured it would be best this way as any unnecessary data would increase index size and degrade performance.

I know Monstache supports native collection selections to narrow down the sources to index, but does it also support field selection to narrow down the data to index?

[dblado]

I believe what you are looking for is not on the monstache side, but on the elasticsearch side: https://www.elastic.co/docs/manage-data/data-store/mapping/dynamic-field-mapping

Setting dynamic to false will prevent ES from automatically indexing fields that were not defined in the mapping.

[GalacticHypernova]

I believe what you are looking for is not on the monstache side, but on the elasticsearch side: https://www.elastic.co/docs/manage-data/data-store/mapping/dynamic-field-mapping

Setting dynamic to false will prevent ES from automatically indexing fields that were not defined in the mapping.

Hey, sorry for missing your reply,

Thanks for the link, but setting dynamic to false still stores it. What I was referring to was dropping it entirely (similar to an ingest pipeline, but perhaps more streamlined on the database level as that would be more performant).