By continuing you indicate that you have read and agree to our Terms of service and Privacy policy
incubator-dolphinscheduler | Apache DolphinScheduler | BPM library
kandi X-RAY | incubator-dolphinscheduler Summary
Support
- incubator-dolphinscheduler has a medium active ecosystem.
- It has 5281 star(s) with 1854 fork(s). There are 264 watchers for this library.
- It had no major release in the last 12 months.
- There are 541 open issues and 1785 have been closed. On average issues are closed in 18 days. There are 35 open pull requests and 0 closed requests.
- It has a neutral sentiment in the developer community.
- The latest version of incubator-dolphinscheduler is 1.3.5
Quality
- incubator-dolphinscheduler has 0 bugs and 0 code smells.
Security
- incubator-dolphinscheduler has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
- incubator-dolphinscheduler code analysis shows 0 unresolved vulnerabilities.
- There are 0 security hotspots that need review.
License
- incubator-dolphinscheduler is licensed under the Apache-2.0 License. This license is Permissive.
- Permissive licenses have the least restrictions, and you can use them in most projects.
Reuse
- incubator-dolphinscheduler releases are available to install and integrate.
- Deployable package is available in Maven.
- Build file is available. You can build the component from source.
- Installation instructions are not available. Examples and code snippets are available.
- incubator-dolphinscheduler saves you 59056 person hours of effort in developing the same functionality from scratch.
- It has 67674 lines of code, 5320 functions and 1077 files.
- It has medium code complexity. Code complexity directly impacts maintainability of the code.
Coming Soon for all Libraries!
Currently covering the most popular Java, JavaScript and Python libraries. See a SAMPLE HERE.
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
incubator-dolphinscheduler Key Features
Associate the tasks according to the dependencies of the tasks in a DAG graph, which can visualize the running state of the task in real-time.
Support various task types: Shell, MR, Spark, SQL (MySQL, PostgreSQL, hive, spark SQL), Python, Sub_Process, Procedure, etc.
Support scheduling of workflows and dependencies, manual scheduling to pause/stop/recover task, support failure task retry/alarm, recover specified nodes from failure, kill task, etc.
Support the priority of workflows & tasks, task failover, and task timeout alarm or failure.
Support workflow global parameters and node customized parameter settings.
Support online upload/download/management of resource files, etc. Support online file creation and editing.
Support task log online viewing and scrolling and downloading, etc.
Have implemented cluster HA, decentralize Master cluster and Worker cluster through Zookeeper.
Support the viewing of Master/Worker CPU load, memory, and CPU usage metrics.
Support displaying workflow history in tree/Gantt chart, as well as statistical analysis on the task status & process status in each workflow.
Support back-filling data.
Support multi-tenant.
Support internationalization.
More features waiting for partners to explore…​
Submit an [issue](https://github.com/apache/incubator-dolphinscheduler/issues/new/choose)
Subscribe to this mailing list: https://dolphinscheduler.apache.org/en-us/community/development/subscribe.html, then email dev@dolphinscheduler.apache.org
incubator-dolphinscheduler Examples and Code Snippets
default
Stability | Accessibility | Features | Scalability |
-- | -- | -- | --
Decentralized multi-master and multi-worker | Visualization of workflow key information, such as task status, task type, retry times, task operation machine information, visual variables, and so on at a glance. | Support pause, recover operation | Support customized task types
support HA | Visualization of all workflow operations, dragging tasks to draw DAGs, configuring data sources and resources. At the same time, for third-party systems, provide API mode operations. | Users on DolphinScheduler can achieve many-to-one or one-to-one mapping relationship through tenants and Hadoop users, which is very important for scheduling large data jobs. | The scheduler supports distributed scheduling, and the overall scheduling capability will increase linearly with the scale of the cluster. Master and Worker support dynamic adjustment.
Overload processing: By using the task queue mechanism, the number of schedulable tasks on a single machine can be flexibly configured. Machine jam can be avoided with high tolerance to numbers of tasks cached in task queue. | One-click deployment | Support traditional shell tasks, and big data platform task scheduling: MR, Spark, SQL (MySQL, PostgreSQL, hive, spark SQL), Python, Procedure, Sub_Process | |Community Discussions
Trending Discussions on BPM
QUESTION
Camunda embedded with H2: Cockpit Login fails
Asked 2022-Mar-09 at 08:50I'm currently wokring on a product with the following conditions:
- Spring-Boot (2.6) with Camunda embedded (7.16)
- Connection to Camunda configured to use H2 (2.1.210) embedded with the following is configured in application.yml:
app:
datasource-camunda:
jdbcUrl: jdbc:h2:./h2/test;MODE=LEGACY
camunda:
bpm:
database:
schema-update: true
auto-deployment-enabled: true
and as Java-Configuration:
@Bean("camundaBpmDataSource")
@ConfigurationProperties
public DataSource camundaDataSource() {
return DataSourceBuilder.create().build();
}
@Bean
public PlatformTransactionManager camundaBpmTransactionManager(DataSource datasource) {
return new DataSourceTransactionManager(datasource)
}
The camunda engine is not configured explicitly since I used the appropriate starter and let Spring auto configured it. As a result the resulting setup should look very similar to the embedded camunda h2 configuration showed here: https://docs.camunda.org/get-started/spring/embedded-process-engine/
The application runs good with this setup. No problems with the application at all, but I faced an issue while logging in to the camunda cockpit. Login succeeds but then I see an error in the login mask saying:
Login Failed
An exception occured in the persistence layer. Please check the server logs for a detailed message and the entire exception stack trace
Caused by: org.h2.jdbc.JdbcSQLNonTransientException: Unbekannter Datentyp: "?2"
Unknown data type: "?2"; SQL statement:
SELECT
CASE
WHEN
EXISTS
(SELECT
A.RESOURCE_ID_
FROM
ACT_RU_AUTHORIZATION A
WHERE
A.TYPE_ = 1
AND
A.USER_ID_ = ?
AND
BITAND(A.PERMS_,?) = ?
AND
A.RESOURCE_TYPE_ = ?
AND
A.RESOURCE_ID_ = ? )
THEN 1
WHEN
EXISTS
(SELECT
ID_
FROM
ACT_RU_AUTHORIZATION A
WHERE
A.TYPE_ = 1
AND
A.USER_ID_ = ?
AND
BITAND(A.PERMS_,?) = ?
AND
A.RESOURCE_TYPE_ = ?
AND
A.RESOURCE_ID_ = '*')
THEN 1
ELSE
(
SELECT
CASE
WHEN
EXISTS
(SELECT
A.RESOURCE_ID_
FROM
ACT_RU_AUTHORIZATION A
WHERE
A.TYPE_ = 1
AND
A.GROUP_ID_ IN ( ? )
AND
BITAND(A.PERMS_,?) = ?
AND
A.RESOURCE_TYPE_ = ?
AND
A.RESOURCE_ID_ = ? )
THEN 1
WHEN
EXISTS
(SELECT
ID_
FROM
ACT_RU_AUTHORIZATION A
WHERE
A.TYPE_ = 1
AND
A.GROUP_ID_ IN ( ? )
AND
BITAND(A.PERMS_,?) = ?
AND
A.RESOURCE_TYPE_ = ?
AND
A.RESOURCE_ID_ = '*')
THEN 1
ELSE (
SELECT
CASE
WHEN
EXISTS
(SELECT
A.RESOURCE_ID_
FROM
ACT_RU_AUTHORIZATION A
WHERE
A.TYPE_ = 0
AND
A.USER_ID_ = '*'
AND
BITAND(A.PERMS_,?) = ?
AND
A.RESOURCE_TYPE_ = ?
AND
A.RESOURCE_ID_ = ? )
THEN 1
WHEN
EXISTS
(SELECT
ID_
FROM
ACT_RU_AUTHORIZATION A
WHERE
A.TYPE_ = 0
AND
A.USER_ID_ = '*'
AND
BITAND(A.PERMS_,?) = ?
AND
A.RESOURCE_TYPE_ = ?
AND
A.RESOURCE_ID_ = '*')
THEN 1
ELSE
null
END
)
END
)
END [50004-210]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:573) ~[h2-2.1.210.jar:2.1.210]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:496) ~[h2-2.1.210.jar:2.1.210]
at org.h2.message.DbException.get(DbException.java:227) ~[h2-2.1.210.jar:2.1.210]
I already took a look into the database and saw all tables where created sucesfully, so does anybody faced a similar issue?
ANSWER
Answered 2022-Mar-09 at 08:50Remove the "MODE=LEGACY" from the url. Here is a working example:
Also ensure you use a supported H2 version. That is 1.4.x fro 7.16.x: https://docs.camunda.org/manual/7.16/introduction/supported-environments/
The BOM will inclcude H2 1.4.200.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install incubator-dolphinscheduler
You can use incubator-dolphinscheduler like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the incubator-dolphinscheduler component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .
Support
DOWNLOAD this Library from
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from
over 430 million Knowledge Items
Find more librariesReuse Solution Kits and Libraries Curated by Popular Use Cases
Save this library and start creating your kit
Explore Related Topics
Share this Page
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from
over 430 million Knowledge Items
Find more librariesReuse Solution Kits and Libraries Curated by Popular Use Cases
Save this library and start creating your kit