active 2025-02-20 → 2025-03-12 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 21 days from 2025-02-20 to 2025-03-12. Pushes: 3 total, peak 1 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 13 total, peak 4 in a day. Comments: 11 total, peak 3 in a day. Stars: 0 total, peak 0 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| wlsgur073 | 27 | 3 | 0 | 11 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#15wlsgur0732025-03-11 04:07org.apache.kafka.connect.errors.ConnectException: Stopping connector: generated the configured 1000 number of messages
- Issue#15wlsgur0732025-03-11 04:06org.apache.kafka.connect.errors.ConnectException: Stopping connector: generated the configured 1000 number of messages
- Issue comment#15wlsgur0732025-03-11 04:06org.apache.kafka.connect.errors.ConnectException: Stopping connector: generated the configured 1000 number of messages
- Issue#15wlsgur0732025-03-11 03:41org.apache.kafka.connect.errors.ConnectException: Stopping connector: generated the configured 1000 number of messages
- Issue comment#14wlsgur0732025-03-10 11:20org.apache.kafka.connect.errors.DataException: STRUCT is not supported as the document id.
- Issue#14wlsgur0732025-03-10 11:20org.apache.kafka.connect.errors.DataException: STRUCT is not supported as the document id.
- Issue#14wlsgur0732025-03-10 11:13org.apache.kafka.connect.errors.DataException: STRUCT is not supported as the document id.
- Issue comment#13wlsgur0732025-03-10 05:29org.apache.kafka.connect.errors.DataException: Cannot infer mapping without schema.
- Issue#13wlsgur0732025-03-10 05:29org.apache.kafka.connect.errors.DataException: Cannot infer mapping without schema.
- Issue#13wlsgur0732025-03-10 05:10org.apache.kafka.connect.errors.DataException: Cannot infer mapping without schema.
- Issue comment#12wlsgur0732025-02-24 09:20io.debezium.DebeziumException: Failed to start replication stream at LSN{0/19BFF00}; when setting up multiple connectors for the same database host, please make sure to use a distinct replication slot name for each.
- Issue#12wlsgur0732025-02-24 09:20io.debezium.DebeziumException: Failed to start replication stream at LSN{0/19BFF00}; when setting up multiple connectors for the same database host, please make sure to use a distinct replication slot name for each.
- Issue#12wlsgur0732025-02-24 09:18io.debezium.DebeziumException: Failed to start replication stream at LSN{0/19BFF00}; when setting up multiple connectors for the same database host, please make sure to use a distinct replication slot name for each.
- Issue comment#11wlsgur0732025-02-24 04:46everything works fine and the connector sees the schema and writes to the `public` schema in PostgreSQL Sink (JDBC) Connector.
- Issue comment#11wlsgur0732025-02-24 04:18everything works fine and the connector sees the schema and writes to the `public` schema in PostgreSQL Sink (JDBC) Connector.
- Issue#11wlsgur0732025-02-23 04:20everything works fine and the connector sees the schema and writes to the `public` schema in PostgreSQL Sink (JDBC) Connector.
- Issue comment#11wlsgur0732025-02-23 04:04everything works fine and the connector sees the schema and writes to the `public` schema in PostgreSQL Sink (JDBC) Connector.
- Issue#11wlsgur0732025-02-23 04:02everything works fine and the connector sees the schema and writes to the `public` schema in PostgreSQL Sink (JDBC) Connector.
- Issue comment#10wlsgur0732025-02-20 09:09Can't read default varchar column from Source table to Sink table
- Issue#10wlsgur0732025-02-20 08:57Can't read default varchar value in Sink table
- Issue comment#10wlsgur0732025-02-20 08:56Can't read default varchar value in Sink table
- Issue comment#9wlsgur0732025-02-20 08:06io.confluent.connect.jdbc.sink.TableAlterOrCreateException: Table "test"."customers_sink" is missing fields ([SinkRecordField{schema=Schema{INT32}, name='age', isPrimaryKey=false}]) and auto-evolution is disabled.
- Issue#9wlsgur0732025-02-20 08:06io.confluent.connect.jdbc.sink.TableAlterOrCreateException: Table "test"."customers_sink" is missing fields ([SinkRecordField{schema=Schema{INT32}, name='age', isPrimaryKey=false}]) and auto-evolution is disabled.
- Issue#9wlsgur0732025-02-20 07:59io.confluent.connect.jdbc.sink.TableAlterOrCreateException: Table "test"."customers_sink" is missing fields ([SinkRecordField{schema=Schema{INT32}, name='age', isPrimaryKey=false}]) and auto-evolution is disabled.
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.