Ecosyste.ms: Timeline
Browse the timeline of events for every public repo on GitHub. Data updated hourly from GH Archive.
ActivePeter created a review comment on a pull request on GreptimeTeam/greptimedb
Actully this shouldn't happen because we just started sleep, but I think change to `*this.state = State::Pollable;` is ok too.
evenyag opened a draft pull request on GreptimeTeam/greptimedb
feat: get row group time range from cached metadata
I hereby agree to the terms of the [GreptimeDB CLA](https://github.com/GreptimeTeam/.github/blob/main/CLA.md). ## Refer to a related PR or issue link (optional) https://github.com/GreptimeTeam/...
ActivePeter created a review comment on a pull request on GreptimeTeam/greptimedb
> Did you test this under release mode? BTW, better to display the workload type by name instead of the id. I’ll try it
slitobo created a comment on an issue on GreptimeTeam/greptimedb
After updating to 0.9.5, it works normally
slitobo closed an issue on GreptimeTeam/greptimedb
flow result incorrect
### What type of bug is this? Unexpected error ### What subsystems are affected? Standalone mode ### Minimal reproduce step I referenced this document to verify the usage of flow, but it repor...
slitobo created a comment on an issue on GreptimeTeam/greptimedb
i chage to v0.9.5, try this: https://docs.greptime.cn/user-guide/continuous-aggregation/overview but get a error: 2024-10-22T12:19:44.061559Z ERROR flow::adapter: Send writeback request errors ...
evenyag created a review comment on a pull request on GreptimeTeam/greptimedb
Maybe `RuntimeRateLimiter` is clearer than this name. ```suggestion struct RuntimeRateLimiter { ratelimiter: Option<Ratelimiter>, } ```
evenyag created a review comment on a pull request on GreptimeTeam/greptimedb
What if we don't return pending here but poll `this.future`? Since we already sleep enough time, it should be fine to poll `this.future`. ```suggestion *this.state = State...
evenyag created a review comment on a pull request on GreptimeTeam/greptimedb
```suggestion fn new(handle: Arc<RuntimeThrottleSharedWithFuture>, future: F) -> Self { ```
evenyag created a review comment on a pull request on GreptimeTeam/greptimedb
Is `std::thread::yield_now()` necessary? What if we only use `tokio::task::yield_now()`.
github-actions[bot] pushed 1 commit to gh-pages GreptimeTeam/greptimedb
- Deploying to gh-pages from @ GreptimeTeam/greptimedb@0c01532a37d5deb4820d88d0e5edee48749e2a06 🚀 c9bbe42
github-merge-queue[bot] pushed 1 commit to main GreptimeTeam/greptimedb
- feat: Sort within each PartitionRange (#4847) * feat: PartSort * chore: rm unused * chore: typo * chore: mem pool... 0c01532
github-merge-queue[bot] deleted a branch GreptimeTeam/greptimedb
gh-readonly-queue/main/pr-4847-6d503b047a131e8edf50e124fc1872c1eec8fe79
waynexia closed a pull request on GreptimeTeam/greptimedb
feat: Sort within each PartitionRange
I hereby agree to the terms of the [GreptimeDB CLA](https://github.com/GreptimeTeam/.github/blob/main/CLA.md). ## Refer to a related PR or issue link (optional) ## What's changed and what's y...
paomian created a review comment on a pull request on GreptimeTeam/greptimedb
I think we can merge this pr first and follow up with a detailed discussion about merging schema info.
WenyXu created a review comment on a pull request on GreptimeTeam/greptimedb
let's throw a unsupported error
github-merge-queue[bot] created a branch on GreptimeTeam/greptimedb
gh-readonly-queue/main/pr-4847-6d503b047a131e8edf50e124fc1872c1eec8fe79 - An open-source, cloud-native, unified time series database for metrics, logs and events with SQL/PromQL supported. Available on GreptimeCloud.
evenyag created a review comment on a pull request on GreptimeTeam/greptimedb
```suggestion - Introduce PID to achieve more accurate limitation. ```
WenyXu created a review comment on a pull request on GreptimeTeam/greptimedb
It's better to store the ttl in the table metadata instead of the manifest. cc @v0y4g3r
Kev1n8 created a review comment on a pull request on GreptimeTeam/greptimedb
> The JSON null is not the same as the null in a datatype system. > `SELECT json_path_exists(parse_json('null'), '$.a');` Thx for pointing that out. I wonder how it should behave in two differ...
