StarRocks/starrocks - Open Source PR Review Scorecard

The world's fastest open query engine for sub-second analytics both on and off the data lakehouse. With the flexibility to support nearly any scenario, StarRocks provides best-in-class performance for multi-dimensional analytics, real-time analytics, and ad-hoc queries. A Linux Foundation project.

C-Rank Grade: S (Elite) - 70/100

External PR Merge Rate: 71%

Response Time: -

First Timer Success: 50%

Frequently Asked Questions

Is StarRocks/starrocks welcoming to first-time open-source contributors?

StarRocks/starrocks has a recorded first-timer success rate of 50.4%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in StarRocks/starrocks respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 70.5 C-Rank™ score (S Tier) represent?

The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 70.5 places StarRocks/starrocks in the S tier.

What is the external contributor pull request merge rate for StarRocks/starrocks?

The external contributor pull request merge rate for StarRocks/starrocks is 70.6%, based on public PR activity from non-core contributors.

Are there Good First Issues available in StarRocks/starrocks?

StarRocks/starrocks currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

StarRocks
StarRocks/starrocksS•Elite12.2k
GitHub
Back to Explorer
StarRocks

StarRocks/starrocks

12,166
Active (30d)S•Elite(70/100)Java

The world's fastest open query engine for sub-second analytics both on and off the data lakehouse. With the flexibility to support nearly any scenario, StarRocks provides best-in-class performance for multi-dimensional analytics, real-time analytics, and ad-hoc queries. A Linux Foundation project.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Empathetic Technical Mentor

Warmth Score
7.5/10
Patience Score
8.2/10
Nitpick Rate
20%

Collaborative maintainer environment in StarRocks/starrocks. Reviews community pull requests with focus on project quality.

Top PR Submission Do's

  • •Ensure code complies with the project coding style
  • •Keep PRs scoped to a single concern
  • •Include context and link to the related issue

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit PRs without linking an issue
  • •Do not break existing tests without fixing them
  • •Do not mix unrelated refactors in a single PR
