feat: Add a way to retrieve metadata from multiple cubes #1271
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adapts the application logic to support retrieving metadata from multiple cubes at once. As we don't yet a design for this feature, there are some
FIXME: adapt to design
comments in places that would need to be revisited once ready.GQL / SPARQL
DataCubeMetadata
query (replaced byDataCubesMetadata
)DESCRIBE
ing cube shape to only fetching what we actually need via a dedicated, more performant query. To further improve performance and limit resolver chains, I've extracted the dimension types from GQL to TypeScript. It also means that we now explicitly parse them inside the resolver and don't need to fire additional queries to get theme and creator labelsContext
This PR is a second part of preparations for merging the cubes. For the technical concept, see this Notion document.
DataCubesComponents
DataCubesMetadata
DataCubesObservations
How to test
Query
Variables