Investigate and Resolve Cube.js Pre-Aggregation Failures with S3 Storage in dotCMS

[victoralfaro-dotcms]

User Story

As a software engineer, I want to troubleshoot and resolve the Cube.js pre-aggregation failures occurring when S3 is configured as the storage backend, so that large datasets can be efficiently queried within the dotCMS analytics infrastructure.

Acceptance Criteria

• Identify the root cause of the Cube.js pre-aggregation failures with S3 storage.
• Implement a solution or provide a workaround to enable successful pre-aggregation storage in production.
• Validate the implemented solution in both local and staging/production-like environments.

dotCMS Version

main

Proposed Objective

Quality Assurance

Proposed Priority

Priority 2 - Important

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

• Original Issue: #31297
• Related Findings: Issue Comment

Assumptions & Initiation Needs

• Access to environments configured with S3 for Cube.js pre-aggregations.
• Availability of team members familiar with the Cube.js and S3 integration within dotCMS.

Quality Assurance Notes & Workarounds

• Monitor for any recurring issues post-implementation.
• Ensure comprehensive testing is conducted to cover various data scenarios.

Sub-Tasks & Estimates

1. Investigation: Analyze logs and configurations to pinpoint the failure cause. Estimate: 2 days
2. Documentation: Record findings and outline potential solutions. Estimate: 1 day
3. Implementation: Develop and apply the chosen fix or workaround. Estimate: 3 days
4. Validation: Test the solution in local and staging environments to confirm resolution. Estimate: 2 days