Is there anything horribly wrong with that?
I'm trying to get files indexed (via ingest attachment plugin)and searchable, but not stored in ES.
Likeso:
Would the remove processor still keep the data of the field indexed & not store, does that mean that remove processor only removes the field from the source whereas the value is persisted in the index ?
Sorry for hijacking this thread but the question came out of curiosity.
Thank you both for your answers.
Okay - I think I see the issue here.
Since neither base64 nor the actual file will be stored in the index, if we try to copy the document to another index via reindex api we won't be able to do so reliably for the terms of the file itself, as reindex api works with _source to do the copy.
Now if a user wants to upload a different document by 'editing' the existing one we would simply re-index it into segments and re-exclude it again. We are also only excluding the source fields related to that file, so we should also still be able to update the document with new/changed metadata fields (assigned tags and categories, who is it shared with etc).
That sound right?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.