You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
.withQuery("select id, first_name, last_name from public.users")
reported lineage is reporting table segment as public.users.
expected output should be two segments: public, users as per Dataplex FQN spec: cloudsql_{scheme}:{projectId}.{location}.{instanceId}.{databaseId}.{schemaId}.{tableId}
if sql query/inputed table is missing schema then beam reports: cloudsql_{scheme}:{projectId}.{location}.{instanceId}.{databaseId}.{tableId}
which dataplex interprets as cloudsql_{scheme}:{projectId}.{location}.{instanceId}.{databaseId}.{schemaId}
Issue Priority
Priority: 3 (minor)
Issue Components
Component: Python SDK
Component: Java SDK
Component: Go SDK
Component: Typescript SDK
Component: IO connector
Component: Beam YAML
Component: Beam examples
Component: Beam playground
Component: Beam katas
Component: Website
Component: Infrastructure
Component: Spark Runner
Component: Flink Runner
Component: Samza Runner
Component: Twister2 Runner
Component: Hazelcast Jet Runner
Component: Google Cloud Dataflow Runner
The text was updated successfully, but these errors were encountered:
stankiewicz
changed the title
[Bug]: Cloud SQL lineage reports schema and table as one segment
[Bug]: JDBC SQL lineage reports schema and table as one segment
Jan 29, 2025
stankiewicz
changed the title
[Bug]: JDBC SQL lineage reports schema and table as one segment
[Bug]: JDBC SQL lineage reports is missing schema support
Jan 29, 2025
What happened?
when querying JDBCIO:
reported lineage is reporting table segment as
public.users
.expected output should be two segments:
public
,users
as per Dataplex FQN spec:cloudsql_{scheme}:{projectId}.{location}.{instanceId}.{databaseId}.{schemaId}.{tableId}
if sql query/inputed table is missing schema then beam reports:
cloudsql_{scheme}:{projectId}.{location}.{instanceId}.{databaseId}.{tableId}
which dataplex interprets as
cloudsql_{scheme}:{projectId}.{location}.{instanceId}.{databaseId}.{schemaId}
Issue Priority
Priority: 3 (minor)
Issue Components
The text was updated successfully, but these errors were encountered: