topic Re: Error reading in Parquet file in Data Engineering

Error reading in Parquet file

BL — Sat, 14 Jan 2023 12:09:25 GMT

I am trying to read a .parqest file from a ADLS gen2 location in azure databricks . But facing the below error:

spark.read.parquet("abfss://............/..._2023-01-14T08:01:29.8549884Z.parquet")

org.apache.spark.SparkException: Job aborted due to stage failure: Task 0 in stage 0.0 failed 4 times, most recent failure: Lost task 0.3 in stage 0.0 (TID 3) (10.139.64.6 executor 0): org.apache.spark.SparkException: Exception thrown in awaitResult:

I searched in google ( as per suggestion in some posts tried to set spark.driver.maxResultSize to 20g , some blogs says to put inferSchema option ) but getting the same error again and again . The file size I am trying to read is 12kb .

I tried with below runtime versions in my databricks cluster

11.3 LTS (includes Apache Spark 3.3.0, Scala 2.12)

11.1 (includes Apache Spark 3.3.0, Scala 2.12)

10.4 LTS (includes Apache Spark 3.2.1, Scala 2.12)

Can anyone please advise how to overcome this issue ?

Re: Error reading in Parquet file

anpa — Sat, 14 Jan 2023 18:59:55 GMT

This error may be related to credential issue.

You can try this code

spark.conf.set("fs.azure.account.auth.type.<storage-account-name>.dfs.core.windows.net", "<your-access-key>")
spark.read.parquet("abfss://............/..._2023-01-14T08:01:29.8549884Z.parquet")

To hide <your-access-key> you can create Secret scopes follow the instructions link below:

Link to create Secret scopes.

Re: Error reading in Parquet file

BL — Sat, 14 Jan 2023 21:44:21 GMT

Thanks for your answer .

But I was using same kind of code with access key

Re: Error reading in Parquet file

BL — Sat, 14 Jan 2023 21:54:36 GMT

I tried again , but the same error

spark.conf.set("fs.azure.account.key.<ContainerName>.dfs.core.windows.net",ACCESS_KEY)

spark.read.parquet("abfss://............/..._2023-01-14T08:01:29.8549884Z.parquet")

Re: Error reading in Parquet file

jose_gonzalez — Mon, 30 Jan 2023 22:51:18 GMT

Can you access the executor logs? When you cluster is up and running, you can access the executor's logs. For example, the error shows:

Go to the Executor 0 and check why it failed