[
https://issues.apache.org/jira/browse/ATLAS-5397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sanket bhor updated ATLAS-5397:
-------------------------------
Description:
h3. Summary:
When Trino sends an ENTITY_CREATE_V2 notification for a CREATE SCHEMA with an
explicit HDFS location, the location attribute is included in the trino_schema
entity payload but is silently dropped by Atlas during entity creation. The
custom HDFS path is only visible on the associated hive_db entity (created by
the Hive Metastore bridge), not on the trino_schema entity itself.
h3. Steps to Reproduce :
# Execute a Trino CREATE SCHEMA with an explicit location:
{code:java}
{{CREATE SCHEMA hive_catalog.trino_schema_hdfs_test4
WITH (
location =
'hdfs://ccycloud-1.sb-iceberg-typedef.root.comops.site:8020/tmp/trino_schema_hdfs_test'
) }}{code}
# Trino sends an ENTITY_CREATE_V2 event with trino_schema entity containing
"location": "hdfs://..." in attributes.
# Atlas creates the trino_schema entity but the location attribute value is
not persisted.
h3. Expected Behavior :
The location attribute should be stored on the trino_schema entity
(hive_catalog.<schema>@cm) and visible in Atlas UI / REST API.
h3. Actual Behavior :
The location attribute is silently dropped. It only appears on the hive_db
entity created by the Hive Metastore bridge via the trino_schema_hive_db
relationship. The trino_schema entity has no location value.
h3.
was:
h3. Summary:
When Trino sends an ENTITY_CREATE_V2 notification for a CREATE SCHEMA with an
explicit HDFS location, the location attribute is included in the trino_schema
entity payload but is silently dropped by Atlas during entity creation. The
custom HDFS path is only visible on the associated hive_db entity (created by
the Hive Metastore bridge), not on the trino_schema entity itself.
h3. Steps to Reproduce :
# Execute a Trino CREATE SCHEMA with an explicit location:
{{CREATE SCHEMA hive_catalog.trino_schema_hdfs_test4
WITH (
location =
'hdfs://ccycloud-1.sb-iceberg-typedef.root.comops.site:8020/tmp/trino_schema_hdfs_test'
) }}
# Trino sends an ENTITY_CREATE_V2 event with trino_schema entity containing
"location": "hdfs://..." in attributes.
# Atlas creates the trino_schema entity but the location attribute value is
not persisted.
h3. Expected Behavior :
The location attribute should be stored on the trino_schema entity
(hive_catalog.<schema>@cm) and visible in Atlas UI / REST API.
h3. Actual Behavior :
The location attribute is silently dropped. It only appears on the hive_db
entity created by the Hive Metastore bridge via the trino_schema_hive_db
relationship. The trino_schema entity has no location value.
h3.
> trino_schema entity does not persist location attribute sent in CREATE SCHEMA
> events
> ------------------------------------------------------------------------------------
>
> Key: ATLAS-5397
> URL: https://issues.apache.org/jira/browse/ATLAS-5397
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Reporter: sanket bhor
> Assignee: sanket bhor
> Priority: Major
>
> h3. Summary:
> When Trino sends an ENTITY_CREATE_V2 notification for a CREATE SCHEMA with an
> explicit HDFS location, the location attribute is included in the
> trino_schema entity payload but is silently dropped by Atlas during entity
> creation. The custom HDFS path is only visible on the associated hive_db
> entity (created by the Hive Metastore bridge), not on the trino_schema entity
> itself.
> h3. Steps to Reproduce :
> # Execute a Trino CREATE SCHEMA with an explicit location:
> {code:java}
> {{CREATE SCHEMA hive_catalog.trino_schema_hdfs_test4
> WITH (
> location =
> 'hdfs://ccycloud-1.sb-iceberg-typedef.root.comops.site:8020/tmp/trino_schema_hdfs_test'
>
> ) }}{code}
> # Trino sends an ENTITY_CREATE_V2 event with trino_schema entity containing
> "location": "hdfs://..." in attributes.
> # Atlas creates the trino_schema entity but the location attribute value is
> not persisted.
> h3. Expected Behavior :
> The location attribute should be stored on the trino_schema entity
> (hive_catalog.<schema>@cm) and visible in Atlas UI / REST API.
> h3. Actual Behavior :
> The location attribute is silently dropped. It only appears on the hive_db
> entity created by the Hive Metastore bridge via the trino_schema_hive_db
> relationship. The trino_schema entity has no location value.
> h3.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
