Fascinated/beatsaber-scoretracker
Archived
1
0
Fork 0
Code Issues 1 Pull Requests 7 Actions Releases Activity

Update dependency org.questdb:questdb to v8.1.0 #2

Merged
Fascinated merged 1 commits from renovate/org.questdb-questdb-8.x into master 2024-07-27 19:22:36 +00:00
Conversation 0 Commits 1 Files Changed 1 +1 -1
renovate-bot commented 2024-07-24 20:02:31 +00:00
Collaborator
Copy Link

This PR contains the following updates:

Package Type Update Change
org.questdb:questdb (source) compile minor 8.0.3 -> 8.1.0

Release Notes

questdb/questdb (org.questdb:questdb)

v8.1.0

Compare Source

QuestDB 8.1.0 has arrived.

In this release, QuestDB's foundation takes a second step towards our next generation architecture.

Our prior release introduced JSON extraction.

And now, by popular demand, QuestDB meets Apache Parquet.

New Features 🐣
  • Parquet read support Use the read_parquet() function to read Apache Parquet files.
  • Improved SAMPLE BY:
    • FROM-TO syntax: Specify result ranges, with support for prefilling and postfilling data. Also can correct misaligned buckets.
    • Parallel SAMPLE BY: Now supports FILL(VALUE) and FILL(NULL).
  • Snapshot recovery: Added a trigger file to initiate snapshot recovery, improving database resilience and ease-of-use.
Performance 🚀
  • Improved ILP ingress latency
  • SQL Performance:
    • Speedup for small transaction writing by 50-100%.
    • Enhanced performance for the like/ilike operator on symbol columns.
    • Speed improvements for regexp_replace(varchar) with simple patterns.
  • Aggregation queries: Aggregation queries are now faster.
Bug Fixes 🐛

  • SQL:

    • Fixed spurious "unsupported operation" errors.
    • Corrected wrong results from parallel WHERE and GROUP BY for some function keys.
    • Fixed incorrect results from parallel GROUP BY with a single varchar function key.
    • Addressed issues with some window functions double counting rows.

  • Core:

    • Prevented table suspension under memory pressure.
    • Fixed Charts when using together with OAuth.

Pull requests

New Contributors

Full Changelog: https://github.com/questdb/questdb/compare/8.0.3...8.1.0

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [org.questdb:questdb](https://questdb.io/) ([source](https://github.com/questdb/questdb)) | compile | minor | `8.0.3` -> `8.1.0` | --- ### Release Notes <details> <summary>questdb/questdb (org.questdb:questdb)</summary> ### [`v8.1.0`](https://github.com/questdb/questdb/releases/tag/8.1.0) [Compare Source](https://github.com/questdb/questdb/compare/8.0.3...8.1.0) QuestDB 8.1.0 has arrived. In this release, QuestDB's foundation takes a second step towards our next generation architecture. Our prior release introduced JSON extraction. And now, by popular demand, QuestDB meets Apache Parquet. ##### New Features 🐣 - **Parquet read support** Use the `read_parquet()` function to read [Apache Parquet](https://questdb.io/glossary/apache-parquet) files. - **Improved SAMPLE BY:** - FROM-TO syntax: Specify result ranges, with support for prefilling and postfilling data. Also can correct misaligned buckets. - Parallel SAMPLE BY: Now supports `FILL(VALUE)` and `FILL(NULL)`. - **Snapshot recovery:** Added a trigger file to initiate snapshot recovery, improving database resilience and ease-of-use. ##### Performance 🚀 - **Improved ILP ingress latency** - **SQL Performance:** - Speedup for small transaction writing by 50-100%. - Enhanced performance for the `like/ilike` operator on symbol columns. - Speed improvements for `regexp_replace(varchar)` with simple patterns. - **Aggregation queries:** Aggregation queries are now faster. ##### Bug Fixes 🐛 - **SQL:** - Fixed spurious "unsupported operation" errors. - Corrected wrong results from parallel `WHERE` and `GROUP BY` for some function keys. - Fixed incorrect results from parallel `GROUP BY` with a single varchar function key. - Addressed issues with some window functions double counting rows. - **Core:** - Prevented table suspension under memory pressure. - Fixed Charts when using together with OAuth. #### Pull requests - fix(sql): fix spurious "unsupported operation" errors by [@&#8203;bluestreak01](https://github.com/bluestreak01) in https://github.com/questdb/questdb/pull/4632 - perf(core): speedup small transaction writing 50-100% by [@&#8203;ideoma](https://github.com/ideoma) in https://github.com/questdb/questdb/pull/4793 - fix(sql): fix wrong results returned from parallel WHERE and GROUP BY for some function keys by [@&#8203;puzpuzpuz](https://github.com/puzpuzpuz) in https://github.com/questdb/questdb/pull/4796 - fix(sql): incorrect results returned from parallel GROUP BY with single varchar function key by [@&#8203;puzpuzpuz](https://github.com/puzpuzpuz) in https://github.com/questdb/questdb/pull/4798 - fix(core): avoid table suspension when under memory pressure by [@&#8203;jerrinot](https://github.com/jerrinot) in https://github.com/questdb/questdb/pull/4745 - perf(sql): speed up like/ilike operator on symbol column by [@&#8203;puzpuzpuz](https://github.com/puzpuzpuz) in https://github.com/questdb/questdb/pull/4794 - perf(sql): speed up regexp_replace(varchar) for simple patterns by [@&#8203;puzpuzpuz](https://github.com/puzpuzpuz) in https://github.com/questdb/questdb/pull/4668 - fix(sql): some window functions might double count rows by [@&#8203;jerrinot](https://github.com/jerrinot) in https://github.com/questdb/questdb/pull/4804 - feat(sql): read_parquet() function by [@&#8203;eugenels](https://github.com/eugenels) in https://github.com/questdb/questdb/pull/4460 - feat(sql): introduce SAMPLE BY FROM-TO syntax for specifying result ranges by [@&#8203;nwoolmer](https://github.com/nwoolmer) in https://github.com/questdb/questdb/pull/4733 - fix(ui): fix Charts when using together with OAuth by [@&#8203;insmac](https://github.com/insmac) in https://github.com/questdb/questdb/pull/4813 - feat(core): trigger file to initiate snapshot recovery by [@&#8203;jerrinot](https://github.com/jerrinot) in https://github.com/questdb/questdb/pull/4807 #### New Contributors - [@&#8203;jchrys](https://github.com/jchrys) made their first contribution in https://github.com/questdb/questdb/pull/4808 **Full Changelog**: https://github.com/questdb/questdb/compare/8.0.3...8.1.0 </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MjYuNCIsInVwZGF0ZWRJblZlciI6IjM3LjQyNi40IiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIiwibGFiZWxzIjpbXX0=-->
renovate-bot added 1 commit 2024-07-24 20:02:32 +00:00
Fascinated merged commit 99d545d81f into master 2024-07-27 19:22:36 +00:00
Fascinated deleted branch renovate/org.questdb-questdb-8.x 2024-07-27 19:22:36 +00:00
This repo is archived. You cannot comment on pull requests.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Fascinated/beatsaber-scoretracker#2
No description provided.
Delete Branch "renovate/org.questdb-questdb-8.x"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?