GalaxyCDC is a core component of PolarDB-X which is responsible for global binary log generation, publication and subscription.

Last update: Dec 19, 2022

Overview

What is ApsaraDB GalaxyCDC ?

GalaxyCDC is a core component of PolarDB-X which is responsible for global binary log generation, publication and subscription.

With GalaxyCDC, PolarDB-X database can provide binary log fully compatible with MySQL binary log, which can be consumed seamlessly by MySQL binary log tools. And it can play the role of MySQL slave through MySQL Replication protocol.

Quick Start

The GalaxyCDC is a builtin component of the PolarDB-X.

Try GalaxyCDC by following these steps:

Start a PolarDB-X

See Quick Start to start a PolarDB-X.

Try MySQL Binary Log Commands

PolarDB-X is fully compatible with MySQL binary log related commands, such as SHOW BINARY LOGS, SHOW BINLOG EVENTS, etc. All commands can be found in the official MySQL documentation.

PolarDB-X as MySQL Slave

PolarDB-X supports MySQL Replica related commands, such as CHANGE MASTER TO，START/STOP/RESET SLAVE，SHOW SLAVE STATUS, etc. you can use PolarDB-X as MySQL slave, refer to Replica Reference Manual for command details.

See more docs about PolarDB-X.

License

ApsaraDB GalaxyCDC is under Apache License 2.0, see the license for details.

Contributing

See how to contribute.

Manages server status and gives log of status information. front end - angular js, backend- sbring boot, DB-MySQL

