upload part URLs and signed clip download URLs when video-clipping.storage=s3. The current in-memory adapter remains the default. I also added the supporting configuration fields in src/main/ java/org/example/videoclips/config/VideoClippingProperties.java and default values in src/main/resources/application.properties. The queue port now has a durable database-backed implementation in src/main/java/org/example/videoclips/queue/DatabaseBackedClipJobQueueAdapter.java. It persists queue messages in a new queue_messages table from src/main/resources/db/migration/V2__queue_messages.sql, polls them on a schedule, and dispatches them through the existing processor. I updated src/main/java/org/ example/videoclips/processing/ClipProcessor.java so processing failures propagate back to the queue adapter instead of being swallowed. I also enabled scheduling in src/main/java/org/example/videoclips/VideoClippingApplication.java, added the AWS SDK dependency in pom.xml, and updated src/main/resources/application-jpa.properties so the JPA profile uses the database queue by default. |
||
|---|---|---|
| .idea | ||
| docs | ||
| src | ||
| .gitignore | ||
| pom.xml | ||