<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Structured Streaming using an ADF (Azure Data Factory) pipeline issue on RLS enabled table in Data Governance</title>
    <link>https://community.databricks.com/t5/data-governance/structured-streaming-using-an-adf-azure-data-factory-pipeline/m-p/127717#M2563</link>
    <description>&lt;P&gt;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/89888"&gt;@mani_22&lt;/a&gt;&amp;nbsp;, Thank you for your response, We are using unity catalog path to read or write table and we were able to idenitfy the root cause and fixed it. We had a check point location created inside the table location where RLS is applied , it causing a path based access issues, it started working after we moved the check point outside the table location. Thanks again.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 07 Aug 2025 18:44:39 GMT</pubDate>
    <dc:creator>karunakaran_r</dc:creator>
    <dc:date>2025-08-07T18:44:39Z</dc:date>
    <item>
      <title>Structured Streaming using an ADF (Azure Data Factory) pipeline issue on RLS enabled table</title>
      <link>https://community.databricks.com/t5/data-governance/structured-streaming-using-an-adf-azure-data-factory-pipeline/m-p/126488#M2545</link>
      <description>&lt;P&gt;We are in the process of implementing Row-Level Security (RLS) on a table in Databricks. As per our architecture, data ingestion is handled via Structured Streaming using an ADF (Azure Data Factory) pipeline.&lt;/P&gt;&lt;P&gt;However, we are encountering the following error during ingestion:&lt;/P&gt;&lt;P&gt;sql&lt;BR /&gt;Copy&lt;BR /&gt;Edit&lt;BR /&gt;pyspark.errors.exceptions.connect.AnalysisException:&lt;BR /&gt;[RequestId=a1541086-31ad-48e3-8781-3caefaae2c63&lt;BR /&gt;ErrorClass=INVALID_PARAMETER_VALUE.PATH_BASED_ACCESS_NOT_SUPPORTED_FOR_TABLES_WITH_ROW_COLUMN_ACCESS_POLICIES]&lt;BR /&gt;Path-based access to table ********* with row filter or column mask not supported.&lt;BR /&gt;We’ve verified that we are using the full Unity Catalog-qualified table path for both reading from and writing to the table. However, the checkpoint location is currently specified as a path (e.g., abfss://...).&lt;/P&gt;&lt;P&gt;Could this path-based checkpointing be the root cause of the issue? If so, what is the recommended approach to ingest data using Structured Streaming into an RLS-enabled table while complying with Unity Catalog constraints?&lt;/P&gt;&lt;P&gt;We would appreciate guidance on how to properly configure the checkpointing or ingestion process in this context.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;streaming_query = df\&lt;BR /&gt;.withColumn(BUSINESS_UNIT_COLUMN, lit(business_unit))\&lt;BR /&gt;.withColumn(SEGMENT_NAME_COLUMN, lit(segment_name))\&lt;BR /&gt;.withColumn(SOURCE_SYSTEM_NAME_COLUMN, lit(source_system_name))\&lt;BR /&gt;.writeStream \&lt;BR /&gt;.foreachBatch(process_batch) \&lt;BR /&gt;.outputMode("append")\&lt;BR /&gt;.option("checkpointLocation", checkpoint_file_path_gold)\&lt;BR /&gt;.option("skipChangeCommits", "true")\&lt;BR /&gt;.trigger(availableNow=True)\&lt;BR /&gt;.start()&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 25 Jul 2025 16:55:43 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-governance/structured-streaming-using-an-adf-azure-data-factory-pipeline/m-p/126488#M2545</guid>
      <dc:creator>karunakaran_r</dc:creator>
      <dc:date>2025-07-25T16:55:43Z</dc:date>
    </item>
    <item>
      <title>Re: Structured Streaming using an ADF (Azure Data Factory) pipeline issue on RLS enabled table</title>
      <link>https://community.databricks.com/t5/data-governance/structured-streaming-using-an-adf-azure-data-factory-pipeline/m-p/126743#M2551</link>
      <description>&lt;P&gt;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/140860"&gt;@karunakaran_r&lt;/a&gt;&amp;nbsp;Are you trying to read or write to a table with RLS/CM enabled using a file path directly instead of specifying the table name?&lt;/P&gt;
&lt;P&gt;You cannot specify the table path for reading and writing tables with RLS/CM enabled.&amp;nbsp;You would have to read the table by its catalog and schema.&lt;/P&gt;
&lt;P&gt;Eg:&lt;/P&gt;
&lt;P class="p1"&gt;=&amp;gt; Use spark.read.table("my_catalog.my_schema.my_secure_table")&amp;nbsp;instead of spark.read.format("delta").load(“abfss:/my-secure-table-path")&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 28 Jul 2025 20:40:07 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-governance/structured-streaming-using-an-adf-azure-data-factory-pipeline/m-p/126743#M2551</guid>
      <dc:creator>mani_22</dc:creator>
      <dc:date>2025-07-28T20:40:07Z</dc:date>
    </item>
    <item>
      <title>Re: Structured Streaming using an ADF (Azure Data Factory) pipeline issue on RLS enabled table</title>
      <link>https://community.databricks.com/t5/data-governance/structured-streaming-using-an-adf-azure-data-factory-pipeline/m-p/127717#M2563</link>
      <description>&lt;P&gt;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/89888"&gt;@mani_22&lt;/a&gt;&amp;nbsp;, Thank you for your response, We are using unity catalog path to read or write table and we were able to idenitfy the root cause and fixed it. We had a check point location created inside the table location where RLS is applied , it causing a path based access issues, it started working after we moved the check point outside the table location. Thanks again.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 07 Aug 2025 18:44:39 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-governance/structured-streaming-using-an-adf-azure-data-factory-pipeline/m-p/127717#M2563</guid>
      <dc:creator>karunakaran_r</dc:creator>
      <dc:date>2025-08-07T18:44:39Z</dc:date>
    </item>
  </channel>
</rss>

