(Spike) Cubejs Preagg when configured with S3 bucket

[victoralfaro-dotcms]

User Story

As a software engineer, I want to research the reason behind the error and determine a solution so that pre-aggregations can be created when massive data needs to be queried in the CubeJS setup for dotCMS analytics infrastructure.

Acceptance Criteria

• Identify the root cause of the CubeJS pre-aggregation failure when using S3 for storage.
• Document the findings with logs and possible misconfigurations.
• Propose a fix or workaround to allow pre-aggregations to be stored correctly in production.
• Validate the solution locally and in a staging/production-like environment.

dotCMS Version

main

Proposed Objective

Quality Assurance

Proposed Priority

Priority 2 - Important

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

to_define

Assumptions & Initiation Needs

• CubeJS is correctly configured to use S3 storage in production.
• Pre-aggregations work correctly in a local development environment.
• The error is related to how CubeJS interacts with S3 storage.

Quality Assurance Notes & Workarounds

• Verify if S3 permissions, policies, or configurations impact the upload process.
• Test different CubeJS storage options for pre-aggregations.
• Ensure network connectivity and access rights to S3 from the production environment.
• Identify any missing dependencies or incorrect CubeJS settings.

Sub-Tasks & Estimates

• Investigate error logs and analyze root cause (4h)
• Review CubeJS and S3 configuration settings (3h)
• Document findings and proposed solution (3h)