apache/dolphinschedulerGitHubLast refreshed Oct 3, 2026
This is a public, read-only report. Striff reads this repository's docs, turns each sentence that makes a claim about the code into a rule, and checks the rule against the code on the default branch. How this works
Names these docs write that the code no longer has3
Each sentence below names a type the default branch doesn't declare, or declares somewhere else. Edit the doc so it matches the code, or bring the type back.
DataSourceProcessor, AbstractDataSourceProcessor, BaseDataSourceParamDTO, BaseHdfsConnectionParam, and the DataSourcePluginManager that loads plugins.
Renamed: BaseHdfsConnectionParam is now BaseHDFSConnectionParam, at dolphinscheduler-datasource-plugin/dolphinscheduler-datasource-api/src/main/java/org/apache/dolphinscheduler/plugin/datasource/api/datasource/BaseHDFSConnectionParam.java. Renamed in 7e0010d
In additional, the AlertChannelFactory extends from PrioritySPI, this means you can set the plugin priority, when you have two plugin has the same name, you can customize the priority by override the getIdentify method.
AlertChannelFactory extends PrioritySPI
Holds
Read Oct 3
AlertChannel The interface of the alert plug-in. The alert plug-in needs to implement this interface. There is only one method process in this interface.
AlertChannel has a process method
Holds
Read Oct 3
AlertData Alarm content information, including id, title, content, log.
AlertData has id
Holds
Read Oct 3
AlertData Alarm content information, including id, title, content, log.
AlertData has title
Holds
Read Oct 3
AlertData Alarm content information, including id, title, content, log.
AlertData has content
Holds
Read Oct 3
AlertData Alarm content information, including id, title, content, log.
AlertData has log
Holds
Read Oct 3
AlertInfo For alarm-related information, when the upper-level system calls an instance of the alarm plug-in, the instance of this class is passed to the specific alarm plug-in through the process method. It contains the alert content AlertData and the parameter information filled in by the front end of the called alert plug-in instance.
PhysicalTaskExecutorFactory builds a PhysicalTaskExecutor (lives in task-executor) around the task plugin (from task-plugin).
PhysicalTaskExecutorFactory depends on PhysicalTaskExecutor
Holds
46 rules from 10 docs
See these where the change is. The browser extension puts a pull request's doc findings, and a diagram of what it changed, on the GitHub page itself, so the code and what your docs say about it are side by side.
