1개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
1
That's a fair point about clarifying the documentation, the history is based on the historical metric, if the rule wasn't applied then the metric wasn't created, the rule cannot backprocess the data to calculate the previous history if the rule wasn't applied.
HI can you please see if you have any thoughts on this question ?https://repost.aws/questions/QU88DiiUZ1STmIjySismV2Ow/how-does-aws-glue-data-quality-custom-sql-work-with-no-unique-column
관련 콘텐츠
AWS 공식업데이트됨 3년 전- AWS 공식업데이트됨 일 년 전
- AWS 공식업데이트됨 3년 전
- AWS 공식업데이트됨 3년 전
Yep, it sounds it thinks the average is 100, not sure why. What did it say on the previous evaluations?
How did you make it process different files on different runs?, do you have any count that the job actually read them all? (maybe it has thrown away invalid rows)
This worked on 5th time. I think the issue is, in my first 3 runs this rule was not there. I added this rule in 4th run only. So it didnt took earlier runs into consideration. But this thing is not mentioned anywhere in documentation. There is no mention how Glue stores 'state' of runs.