Samigo should bypass byte array manipulation and provide direct link to asset

Description

Samigo has used ContentHostingService for asset storage for many versions. CloudContent allows institutions to save content in object storage like Swift or S3. Instead of doing byte manipulation of assets, serve the content directly and avoid loading the asset in JVM heap.

Attachments

8

Activity

Show:

Jacob Cira January 11, 2023 at 8:50 PM

When taking my test as student, I could see the PDF attachment at the beginning of the test, I could see the picture attachment in the according question, and I could play back student-recorded audio. As instructor, I could play the student audio as well. This seems to match the test plan, so I am marking this as verified.

21x https://qa21-mysql.nightly.sakaiproject.org build 632c5116

Earle Nietzel September 28, 2022 at 2:41 PM

Automation for Jira removed the versions will look into this as it shouldn’t be removing versions

Daniel Merino March 7, 2022 at 9:06 AM

After talking about this, most S2U institutions were using mediaToDb=false and we have SAM_MEDIA_T with thousands of attachments right now.

I think that we could not be the only ones across the world with this setting. This change could block the migration of many institutions to newer versions.

Please, if somebody develops a fix it should be added to this JIRA and to the migration documentation.

Andrea Schmidt March 5, 2022 at 4:43 PM
Edited

Verified on 22x: https://qa22-mysql.nightly.sakaiproject.org/, build: 8947e9b0

Created - not sure if it’s related to this fix

Juanjo Meroño February 25, 2022 at 9:45 AM

Unfortunately the conversion media process in Sakai 11 was designed only for deployments that were using mediaToDb=TRUE. We were using mediaToDb=FALSE since the beginning, so we couldn’t run this conversion, and things keep working because mediaToDb=FALSE still work.

Now we have to change the conversion process to be able to run it and move files (already out of the database in a disk location) to another location in ContentHostingService. The documentation in the property it also wasn’t helpful to clarify that the conversion was mandatory at that time:

I don’t know if there are more deployments that nowadays still using mediaToDb=false, anyway, it is what it is.

Thanks.

Fixed

Details

Priority

Affects versions

Fix versions

22 Status

Verified

Components

Assignee

Reporter

Labels

Conversion Script Required

Yes

Created October 11, 2021 at 8:32 PM
Updated January 11, 2023 at 8:50 PM
Resolved December 3, 2021 at 10:31 PM