You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by "github-actions[bot] (via GitHub)" <gi...@apache.org> on 2023/07/03 03:07:43 UTC
[GitHub] [dolphinscheduler] github-actions[bot] commented on issue #14436: [Bug] [data-quality] After the 3.1.x version of the data quality rule type "custom SQL" node is successfully executed, the page status is displayed as "executing" and cannot end.
github-actions[bot] commented on issue #14436:
URL: https://github.com/apache/dolphinscheduler/issues/14436#issuecomment-1617154510
### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
1. Create a data quality rule type as "Custom SQL" node.
2. The configuration is as follows:
3. Check the node log and find that the node runs successfully and ends
4. The page node shows that it is running and cannot be ended.
### What you expected to happen
1. Test version, 3.1.1 and 3.1.7
2. Create a data quality rule type as "Custom SQL" node:
Data source: mysql
Source data table: xxxxxx (task a mysql table)
Actual value name: len
Actual value calculation SQL: select LENGTH (any field) AS len from ${src_table}
Verification method: Actual - Expected
Validation operator: >
Threshold: 0
Failure Policy: Alert
Expected value type: FixValue
fixed value 0
### How to reproduce
none
### Anything else
_No response_
### Version
3.1.x
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org