Open coreycradduck opened 10 months ago
Hey @coreycradduck ! Thanks for reaching out. We've captured this for review. 🚀
Hey @coreycradduck by any chance did you find a solution? I have the exact same situation :'(
any updates on this issue, we are facing this issue in MWAA environment and cannot be handled since dags folder is readonly here.
We are also experiencing the same issue in the MWAA environment as we updated Great Expectations to 0.18.1 from 0.15.30. It appears there have been other fixes to ensure functionality in a read-only environment (https://github.com/great-expectations/great_expectations/pull/8362) - @alexsherstinsky ? This current issue is specific to data_docs_custom_styles.css
. Like the original post, this appears to be the line of code causing the problem: https://github.com/great-expectations/great_expectations/blob/61901f68cc0b679dcc57d51182ac0b041d4c98d5/great_expectations/data_context/data_context/serializable_data_context.py#L342
Has anyone found a fix or are there any updates?
Just a workaround that we identified
The issue here is that the ge_context_root_dir is having strict permission settings by root user . To override that,
Create a CustomGreatExpectation operator class on top of the existing GreatExpectationOperator. Add a pre_execute method to move the data from ge_context_root_dir to /tmp and use it as the new ge_context_root_dir while initialising the operator.
I know this is not a perfect solution, but just a workaround that we identified.
Hi! I've had the exact problem regarding trying to access great_expectations/plugins/custom_data_docs/styles/data_docs_custom_styles.css with read/write permissions on my Airflow application running on Kubernetes. I found no other solution other than downgrading the version to the one you suggested (0.16.3). Hope we see a solution soon.
When instantiating a FileDataContext in my Databricks workflow, I receive an OSError due to some scaffolding attempts. GX is trying to access/modify great_expectations/plugins/custom_data_docs/styles/data_docs_custom_styles.css, which already exists, and because it's running from a specific Git commit rather than from the repo, it's having an issue modifying the file. I had these errors also for custom_data_docs/renderers, views, etc. until I created .gitkeep files so the data_context wouldn't try to set up empty directories. If I run the .py file directly in Databricks using the repository, there is no issue, so it's most likely tied to the attempt by GX to access the specific commit.
When I pin version 0.16.3, I don't have this issue, so I'm not sure what change caused this and if there's an option to disable this automatic data docs scaffolding.
To Reproduce
Expected behavior No error is raised.
Environment (please complete the following information):