con un clic
DBClient
DBClient contiene 15 skills recopiladas de apecloud-inc, con cobertura ocupacional por repositorio y páginas de detalle dentro del sitio.
Skills en este repositorio
Practical guide for adding a new database or middleware engine to DBClient. Use this skill when you need to introduce a new dbType.
Cross-cutting core mechanisms of DBClient: CLI argument parsing, DBConfig, TesterFactory, TestExecutor, and the DatabaseTester interface. Use this skill when modifying generic flows or adding engine registration, validation, or dependencies.
KV / coordination engines in DBClient: Redis, RedisCluster, Redis Sentinel, Camellia-Proxy, Etcd, and Zookeeper. Use this skill when adding, debugging, or modifying such a Tester.
Message-queue engines in DBClient: Kafka, Pulsar, RabbitMQ, and RocketMQ. Use this skill when adding, debugging, or modifying such a Tester.
Relational / JDBC-protocol-compatible engines in DBClient. Covers MySQL-compatible, PostgreSQL-compatible, Oracle, SQLServer, domestic / regulated databases, and analytical databases such as StarRocks, Doris, and ClickHouse. Use this skill when adding, debugging, or modifying such a Tester.
Search / log-retrieval engines in DBClient: Elasticsearch 8.x and OpenSearch. Use this skill when adding, debugging, or modifying such a Tester.
Document / object / graph / big-data storage engines in DBClient: MongoDB, MinIO, Hadoop, Hive, Vault, and Nebula. Use this skill when adding, debugging, or modifying such a Tester.
Time-series engines in DBClient: InfluxDB, TDengine, VictoriaMetrics, VictoriaLogs, and Loki. Use this skill when adding, debugging, or modifying such a Tester.
Vector databases in DBClient: Milvus and Qdrant. Use this skill when adding, debugging, or modifying such a Tester.
Entry index for DBClient (OneClient), a unified database testing CLI client. Start here when you are unsure which sub-skill to use.
Generic logic for DBClient benchmark test mode: DatabaseTester.bench() implementation conventions, concurrency model, and result calculation. Use this skill when modifying the performance-test framework or troubleshooting throughput/concurrency issues.
Generic logic for DBClient executionloop test mode: DatabaseTester.executionLoop() periodic execution and intermediate reporting. Use this skill when modifying long-running tests or scheduled report logic.
Generic logic for DBClient query test mode: DatabaseTester.execute(), QueryResult wrapping, and format branches in TestExecutor.formatQueryResult(). Use this skill when modifying query execution or result output for any engine.
Generic logic for DBClient connectionstress test mode: DatabaseTester.connectionStress() implementation conventions, concurrent connection creation, and connection-leak troubleshooting. Use this skill when modifying the stress model or investigating connection-count issues.
Decision tree and common failure modes for DBClient. Use this skill first when a test run fails and you need to narrow down whether the issue is in CLI args, factory mapping, the engine Tester, result formatting, or dependencies.