<?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: Reading JSON file to columns as relational ? in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/reading-json-file-to-columns-as-relational/m-p/147895#M52788</link>
    <description>&lt;P&gt;You can read a JSON file into &lt;STRONG&gt;relational columns&lt;/STRONG&gt; in Databricks by explicitly binding a schema and choosing the right parsing mode.&lt;/P&gt;&lt;H3&gt;PySpark (recommended when you already have a schema JSON)&lt;/H3&gt;&lt;PRE&gt;import json
from pyspark.sql.types import StructType

schema_json = json.loads(dbutils.fs.head(
    "file:/Workspace/path/receipt.schema.json", 1000000))
schema = StructType.fromJson(schema_json)

df = (spark.read
      .schema(schema)
      .option("multiLine", "true")  # if JSON is multi-line
      .option("mode", "PERMISSIVE")
      .option("columnNameOfCorruptRecord", "_corrupt_record")
      .json("file:/Workspace/path/receipt.json"))

display(df)&lt;/PRE&gt;&lt;P&gt;&lt;STRONG&gt;Error handling&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;PERMISSIVE → keeps rows, bad records go to _corrupt_record&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;DROPMALFORMED → drops bad rows&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;FAILFAST → fails on first error&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;H3&gt;Databricks SQL&lt;/H3&gt;&lt;PRE&gt;SELECT
  from_json(content,
    schema_of_json(
      (SELECT content
       FROM read_files('file:/Workspace/path/receipt.schema.json', format =&amp;gt; 'text')
      )
  ) AS parsed
FROM read_files('file:/Workspace/path/receipt.json', format =&amp;gt; 'text');&lt;/PRE&gt;&lt;P&gt;Then select fields from parsed to get relational columns.&lt;/P&gt;&lt;H3&gt;Notes&lt;/H3&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Use file:/Workspace/... paths for workspace files (best for small dev/test data).&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;For production, use DBFS Volumes or cloud storage.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;Docs&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Workspace files: &lt;A href="https://docs.databricks.com/files/workspace-interact.html" target="_blank" rel="noopener"&gt;https://docs.databricks.com/files/workspace-interact.html&lt;/A&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;JSON parsing &amp;amp; error modes: &lt;A href="https://docs.databricks.com/sql/language-manual/functions/from_json.html" target="_blank" rel="noopener"&gt;https://docs.databricks.com/sql/language-manual/functions/from_json.html&lt;/A&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;read_files() (SQL): &lt;A href="https://docs.databricks.com/sql/language-manual/functions/read_files.html" target="_blank" rel="noopener"&gt;https://docs.databricks.com/sql/language-manual/functions/read_files.html&lt;/A&gt;&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;HR /&gt;</description>
    <pubDate>Tue, 10 Feb 2026 12:22:00 GMT</pubDate>
    <dc:creator>bianca_unifeye</dc:creator>
    <dc:date>2026-02-10T12:22:00Z</dc:date>
    <item>
      <title>Reading JSON file to columns as relational ?</title>
      <link>https://community.databricks.com/t5/data-engineering/reading-json-file-to-columns-as-relational/m-p/147795#M52777</link>
      <description>&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;P&gt;Reading JSON file to columns as relational ?&lt;/P&gt;&lt;P&gt;======================================&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for reviewing my threads. I like to explore Reading JSON file to columns as relational&amp;nbsp; within Databricks.&lt;/P&gt;&lt;P&gt;I have input file at workspace path &amp;gt; path\receipt.json&lt;/P&gt;&lt;P&gt;I have schema at workspace path &amp;gt; path\receipt.schema.json&lt;/P&gt;&lt;P&gt;How can I read the input json file binding with schema and output the data in relational columns?&lt;/P&gt;&lt;P&gt;I like to have both option with SQL , pyspark.&lt;/P&gt;&lt;P&gt;What to do with errors while parsing ?&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Are there any doc/whitepapers on this subject?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Thanks for your insights.&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 09 Feb 2026 22:35:25 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/reading-json-file-to-columns-as-relational/m-p/147795#M52777</guid>
      <dc:creator>RIDBX</dc:creator>
      <dc:date>2026-02-09T22:35:25Z</dc:date>
    </item>
    <item>
      <title>Re: Reading JSON file to columns as relational ?</title>
      <link>https://community.databricks.com/t5/data-engineering/reading-json-file-to-columns-as-relational/m-p/147895#M52788</link>
      <description>&lt;P&gt;You can read a JSON file into &lt;STRONG&gt;relational columns&lt;/STRONG&gt; in Databricks by explicitly binding a schema and choosing the right parsing mode.&lt;/P&gt;&lt;H3&gt;PySpark (recommended when you already have a schema JSON)&lt;/H3&gt;&lt;PRE&gt;import json
from pyspark.sql.types import StructType

schema_json = json.loads(dbutils.fs.head(
    "file:/Workspace/path/receipt.schema.json", 1000000))
schema = StructType.fromJson(schema_json)

df = (spark.read
      .schema(schema)
      .option("multiLine", "true")  # if JSON is multi-line
      .option("mode", "PERMISSIVE")
      .option("columnNameOfCorruptRecord", "_corrupt_record")
      .json("file:/Workspace/path/receipt.json"))

display(df)&lt;/PRE&gt;&lt;P&gt;&lt;STRONG&gt;Error handling&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;PERMISSIVE → keeps rows, bad records go to _corrupt_record&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;DROPMALFORMED → drops bad rows&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;FAILFAST → fails on first error&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;H3&gt;Databricks SQL&lt;/H3&gt;&lt;PRE&gt;SELECT
  from_json(content,
    schema_of_json(
      (SELECT content
       FROM read_files('file:/Workspace/path/receipt.schema.json', format =&amp;gt; 'text')
      )
  ) AS parsed
FROM read_files('file:/Workspace/path/receipt.json', format =&amp;gt; 'text');&lt;/PRE&gt;&lt;P&gt;Then select fields from parsed to get relational columns.&lt;/P&gt;&lt;H3&gt;Notes&lt;/H3&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Use file:/Workspace/... paths for workspace files (best for small dev/test data).&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;For production, use DBFS Volumes or cloud storage.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;Docs&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Workspace files: &lt;A href="https://docs.databricks.com/files/workspace-interact.html" target="_blank" rel="noopener"&gt;https://docs.databricks.com/files/workspace-interact.html&lt;/A&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;JSON parsing &amp;amp; error modes: &lt;A href="https://docs.databricks.com/sql/language-manual/functions/from_json.html" target="_blank" rel="noopener"&gt;https://docs.databricks.com/sql/language-manual/functions/from_json.html&lt;/A&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;read_files() (SQL): &lt;A href="https://docs.databricks.com/sql/language-manual/functions/read_files.html" target="_blank" rel="noopener"&gt;https://docs.databricks.com/sql/language-manual/functions/read_files.html&lt;/A&gt;&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;HR /&gt;</description>
      <pubDate>Tue, 10 Feb 2026 12:22:00 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/reading-json-file-to-columns-as-relational/m-p/147895#M52788</guid>
      <dc:creator>bianca_unifeye</dc:creator>
      <dc:date>2026-02-10T12:22:00Z</dc:date>
    </item>
    <item>
      <title>Re: Reading JSON file to columns as relational ?</title>
      <link>https://community.databricks.com/t5/data-engineering/reading-json-file-to-columns-as-relational/m-p/147929#M52797</link>
      <description>&lt;P&gt;Thanks for weighing in, I tested this piece, I am getting:&lt;/P&gt;&lt;P&gt;"Execution Error: An error occurred while calling o481.head&lt;/P&gt;&lt;P&gt;:org.apache.spark.security.exception : [INSUFFICIENT_PERMISSION] Insufficient previleges&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;user does not have permission to select on any file SQLSTATE : 42501"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How do I fix this? Is it a policy issue for my credentials?&lt;/P&gt;&lt;P&gt;Thanks for your guidance.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 10 Feb 2026 17:49:58 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/reading-json-file-to-columns-as-relational/m-p/147929#M52797</guid>
      <dc:creator>RIDBX</dc:creator>
      <dc:date>2026-02-10T17:49:58Z</dc:date>
    </item>
    <item>
      <title>Re: Reading JSON file to columns as relational ?</title>
      <link>https://community.databricks.com/t5/data-engineering/reading-json-file-to-columns-as-relational/m-p/148402#M52885</link>
      <description>&lt;P&gt;Hi I did not see any response.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Are there any alternate way for use of schema = StructType.fromJson(schema_json)&amp;nbsp; ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 14 Feb 2026 01:01:10 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/reading-json-file-to-columns-as-relational/m-p/148402#M52885</guid>
      <dc:creator>RIDBX</dc:creator>
      <dc:date>2026-02-14T01:01:10Z</dc:date>
    </item>
    <item>
      <title>Re: Reading JSON file to columns as relational ?</title>
      <link>https://community.databricks.com/t5/data-engineering/reading-json-file-to-columns-as-relational/m-p/150120#M53252</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/103045"&gt;@RIDBX&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Thanks for the thorough description. Flattening JSON into relational columns is one of the most common data engineering tasks in Databricks, and there are several powerful approaches depending on your JSON structure. Let me walk you through them.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;STEP 1: READ THE JSON FILE&lt;/P&gt;
&lt;P&gt;The first step is reading your JSON file into a DataFrame. Spark can infer the schema automatically.&lt;/P&gt;
&lt;P&gt;For single-line JSON (one JSON object per line):&lt;/P&gt;
&lt;P&gt;df = spark.read.json("/path/to/your/file.json")&lt;/P&gt;
&lt;P&gt;For multi-line JSON (a single JSON object or array spanning multiple lines, which is the more common format for files exported from APIs):&lt;/P&gt;
&lt;P&gt;df = spark.read.option("multiLine", "true").json("/path/to/your/file.json")&lt;/P&gt;
&lt;P&gt;You can inspect the inferred schema with:&lt;/P&gt;
&lt;P&gt;df.printSchema()&lt;BR /&gt;df.display()&lt;/P&gt;
&lt;P&gt;This is the most important first step because it tells you exactly what nested structures you are dealing with (structs, arrays, arrays of structs, etc.).&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;STEP 2: ACCESS NESTED STRUCT FIELDS (DOT NOTATION)&lt;/P&gt;
&lt;P&gt;If your JSON has nested objects like:&lt;/P&gt;
&lt;P&gt;{"name": "Alice", "address": {"city": "Seattle", "state": "WA"}}&lt;/P&gt;
&lt;P&gt;Spark reads "address" as a StructType. You can flatten it by selecting individual fields using dot notation:&lt;/P&gt;
&lt;P&gt;from pyspark.sql.functions import col&lt;/P&gt;
&lt;P&gt;df_flat = df.select(&lt;BR /&gt;col("name"),&lt;BR /&gt;col("address.city").alias("city"),&lt;BR /&gt;col("address.state").alias("state")&lt;BR /&gt;)&lt;/P&gt;
&lt;P&gt;You can also use the star (*) operator to expand ALL fields in a struct:&lt;/P&gt;
&lt;P&gt;df_flat = df.select("name", "address.*")&lt;/P&gt;
&lt;P&gt;This automatically creates one column per field inside the "address" struct.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;STEP 3: EXPLODE ARRAYS INTO ROWS&lt;/P&gt;
&lt;P&gt;If your JSON has arrays like:&lt;/P&gt;
&lt;P&gt;{"customer": "Alice", "orders": [{"id": 1, "amount": 50}, {"id": 2, "amount": 75}]}&lt;/P&gt;
&lt;P&gt;You need to use explode() to turn each array element into its own row:&lt;/P&gt;
&lt;P&gt;from pyspark.sql.functions import explode&lt;/P&gt;
&lt;P&gt;df_exploded = df.select(&lt;BR /&gt;col("customer"),&lt;BR /&gt;explode(col("orders")).alias("order")&lt;BR /&gt;)&lt;/P&gt;
&lt;P&gt;This gives you one row per order. Since each element is a struct, combine with dot notation:&lt;/P&gt;
&lt;P&gt;df_final = df_exploded.select(&lt;BR /&gt;col("customer"),&lt;BR /&gt;col("order.id").alias("order_id"),&lt;BR /&gt;col("order.amount").alias("order_amount")&lt;BR /&gt;)&lt;/P&gt;
&lt;P&gt;Or do it in one step using inline(), which explodes an array of structs directly into columns:&lt;/P&gt;
&lt;P&gt;from pyspark.sql.functions import inline&lt;/P&gt;
&lt;P&gt;df_final = df.select(&lt;BR /&gt;col("customer"),&lt;BR /&gt;inline(col("orders"))&lt;BR /&gt;)&lt;/P&gt;
&lt;P&gt;Note: inline() is available in Databricks Runtime 12.2 LTS and above as a table-valued generator.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;STEP 4: HANDLE DEEPLY NESTED JSON&lt;/P&gt;
&lt;P&gt;For deeply nested JSON, you may need to chain these operations. For example:&lt;/P&gt;
&lt;P&gt;{&lt;BR /&gt;"company": "Acme",&lt;BR /&gt;"departments": [&lt;BR /&gt;{&lt;BR /&gt;"name": "Engineering",&lt;BR /&gt;"employees": [&lt;BR /&gt;{"name": "Alice", "skills": ["Python", "Spark"]},&lt;BR /&gt;{"name": "Bob", "skills": ["Java", "Scala"]}&lt;BR /&gt;]&lt;BR /&gt;}&lt;BR /&gt;]&lt;BR /&gt;}&lt;/P&gt;
&lt;P&gt;You would flatten this step by step:&lt;/P&gt;
&lt;P&gt;from pyspark.sql.functions import col, explode&lt;/P&gt;
&lt;P&gt;# Step 1: Explode departments array&lt;BR /&gt;df1 = df.select(&lt;BR /&gt;col("company"),&lt;BR /&gt;explode(col("departments")).alias("dept")&lt;BR /&gt;)&lt;/P&gt;
&lt;P&gt;# Step 2: Explode employees array within each department&lt;BR /&gt;df2 = df1.select(&lt;BR /&gt;col("company"),&lt;BR /&gt;col("dept.name").alias("department"),&lt;BR /&gt;explode(col("dept.employees")).alias("emp")&lt;BR /&gt;)&lt;/P&gt;
&lt;P&gt;# Step 3: Explode skills array and extract employee name&lt;BR /&gt;df3 = df2.select(&lt;BR /&gt;col("company"),&lt;BR /&gt;col("department"),&lt;BR /&gt;col("emp.name").alias("employee_name"),&lt;BR /&gt;explode(col("emp.skills")).alias("skill")&lt;BR /&gt;)&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;SQL APPROACH: THE COLON (:) SYNTAX&lt;/P&gt;
&lt;P&gt;If you prefer SQL, Databricks has a powerful colon operator for accessing nested JSON fields. First, register your data as a view:&lt;/P&gt;
&lt;P&gt;df.createOrReplaceTempView("raw_data")&lt;/P&gt;
&lt;P&gt;Then query nested fields directly:&lt;/P&gt;
&lt;P&gt;SELECT&lt;BR /&gt;raw:customer::string AS customer,&lt;BR /&gt;raw:orders[0].id::int AS first_order_id,&lt;BR /&gt;raw:orders[0].amount::double AS first_order_amount&lt;BR /&gt;FROM raw_data&lt;/P&gt;
&lt;P&gt;For exploding arrays in SQL:&lt;/P&gt;
&lt;P&gt;SELECT&lt;BR /&gt;raw:customer::string AS customer,&lt;BR /&gt;order_data.id::int AS order_id,&lt;BR /&gt;order_data.amount::double AS order_amount&lt;BR /&gt;FROM raw_data,&lt;BR /&gt;LATERAL VIEW explode(from_json(&lt;BR /&gt;raw:orders,&lt;BR /&gt;'ARRAY&amp;lt;STRUCT&amp;lt;id: INT, amount: DOUBLE&amp;gt;&amp;gt;'&lt;BR /&gt;)) AS order_data&lt;/P&gt;
&lt;P&gt;Or if your table already has a properly inferred schema (not stored as a raw string column):&lt;/P&gt;
&lt;P&gt;SELECT&lt;BR /&gt;customer,&lt;BR /&gt;o.id AS order_id,&lt;BR /&gt;o.amount AS order_amount&lt;BR /&gt;FROM my_table&lt;BR /&gt;LATERAL VIEW explode(orders) AS o&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;BONUS: USING from_json() FOR STRING COLUMNS&lt;/P&gt;
&lt;P&gt;If your JSON is stored as a plain string column (for example, from a Kafka topic or a text file), use from_json() with a schema to parse it:&lt;/P&gt;
&lt;P&gt;from pyspark.sql.functions import from_json, schema_of_json&lt;/P&gt;
&lt;P&gt;# Let Spark infer the schema from a sample&lt;BR /&gt;json_sample = '{"name": "Alice", "address": {"city": "Seattle"}}'&lt;BR /&gt;schema = schema_of_json(json_sample)&lt;/P&gt;
&lt;P&gt;df_parsed = df.select(&lt;BR /&gt;from_json(col("json_string_column"), schema).alias("parsed")&lt;BR /&gt;).select("parsed.*")&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;QUICK REFERENCE: WHICH FUNCTION TO USE&lt;/P&gt;
&lt;P&gt;- Nested objects (structs) --&amp;gt; col("parent.child") or select("parent.*")&lt;BR /&gt;- Arrays --&amp;gt; explode() to get one row per element&lt;BR /&gt;- Arrays of structs --&amp;gt; inline() to get rows AND columns in one step&lt;BR /&gt;- Nested arrays --&amp;gt; flatten() first, then explode()&lt;BR /&gt;- JSON string column --&amp;gt; from_json() to parse, then use the above&lt;BR /&gt;- SQL queries --&amp;gt; use the : colon operator for extraction&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;DOCUMENTATION LINKS&lt;/P&gt;
&lt;P&gt;- Reading JSON files: &lt;A href="https://docs.databricks.com/en/query/formats/json.html" target="_blank"&gt;https://docs.databricks.com/en/query/formats/json.html&lt;/A&gt;&lt;BR /&gt;- Querying semi-structured data (colon syntax): &lt;A href="https://docs.databricks.com/en/sql/language-manual/sql-ref-json-path-expression.html" target="_blank"&gt;https://docs.databricks.com/en/sql/language-manual/sql-ref-json-path-expression.html&lt;/A&gt;&lt;BR /&gt;- explode() function: &lt;A href="https://docs.databricks.com/en/sql/language-manual/functions/explode.html" target="_blank"&gt;https://docs.databricks.com/en/sql/language-manual/functions/explode.html&lt;/A&gt;&lt;BR /&gt;- inline() function: &lt;A href="https://docs.databricks.com/en/sql/language-manual/functions/inline.html" target="_blank"&gt;https://docs.databricks.com/en/sql/language-manual/functions/inline.html&lt;/A&gt;&lt;BR /&gt;- from_json() function: &lt;A href="https://docs.databricks.com/en/sql/language-manual/functions/from_json.html" target="_blank"&gt;https://docs.databricks.com/en/sql/language-manual/functions/from_json.html&lt;/A&gt;&lt;BR /&gt;- schema_of_json() function: &lt;A href="https://docs.databricks.com/en/sql/language-manual/functions/schema_of_json.html" target="_blank"&gt;https://docs.databricks.com/en/sql/language-manual/functions/schema_of_json.html&lt;/A&gt;&lt;BR /&gt;- flatten() function: &lt;A href="https://docs.databricks.com/en/sql/language-manual/functions/flatten.html" target="_blank"&gt;https://docs.databricks.com/en/sql/language-manual/functions/flatten.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;If you can share a sample of your JSON structure, I can give you a more specific solution tailored to your data. Hope this helps!&lt;/P&gt;
&lt;P&gt;* This reply used an agent system I built to research and draft this response based on the wide set of documentation I have available and previous memory. I personally review the draft for any obvious issues and for monitoring system reliability and update it when I detect any drift, but there is still a small chance that something is inaccurate, especially if you are experimenting with brand new features.&lt;/P&gt;</description>
      <pubDate>Sun, 08 Mar 2026 04:12:43 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/reading-json-file-to-columns-as-relational/m-p/150120#M53252</guid>
      <dc:creator>SteveOstrowski</dc:creator>
      <dc:date>2026-03-08T04:12:43Z</dc:date>
    </item>
    <item>
      <title>Re: Reading JSON file to columns as relational ?</title>
      <link>https://community.databricks.com/t5/data-engineering/reading-json-file-to-columns-as-relational/m-p/151174#M53607</link>
      <description>&lt;P&gt;Hi, this looks like you don't have select persmision on where you have saved the file? Is it in a UC volume?&lt;/P&gt;</description>
      <pubDate>Tue, 17 Mar 2026 17:58:04 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/reading-json-file-to-columns-as-relational/m-p/151174#M53607</guid>
      <dc:creator>emma_s</dc:creator>
      <dc:date>2026-03-17T17:58:04Z</dc:date>
    </item>
  </channel>
</rss>