ServerManagerApplication / | | / | | ( ___ _ __ __ __ ___ _ __ | \ / | __ _ _ __ __ _ __ _ ___ _ __ __ \ / _ \ | '| \ \ / / / _ \ | '| | |/| | / | | '

Jan 6, 2022

A React Native project starter with Typescript, a theme provider with hook to easy styling component, a folder architecture ready and some configs to keep a codebase clean.

React Native Boilerplate Folder structure : src ├── assets │ ├── audios │ ├── fonts │ ├── icons │ └── images ├── components │ ├── Layout.tsx

Sep 1, 2022

Comments

show slave status报io exception

cdc版本用的是lastest，由于镜像版本和galaxycdc版本对应关系没找到，所以不知道lastest是哪个版本. mysql> show slave status\G ERROR 3009 (HY000): [14a1336302402000][10.42.7.85:3306][rpl]UNAVAILABLE: io exception 集群运行状态正常: [root@localhost polardb-x]# kubectl get pods NAME READY STATUS RESTARTS AGE pxtest-29nk-cdc-half-6f6664c556-nz8b8 2/2 Running 0 26m pxtest-29nk-cn-zone-a-67f46c7c86-jv5z5 3/3 Running 0 10m pxtest-29nk-dn-0-cands1-0 3/3 Running 0 6d1h pxtest-29nk-dn-0-cands2-0 3/3 Running 0 6d1h pxtest-29nk-dn-0-log-0 3/3 Running 0 6d1h pxtest-29nk-gms-cand-zone-a-0 3/3 Running 0 21m pxtest-29nk-gms-cand-zone-b-0 3/3 Running 0 20m pxtest-29nk-gms-log-zone-c-0 3/3 Running 0 19m

CDC错误日志:

ERROR 9001 (HY000) at line 534: [14a10a6ddf801000][10.42.9.50:3306][grafana]ERR-CODE: [PXC-9001][ERR_GMS_GENERIC] Identifier name '_local_UQE_library_element_connection_element_id_kind_connection_id' is too long (max = 64). 2022-07-20 17:51:14.863 [qtp300104620-42] INFO c.a.p.binlog.daemon.rest.RestServer - 127.0.0.1 - - [20/Jul/2022:09:51:14 +0000] "GET //127.0.0.1:3007/cdc/metrics HTTP/1.1" 200 6 9 2022-07-20 17:51:15.505 [TimerTask-NodeReport] ERROR c.a.p.b.task.AbstractBinlogTimerTask - exec timer task fail NodeReport 1000 org.springframework.jdbc.UncategorizedSQLException: ### Error updating database. Cause: java.sql.SQLException: The consensus follower is not allowed to to do current operation. ### The error may exist in com/aliyun/polardbx/binlog/dao/NodeInfoMapper.java (best guess) ### The error may involve com.aliyun.polardbx.binlog.dao.NodeInfoMapper.insert-Inline ### The error occurred while setting parameters ### SQL: insert into binlog_node_info (gmt_created, gmt_modified, cluster_id, container_id, ip, daemon_port, available_ports, status, core, mem, gmt_heartbeat, role, cluster_type) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) ### Cause: java.sql.SQLException: The consensus follower is not allowed to to do current operation. ; uncategorized SQLException for SQL []; SQL state [HY000]; error code [3934]; The consensus follower is not allowed to to do current operation.; nested exception is java.sql.SQLException: The consensus follower is not allowed to to do current operation. at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:84) at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:81) at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:81) at org.mybatis.spring.MyBatisExceptionTranslator.translateExceptionIfPossible(MyBatisExceptionTranslator.java:88) at org.mybatis.spring.SqlSessionTemplate$SqlSessionInterceptor.invoke(SqlSessionTemplate.java:440) at com.sun.proxy.$Proxy17.insert(Unknown Source) at org.mybatis.spring.SqlSessionTemplate.insert(SqlSessionTemplate.java:271) at org.apache.ibatis.binding.MapperMethod.execute(MapperMethod.java:62) at org.apache.ibatis.binding.MapperProxy$PlainMethodInvoker.invoke(MapperProxy.java:152) at org.apache.ibatis.binding.MapperProxy.invoke(MapperProxy.java:85) at com.sun.proxy.$Proxy31.insert(Unknown Source) at org.mybatis.dynamic.sql.util.mybatis3.MyBatis3Utils.insert(MyBatis3Utils.java:93) at com.aliyun.polardbx.binlog.dao.NodeInfoMapper.insertSelective(NodeInfoMapper.java:212) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.apache.ibatis.binding.MapperProxy$DefaultMethodInvoker.invoke(MapperProxy.java:166) at org.apache.ibatis.binding.MapperProxy.invoke(MapperProxy.java:85) at com.sun.proxy.$Proxy31.insertSelective(Unknown Source) at com.aliyun.polardbx.binlog.daemon.schedule.NodeReporter.exec(NodeReporter.java:90) at com.aliyun.polardbx.binlog.task.AbstractBinlogTimerTask$1.run(AbstractBinlogTimerTask.java:55) at java.util.TimerThread.mainLoop(Timer.java:555) at java.util.TimerThread.run(Timer.java:505) Caused by: java.sql.SQLException: The consensus follower is not allowed to to do current operation. at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:965) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3933) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3869) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2524) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2675) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2465) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1915) at com.mysql.jdbc.PreparedStatement.execute(PreparedStatement.java:1254) at sun.reflect.GeneratedMethodAccessor27.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.tomcat.jdbc.pool.StatementFacade$StatementProxy.invoke(StatementFacade.java:114) at com.sun.proxy.$Proxy30.execute(Unknown Source) at org.apache.ibatis.executor.statement.PreparedStatementHandler.update(PreparedStatementHandler.java:47) at org.apache.ibatis.executor.statement.RoutingStatementHandler.update(RoutingStatementHandler.java:74) at org.apache.ibatis.executor.ReuseExecutor.doUpdate(ReuseExecutor.java:52) at org.apache.ibatis.executor.BaseExecutor.update(BaseExecutor.java:117) at org.apache.ibatis.executor.CachingExecutor.update(CachingExecutor.java:76) at org.apache.ibatis.session.defaults.DefaultSqlSession.update(DefaultSqlSession.java:197) at org.apache.ibatis.session.defaults.DefaultSqlSession.insert(DefaultSqlSession.java:184) at sun.reflect.GeneratedMethodAccessor55.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.mybatis.spring.SqlSessionTemplate$SqlSessionInterceptor.invoke(SqlSessionTemplate.java:426) ... 16 common frames omitted 2022-07-20 17:51:16.501 [TimerTask-NodeReport] ERROR c.a.p.b.task.AbstractBinlogTimerTask - exec timer task fail NodeReport 1000 org.springframework.jdbc.UncategorizedSQLException: ### Error updating database. Cause: java.sql.SQLException: The consensus follower is not allowed to to do current operation. ### The error may exist in com/aliyun/polardbx/binlog/dao/NodeInfoMapper.java (best guess) ### The error may involve com.aliyun.polardbx.binlog.dao.NodeInfoMapper.insert-Inline ### The error occurred while setting parameters ### SQL: insert into binlog_node_info (gmt_created, gmt_modified, cluster_id, container_id, ip, daemon_port, available_ports, status, core, mem, gmt_heartbeat, role, cluster_type) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) ### Cause: java.sql.SQLException: The consensus follower is not allowed to to do current operation. ; uncategorized SQLException for SQL []; SQL state [HY000]; error code [3934]; The consensus follower is not allowed to to do current operation.; nested exception is java.sql.SQLException: The consensus follower is not allowed to to do current operation. at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:84) at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:81) at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:81) at org.mybatis.spring.MyBatisExceptionTranslator.translateExceptionIfPossible(MyBatisExceptionTranslator.java:88) at org.mybatis.spring.SqlSessionTemplate$SqlSessionInterceptor.invoke(SqlSessionTemplate.java:440) at com.sun.proxy.$Proxy17.insert(Unknown Source) at org.mybatis.spring.SqlSessionTemplate.insert(SqlSessionTemplate.java:271) at org.apache.ibatis.binding.MapperMethod.execute(MapperMethod.java:62) at org.apache.ibatis.binding.MapperProxy$PlainMethodInvoker.invoke(MapperProxy.java:152) at org.apache.ibatis.binding.MapperProxy.invoke(MapperProxy.java:85) at com.sun.proxy.$Proxy31.insert(Unknown Source) at org.mybatis.dynamic.sql.util.mybatis3.MyBatis3Utils.insert(MyBatis3Utils.java:93) at com.aliyun.polardbx.binlog.dao.NodeInfoMapper.insertSelective(NodeInfoMapper.java:212) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.apache.ibatis.binding.MapperProxy$DefaultMethodInvoker.invoke(MapperProxy.java:166) at org.apache.ibatis.binding.MapperProxy.invoke(MapperProxy.java:85) at com.sun.proxy.$Proxy31.insertSelective(Unknown Source) at com.aliyun.polardbx.binlog.daemon.schedule.NodeReporter.exec(NodeReporter.java:90) at com.aliyun.polardbx.binlog.task.AbstractBinlogTimerTask$1.run(AbstractBinlogTimerTask.java:55) at java.util.TimerThread.mainLoop(Timer.java:555) at java.util.TimerThread.run(Timer.java:505) Caused by: java.sql.SQLException: The consensus follower is not allowed to to do current operation. at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:965) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3933) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3869) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2524) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2675) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2465) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1915) at com.mysql.jdbc.PreparedStatement.execute(PreparedStatement.java:1254) at sun.reflect.GeneratedMethodAccessor27.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.tomcat.jdbc.pool.StatementFacade$StatementProxy.invoke(StatementFacade.java:114) at com.sun.proxy.$Proxy30.execute(Unknown Source) at org.apache.ibatis.executor.statement.PreparedStatementHandler.update(PreparedStatementHandler.java:47) at org.apache.ibatis.executor.statement.RoutingStatementHandler.update(RoutingStatementHandler.java:74) at org.apache.ibatis.executor.ReuseExecutor.doUpdate(ReuseExecutor.java:52) at org.apache.ibatis.executor.BaseExecutor.update(BaseExecutor.java:117) at org.apache.ibatis.executor.CachingExecutor.update(CachingExecutor.java:76) at org.apache.ibatis.session.defaults.DefaultSqlSession.update(DefaultSqlSession.java:197) at org.apache.ibatis.session.defaults.DefaultSqlSession.insert(DefaultSqlSession.java:184) at sun.reflect.GeneratedMethodAccessor55.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.mybatis.spring.SqlSessionTemplate$SqlSessionInterceptor.invoke(SqlSessionTemplate.java:426) ... 16 common frames omitted

opened by welyss 4
java11 中提示少依赖包

polardbx-cdc-backup/src/main/java/com/aliyun/polardbx/binlog/download/RdsApi.java import javax.xml.bind.DatatypeConverter; java11 中提示少依赖包

JAXB API是java EE 的API，在java SE 9.0 中不再包含这个 Jar 包 jar包中缺少这一依赖-javax.xml.bind.api

opened by co63oc 0
BASE64Encoder 不支持java11

polardbx-cdc-daemon/src/main/java/com/aliyun/polardbx/binlog/daemon/rest/signature/Signature.java

文件中使用 import sun.misc.BASE64Encoder; 不支持java 11

java 11使用 import java.util.Base64;

opened by co63oc 0
5.4.12版本迭代，bugfix修复 & 优化 & 新feature
修复：日志清理脚本只能清除当前最新日志，无法清除历史日志问题

修复：针对中文库表名称，因解析乱码导致库表数据被过滤，引发数据丢失问题

修复：收到ScaleOut/In打标指令后，如果指令前后storge列表并未发生变化，无法触发集群重新调度引发数据链路卡住的问题

修复：当表名当中含有反引号时，polardbx-meta-cdc模块解析失效，导致触发语法错误，引发数据链路中断

修复：针对drop database和drop table sql，meta模块未对拓扑信息进行remove，造成内存泄漏或脏数据问题

优化：针对polardb-x私有ddl sql的处理进行专项优化，remove掉私有语法，提升和mysql生态的兼容性

优化：支持可动态修改记录到全局Binlog中的心跳事件的频率

新增：支持集群调度功能可暂停

新增：支持通过traceid记录server_id，支持实例间双向同步时的循环同步问题

新增：适配polardb-x instant add column特性，保证当逻辑表和物理表列序不一致时，binlog内容的正确性

新增：适配新版DN记录TSO的方式(独立的GCN Event记录)

enhancement
opened by lulu2panpan 0

Releases(galaxycdc-5.4.15)

galaxycdc-5.4.15(Nov 3, 2022)

see v5.4.15-alpha
Source code(tar.gz)
Source code(zip)
galaxycdc-5.4.15-alpha(Oct 26, 2022)
RELEASE NOTE

Important New Feature

Add backup capability：global binlog files can be uploaded to OSS in real time and restored to local from OSS for recovery

Greatly improved performance：the maximum EPS capacity is increased from 100w/s to 200w/s, and the maximum write throughput capacity is increased from 250M/s to 500M/s

Feature enhancement

Add built-in automatic cleaning capability：binlog file on the local disk can be automatically cleared periodically when the total file size exceeds a specified threshold

Reduced memory usage by 40%：all kinds of optimization such as Metadata persistence, buffer size optimization, memory/disk swap policy optimization, and serialization/deserialization optimization

More Strong data consistency: During DDL changes, the data reformat module supports reformating the data type and precision of binlog events

New historical record clearing capability: Supports periodic clearing of ddl marking information and cluster scheduling history information

Optimized log clearing policy: Optimized the clearing policy for the memory dump files (*.hprof) to reduce the threshold of the number of reserved files and avoid the risk of disk explosion

Optimized the health checking policy for cdc processes: Change the health checking method from the 'jps' command to 'ps -ef' to solve the host cpu jitter problem caused by jps in high load scenarios

Optimized CDC recovery policy: fix the issue that When a 2PC transaction spans multiple DN binlog files during recovery, data loss may occur in extreme cases

Add hot effect capability for parameters: automatically scans the binlog_system_config configuration table and config.properties file, and automatically resets memory parameter values

Optimized performance for binlog data filtering : optimize the TxnBuffer data structure to solve the performance bottleneck caused by the high-frequency remove operation on the refList

Added blacklist configuration for database/table: supports filtering the data for some database or table which configured in the blacklist

发布说明

重要功能新增

新增binlog备份恢复能力：binlog文件可实时上传至OSS、以及从OSS恢复到本地

同步性能大幅提升：最大EPS能力从100w/s提升至200w/s，最大写入吞吐能力从250M/s提升至500M/s

特性更新

新增binlog自动清理能力：本地磁盘binlog文件大小超过指定阈值，支持可定时自动清理

内存占用降低40%：支持对元数据进行持久化、缓冲区大小优化、内存/磁盘swap策略优化、序列化/反序列化优化等

更高数据一致性保证：DDL变更过程中，数据整形模块新增支持对binlog event的数据类型和精度进行整形

新增历史记录清理能力：支持对ddl打标信息、集群调度历史信息等进行定时清理

日志清理策略优化：内存dump文件(*.hprof)清理策略优化，降低保留文件个数阈值，规避磁盘打爆风险

进程探活定时任务优化：进程探活方式，由jps命令调整为ps -ef，解决高负载场景下，因jps导致宿主机cpu抖动问题

CDC Recovery策略优化：解决在链路恢复过程中，当某个2PC事务跨多个DN binlog文件时，极端情况下可能导致的数据丢失问题

新增参数热生效能力：自动扫描binlog_system_config配置表和 config.properties文件，自动reset内存参数值

binlog数据过滤性能优化：优化TxnBuffer数据结构，解决因对refList进行高频remove操作导致的性能瓶颈问题

新增库表黑名单能力：全局binlog中支持针对指定库表的数据进行过滤

Source code(tar.gz)
Source code(zip)
galaxycdc-5.4.13(Mar 30, 2022)
RELEASE NOTE

Important New Feature

Introduce new component named Replica which can simulate PolarDB-X as mysql slave by use sql like ‘change master …’

Support recording Rows_query_event in Global Binlog with a precondition that should set binlog_rows_query_log_events to ON in DN Nodes

Feature enhancement

Optimize algorithm for TableMapId Generation to guarantee consistent ID for same table

Optimize algorithm with rollback for CDC meta information to resolve possible inconsistency issue in extremely scene，and introduce consistency checking module for meta

Support Skip Selection for disordered TraceId with a new configuration parameter

Add parameterization support whether record implicit primary key to Global Binlog

support utf8mb3 character encoding

support special processing for rotate event which existed in middle of DN binlog file

Bugfix

Fix truncation issue for TableMapId because of incorrect data type usage

Remove two StatusVars in Query Event(MODE_NO_ZERO_IN_DATE和MODE_NO_ZERO_DATE) to resolve program error in mysql slave when processing null timestamp columns

Fix Invalid Checking for Heartbeat Window integrity in LogEventMerger when meet Scale Out/In

Fix Type defination defect of FastSql Repository , which resulting in metadata overwritten with each other between Tables and Indexes with the same name

Fix file size issue in binlog_oss_reocrd table

Fix some bugs of rule mismatching because of missing process for back quote

发布说明

重要功能新增

新增Replica组件，支持通过change master … 语法的方式将PolarDB-X作为MySQL Slave来消费数据

全局Binlog中支持记录Rows_query_event类型数据，前置条件：需将DN节点binlog_rows_query_log_events参数设置为On

特性更新

优化TableMapId生成算法，保证相同逻辑表ID一致

优化CDC元数据Rollback算法，解决极端情况下元数据不一致问题，并引入元数据一致性校验算法

针对乱序的TraceId，支持参数化配置是否进行跳过

支持参数化配置，是否记录PolarDB-X隐藏主键到全局Binlog

支持utf8mb3字符编码

支持对DN binlog文件中间位置出现的rotate event进行特殊处理

问题修复

修复因数据类型精度不够导致TableMapId被截断问题

删除QueryEvent中的两个状态变量MODE_NO_ZERO_IN_DATE和MODE_NO_ZERO_DATE，解决Timstamp Column值为空时同步到下游MySQL报错问题

解决Scale Out/In场景下，LogEventMerger心跳窗口完整性检测失效问题

修复FastSql Repository类型区分不够精细，导致具有相同名字的Table和Index的元数据相互覆盖问题

修复记录到binlog_oss_record表中的Binlog文件大小错误问题

修复若干因反引号导致的规则匹配失效问题

Source code(tar.gz)
Source code(zip)
galaxycdc-5.4.12(Jan 30, 2022)
RELEASE NOTE

Feature enhancement

Improve DDL compatibility with MySQL

supports reset the frequency of heartbeat events recorded to binlog

Support suspending for cluster schedule

Support record server_id into trace_id for breaking circulation in bidirectional synchronization

Support instant add column feature by resolving different column order between logic schema and physical schema

Support GCN event for recording tso

Bugfix

Fix the failure of log cleanup

Fix data loss issue when table name contains Chinese characters

Fix possible blocking in scale-out or scale-in

Fix sql parse failure when sql statement contains backquote

Fix dirty metadata issue when received drop database sql and drop table sql

发布说明

特性更新

针对polardb-x私有ddl sql的处理进行专项优化，remove掉私有语法，提升和mysql生态的兼容性

支持可动态修改记录到全局Binlog中的心跳事件的频率

支持集群调度功能可暂停

支持通过traceid记录server_id，支持实例间双向同步时的循环同步问题

适配polardb-x instant add column特性，保证当逻辑表和物理表列序不一致时，binlog内容的正确性

适配新版DN记录TSO的方式(独立的GCN Event记录)

问题修复

日志清理脚本只能清除当前最新日志，无法清除历史日志问题

针对中文库表名称，因解析乱码导致库表数据被过滤，引发数据丢失问题

收到ScaleOut/In打标指令后，如果指令前后storge列表并未发生变化，无法触发集群重新调度引发数据链路卡住的问题

当表名当中含有反引号时，polardbx-meta-cdc模块解析失效，导致触发语法错误，引发数据链路中断

针对drop database和drop table sql，meta模块未对拓扑信息进行remove，造成内存泄漏或脏数据问题

Source code(tar.gz)
Source code(zip)

GalaxyCDC is a core component of PolarDB-X which is responsible for global binary log generation, publication and subscription.

Related tags

Overview

What is ApsaraDB GalaxyCDC ?

Quick Start

License

Contributing

You might also like...

Comments

Releases(galaxycdc-5.4.15)

galaxycdc-5.4.15(Nov 3, 2022)

galaxycdc-5.4.15-alpha(Oct 26, 2022)

RELEASE NOTE

Important New Feature

Feature enhancement

发布说明

重要功能新增

特性更新

galaxycdc-5.4.13(Mar 30, 2022)

RELEASE NOTE

Important New Feature

Feature enhancement

Bugfix

发布说明

重要功能新增

特性更新

问题修复

galaxycdc-5.4.12(Jan 30, 2022)

RELEASE NOTE

Feature enhancement

Bugfix

发布说明

特性更新

问题修复

Owner

Java-Trading-Log-Project - A Trading Log to Journal Your Trades.

Sceneform React Native AR Component using ARCore and Google Filament as 3D engine. This the Sceneform Maintained Component for React Native

PolarDB-X is a cloud native distributed SQL Database designed for high concurrency, massive storage, complex querying scenarios.

OpenAPI Generator allows generation of API client libraries (SDK generation), server stubs, documentation and configuration automatically given an OpenAPI Spec (v2, v3)

Daily mail subscription implementation using Java Spring-boot and Quartz Scheduler

tuya-spring-boot-starter helps you efficiently create cloud development projects regarding the OpenAPI or message subscription capabilities. You can put all the focus on business logic without taking care of server-side programming nor relational databases.

Velocity global chat/discord bridge

Fabric mod to (maybe) ignore global bans while still using the auth server

Minecraft configurable plugin , which sends messages the first time a player logs into the server or the next time they log in.

trying to create a plugin using the spigot api! this plugin will be responsible for delivering the products according to the settings!