Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error Handling for Corrupt Files in Chunk Processing #840

Open
1 task done
toandaominh1997 opened this issue Mar 19, 2024 · 1 comment
Open
1 task done

Error Handling for Corrupt Files in Chunk Processing #840

toandaominh1997 opened this issue Mar 19, 2024 · 1 comment

Comments

@toandaominh1997
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

I am using the spark-excel library to read Excel files in chunks from a directory. My process involves reading multiple Excel files and then performing operations on the data. However, I've encountered an issue where if any of the files are corrupt or cause an error during reading, the entire processing job fails and does not skip the problematic file.

Expected Behavior

I would expect the library to provide a mechanism to skip over files that cause errors during the read operation, allowing the process to continue with the next files in the list.

Steps To Reproduce

Set up a Spark session and configure it to read Excel files using spark-excel.
Use a loop to read files in chunks from a specified directory.
If an error occurs while reading a file (e.g., due to corruption or format issues), the process stops, and subsequent files are not processed.

Environment

- Spark version: 3.4.1
- Spark-Excel version: 0.20.3
- OS: Linux
- Cluster environment: Databricks

Anything else?

No response

@nightscape
Copy link
Owner

Could you post an excerpt of your code?
This part sounds like you're looping over the files yourself:

Use a loop to read files in chunks from a specified directory.

If so, then it is under your control to catch any exceptions thrown during reading.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants