Answers to: How to persist fields in ivy repo but not index in elastic?

Comment by Alex Suter on skilchenmann's answer

Alex Suter — Wed, 25 Sep 2019 14:24:49 -0400

I strongly recommend to not store files in business data. It was never intended for it!

Comment by adamf on skilchenmann's answer

adamf — Tue, 24 Sep 2019 04:57:59 -0400

Thank you for the answers. I have a similar Impression that we should use the database persistence https://developer.axonivy.com/doc/7.0.11/DesignerGuideHtml/ivy.datamodeling.html#ivy-persistence for the document and create a DocumentService that get a path from elastic and return the blob from the database. And that would be similar to existing solutions using the disk as storage.

Comment by Christian Strebel on skilchenmann's answer

Christian Strebel — Tue, 24 Sep 2019 04:14:52 -0400

Yes but they are still in the source json and so also stored by elastic search...

Answer by Christian Strebel

Christian Strebel — Tue, 24 Sep 2019 04:14:08 -0400

There are ways that elasticsearch does not index some fields, but they are still in the source and go over the wire and are saved in the elastic search. So there is nothing at the moment which does really exclude some fields form the json which goes to the elasticsearch.

For me the easiest way would be if you store the files in our own table in the database and just reference it form the BusinessData.

Answer by skilchenmann

skilchenmann — Tue, 24 Sep 2019 04:09:06 -0400

you could define if a field should be indexed or not: https://www.elastic.co/guide/en/elasticsearch/reference/current/enabled.html

as a semi solution ;)