Implement 64k limit on extracted_text
Bug #1340295 reported by
Paul Everitt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KARL3 |
Fix Released
|
Low
|
Chris Rossi |
Bug Description
As the followup to lp:1338271 let's take the following steps:
- Change the software to have a configurable size (set at 64k) for the upper limit on when we choose to store the extracted text on the resource as extracted_text
- *AS AN OPTION** gzip the string
- Write a console script which, in a production-friendly way(*), wipes out extracted_text on existing objects
(*) Production-friendly means:
a. Can be run without keeping a site-update from taking forever for an evolve, getting stuck on evolve errors, etc.
b. Doesn't accidentally generate a bunch of email alerts or feed entries
Changed in karl3: | |
milestone: | m138 → m139 |
Changed in karl3: | |
status: | New → In Progress |
tags: | added: r3.130 |
tags: |
added: r3.131 removed: r3.130 |
Changed in karl3: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Committed on branch: better- extracted- text-caching- lp1340295