This week in Databend #49
Databend is an open source elastic and reliable Modern Cloud Data Warehouse, it offers blazing fast query and combines elasticity, simplicity, low cost of the cloud, built to make the Data Cloud easy.
Below is a list of some major changes that we don't want you to miss.
- add call procedure for sync stage (#6344)
- support all
- support any, all and some subquery in parser (#6438)
- migrate call statement to new planner (#6361)
IS [NOT] DISTINCT FROMin planner_v2 (#6170)
- support qualified column name with database specified (#6444)
- support mark join, (not)in/any subquery, make tpch16 and tpch18 happy (#6412)
- add Presign statement (#6503)
- logic test with clickhouse handler (#6329)
- enable semantic PRs and fully migrate to mergify and gh cli (#6386, #6419 and more)
- fix hashmap memory leak (#6354)
- fix array inner type with null (#6407)
- fix lost event in resize processor (#6501)
Let's learn a weekly tip from Databend.
Monitoring Databend with Sentry
Sentry is cross-platform application monitoring, with a focus on error reporting.
Databend supports error tracking and performance monitoring with Sentry.
- Use the SaaS service provided by sentry.io, or deploy it yourself by following Self-Hosted Sentry.
- Create a project in Sentry and get a
DSNlooks the same as
This will only use the sentry-log feature, which will help us with error tracking.
SENTRY_TRACES_SAMPLE_RATE greater than 0.0 will allow sentry to perform trace sampling, which will help set up performance monitoring.
DATABEND_SENTRY_DSN="<your-sentry-dsn>" SENTRY_TRACES_SAMPLE_RATE=1.0 LOG_LEVEL=DEBUG ./databend-query
SENTRY_TRACES_SAMPLE_RATE to a lower value in production.
You can check the changelogs of Databend nightly to learn about our latest developments.
Thanks a lot to the contributors for their excellent work this week.
Please join the DatafuseLabs Community if you are interested in Databend.
We are looking forward to seeing you try our code. We have a strong team behind you to ensure a smooth experience in trying our code for your projects. If you are a hacker passionate about database internals, feel free to play with our code.
You can submit issues for any problems you find. We also highly appreciate any of your pull requests.