Response Velocity
-
No reviewer activity recorded

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
70.6%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
50.4%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
114 core
Highly collaborative maintainer core
Diagnostic Health HUD
70.6%
Merge Gauge
50.4%
1st-Timer
Community Vibe43/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for StarRocks/starrocks
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/StarRocks/starrocks)](https://getmerged.abhishekco.de/StarRocks/starrocks?utm_source=github&utm_medium=badge)

Active Good First Issues (5)

View on GitHub

Steps to reproduce the behavior (Required) docker run -p 9030:9030 -p 8030:8030 -p 8040:8040 --name sr-repro \ -itd starrocks/allin1-ubuntu:4.1.1 CREATE TABLE: CREATE DATABASE sr_histogram_repro; USE sr_histogram_repro; CREATE TABLE t (id BIGINT NOT NULL, v INT NULL) ENGINE=OLAP DUPLICATE KEY(id) DISTRIBUTED BY HASH(id) BUCKETS 4 PROPERTIES ("replication_num" = "1"); INSERT INTO: INSERT INTO t VALUES (1,1),(2,1),(3,2),(4,2),(5,3),(6,3),(7,4),(8,4),(9,5),(10,5); SELECT: SELECT histogram(v, cast(64 as int), cast(1.0 as double)) FROM t; Expected behavior (Required) A histogram string, or a clear error if the aggregate is not intended to be called directly from SQL. Real behavior (Required) Every BE running a fragment aborts simultaneously. The client sees a message that names a missing backend rather than the statement that caused it: ERROR 1064 (HY000): Backend node not found. Check if any backend node is down. backend: [127.0.0.1 alive: true inBlacklist: true] be.out shows rep

📅 Opened Aug 18, 2026💬 2 comments
Quality: 50/100Contribute

Steps to reproduce the behavior (Required) CREATE TABLE example_table ( col1 VARCHAR(10) ) ENGINE = olap DUBLICATE KEY(col1 ) DISTRIBUTED BY HASH(col1); CREATE OR REPLACE GLOBAL FUNCTION test_func(a STRING) RETURNS a; CREATE MATERIALIZED VIEW IF NOT EXISTS udf_bug_test REFRESH async AS select test_func(item) from example_table; Expected behavior (Required) Materialized view is created and can be used for rewrite query Real behavior (Required) select QUERY_REWRITE_STATUS from information_schema.materialized_views WHERE table_name = 'udf_bug_test' UNKNOWN: MV plan is not in cache, valid check is unknown And error is logged: 2026-07-12 22:53:04.640+03:00 WARN (mv-plan-cache-4|105) [MvPlanContextBuilder.doGetOptimizePlan():67] Failed to build mv plan context com.google.common.util.concurrent.UncheckedExecutionException: java.lang.NullPointerException: Cannot invoke "com.starrocks.catalog.UserIdentity.isEphemeral()" because "userIdentity" is null at com.google.co

📅 Opened Jul 12, 2026💬 1 comment
Quality: 40/100Contribute

Feature request Is your feature request related to a problem? Please describe. StarRocks returns Arrow IPC data over Arrow Flight completely uncompressed. Confirmed at source level: be/src/service/service_be/arrow_flight_sql_service.cpp — DoGetStatement returns RecordBatchStream(reader) with no IpcWriteOptions argument; the codec defaults to UNCOMPRESSED. fe/.../ArrowFlightSqlService.java — FlightServer.builder has no .compressor() call; nothing compression-related exists on the builder. No BE or FE config parameters exist to enable compression. Confirmed with StarRocks support (Rocky, 2026-05-22). Client-side workarounds have no effect: grpc-encoding: gzip and grpc.default_compression_algorithm only compress client→server messages. The server must compress its own DoGet responses, which it does not. Describe the solution you'd like Add IpcWriteOptions with a codec to RecordBatchStream in DoGetStatement: arrow::ipc::IpcWriteOptions options = arrow::ipc::IpcWriteOptions::Default

📅 Opened May 26, 2026💬 1 comment
Quality: 30/100Contribute

Enabling the -pie compilation results in the following error: /usr/local/bin/ld: /usr1/opensourcebuild/StarRocks/code/thirdparty/installed//lib/libtenann-bundle-avx2.a(parallel.o): relocation R_X86_64_32 against hidden symbol `gomp_global_icv' can not be used when making a PIE object %F/usr/local/bin/ld: failed to set dynamic section sizes: bad value collect2: error: ld returned 1 exit status execute failed, /opt/buildtools/gcc_12.3.0/bin/../bin/g++: Operation not permitted ninja: build stopped: subcommand failed. real 0m48.010s user 0m4.282s sys 0m9.253s [CloudCache] 2026/02/27 22:00:35 [ { "type": "c", "total": "6", "remote_hit": "0", "remote_avg_cost": "", "hash_avg_cost": "3ms", "local_hit": { "direct": "2", "preprocessed": "0" }, "miss": "0", "skip": "4" } ] StarRocks version (Required) 3.4.5

📅 Opened Feb 28, 2026💬 2 comments
Quality: 40/100Contribute

Steps to reproduce the behavior (Required) StarRocks > CREATE TABLE IF NOT EXISTS `test_schema_yq4hcg84`.`sr_mv_combo_a_src` (`order_id` BIGINT, `event_date` DATE, `customer_id` INT, `amount` DECIMAL(18, 2), `region` VARCHAR(50)) PRIMARY KEY (`order_id`, `event_date`) PARTITION BY `event_date`; ERROR 1064 (HY000): Getting analyzing error. Detail message: The partition expr should base on key column. StarRocks > CREATE TABLE IF NOT EXISTS `test_schema_yq4hcg84`.`sr_mv_combo_a_src` (`order_id` BIGINT, `event_date` DATE, `customer_id` INT, `amount` DECIMAL(18, 2), `region` VARCHAR(50)) PRIMARY KEY (`order_id`, `event_date`) PARTITION BY (`event_date`); Query OK, 0 rows affected (0.03 sec) The only diff is the parentheses for PARTITION BY. PARTITION BY event_date PARTITION BY (event_date) Expected behavior (Required) According to the expression partitioning syntax, the first only should be success too. And error "The partition expr should base on key column" is not correct. Real

📅 Opened Jan 28, 2026💬 4 comments
Quality: 40/100Contribute
Looking for more Java beginner tasks?Explore Java GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for StarRocks/starrocks

When evaluating whether to contribute to StarRocks/starrocks, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.

Currently, maintainers of StarRocks/starrocks acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 70.6% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to StarRocks/starrocks

01

Is StarRocks/starrocks welcoming to first-time open-source contributors?

StarRocks/starrocks has a recorded first-timer success rate of 50.4%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 70.5 C-Rank™ score represent?

The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 70.5 places StarRocks/starrocks in the Elite tier.

04

What is the external contributor pull request merge rate for StarRocks/starrocks?

The external pull request merge rate is 70.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in StarRocks/starrocks?

Yes, StarRocks/starrocks currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for StarRocks/starrocks are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.