cube-js/cube

schemas ingested via repositoryFactory do not appear in the playground schemas tab

Open

#3,908 opened on Jan 11, 2022

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Rust (19,563 stars) (1,965 forks)batch import
help wanted

Description

Describe the bug When implementing a custom repositoryFactory (e.g. my s3 implementation), files ingested by cubejs do not appear under the schemas tab in the playground, although measures and dimensions appear as expected.

To Reproduce Steps to reproduce the behavior:

  1. Implement a custom repositoryFactory in cube.js
  2. visit /#/schema in the playground
  3. note that files are not listed there

Expected behavior A list of files (e.g. files ingested via s3) appears in the list

Version: v0.28.57

Contributor guide

Tech stack
javascripttypescriptnodejs
Domain
frontendbackend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic understanding of Cube.jsFamiliarity with custom repositoryFactory
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate how the playground schema tab retrieves and displays files from repositoryFactory. Look at the implementation in the Cube.js repository, likely under packages/cubejs playground or similar. The issue mentions that measures and dimensions appear but files do not, so the bug may be in the file listing logic. Check if there is a missing API endpoint or filtering that excludes custom repository files. Also review the linked gist for the S3 repositoryFactory to understand the expected behavior.