You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Profiling jobs failing with ImportError: cannot import name 'ColumnProfilerRunner' from 'awsglue.transforms' (/opt/amazon/lib/python3.6/site-packages/awsglue/transforms/__init__.py)
#1216
When running a profiling job from data.all on a table the glue job fails. In the AWS Console we see the error: ImportError: cannot import name 'ColumnProfilerRunner' from 'awsglue.transforms' (/opt/amazon/lib/python3.6/site-packages/awsglue/transforms/__init__.py)
How to Reproduce
Click on run profiling job on a table
verify errors in AWS Console Glue
Expected behavior
Profiling jobs works smoothly and succeeds
Your project
No response
Screenshots
No response
OS
n/a
Python version
n/a
AWS data.all version
2.3+additional PRs
Additional context
No response
The text was updated successfully, but these errors were encountered:
### Feature or Bugfix
<!-- please choose -->
- Bugfix
### Detail
- ColumnProfilerRunner must be imported from pydeequ.profiles
- Workaround about missing SPARK_VERSION
### Relates
- #1216
### Security
Please answer the questions below briefly where applicable, or write
`N/A`. Based on
[OWASP 10](https://owasp.org/Top10/en/).
- Does this PR introduce or modify any input fields or queries - this
includes
fetching data from storage outside the application (e.g. a database, an
S3 bucket)?
- Is the input sanitized?
- What precautions are you taking before deserializing the data you
consume?
- Is injection prevented by parametrizing queries?
- Have you ensured no `eval` or similar functions are used?
- Does this PR introduce any functionality or component that requires
authorization?
- How have you ensured it respects the existing AuthN/AuthZ mechanisms?
- Are you logging failed auth attempts?
- Are you using or adding any cryptographic features?
- Do you use a standard proven implementations?
- Are the used keys controlled by the customer? Where are they stored?
- Are you introducing any new policies/roles/users?
- Have you used the least-privilege principle? How?
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 license.
Co-authored-by: Sofia Sazonova <sazonova@amazon.co.uk>
Describe the bug
When running a profiling job from data.all on a table the glue job fails. In the AWS Console we see the error:
ImportError: cannot import name 'ColumnProfilerRunner' from 'awsglue.transforms' (/opt/amazon/lib/python3.6/site-packages/awsglue/transforms/__init__.py)
How to Reproduce
Expected behavior
Profiling jobs works smoothly and succeeds
Your project
No response
Screenshots
No response
OS
n/a
Python version
n/a
AWS data.all version
2.3+additional PRs
Additional context
No response
The text was updated successfully, but these errors were encountered: