We are trying to figure the best solution for handling attachments with Appsearch. I saw a thread regarding a hard 10MB limit for file. To overcome Appsearch limitation is to build a custom intermediary solution to parse files and handle either with Tika or use elastic-search attachment ingest and then parse file into JSON and send to Appsearch.
Wanted to know what approach people implement and any issues/constraints we should consider.
I did not see the datatype called "attachments" in the Appsearch documentation
I found a suggestion to use _simulate (which means to post the attachment to elasticsearch first then query the elasticsearch _simulate to get back the data to be submitted to the Appsearch
or
Are we missing something?
Another solution is to use Tika: * programmatically parsing my files with Apache Tika (should I convert them to Base64?)
Not sure this applies to AppSearch but with Elasticsearch you can use:
the size and from parameters to display by default up to 10000 records to your users. If you want to change this limit, you can change index.max_result_window setting but be aware of the consequences (ie memory).
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.