crate / crate/croud

API: Improve representation of job's metadata `destination.table` attribute

Open
#566 0 comments 0 reactions 1 assignee Claimed by @tomach View on GitHub
Dominant language
Python
Stars
5
Forks
1
PR merge metrics
No merged PRs in 30d

Description

## About
We'd like to share an observation about suboptimal handling of schema and table names within job metadata as relayed by the Cloud API or its Croud client wrapper.

## Details
It is about the `destination.table` attribute within the job information metadata payload: Currently, if the observation from Nov 2023 still holds true, it includes both schema and table name within an opaque string like `.`, but the individual components are not quoted properly according to CrateDB/SQL standards, so downstream software components need to [compensate](https://github.com/crate/cratedb-toolkit/blob/e3d0290408261fc4322144ad2b49cd797ad985e6/cratedb_toolkit/io/croud.py#L67-L83).

## References
- https://github.com/crate/cratedb-toolkit/pull/81#discussion_r1397878562

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.