Implement proper cache bin for caching extracted results

Created on 18 April 2018, over 6 years ago

Updated 17 February 2024, 10 months ago

The module currently caches extracted results in the keyvalue store which is not ideal. We should use a proper cache bin for this instead.

Ideally, we'd have our own cache bin, but we could reuse the data bin if required.

✨ Feature request

Status

Closed: works as designed

Version

1.0

Component

Code

Created by

🇦🇺Australia acbramley

Live updates comments and jobs are added and updated live.

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment about 1 year ago →
🇬🇧United Kingdom hdotnet
Hello,

5 years later, this issue is becoming large for us! With 3k of files, all multi mb PDFs, our key_value table has ballooned to an unmanageable size.

I noticed that text files essentially aren't cached. Do you have any opinions on using the filesystem to store extracted text rather than the key_value table?
Comment 10 months ago →
🇺🇸United States apotek
Added relationship to issue #3084967, which has the solution.

Production build 0.71.5 2024