dennis zhuang
dennis zhuang
@edenworky Sorry for the delayed response. Thank you for the detailed explanation. > So to sum up my understanding of your response here and on https://github.com/killme2008/defun/issues/26, I could just take...
https://github.com/sofastack/sofa-jraft/issues/1209 线程池是复用的，并不需要释放。
Good catch! 可以的，欢迎来贡献。
> 目前看3和4应该是每次都会走到的。 我的想法是在disruptor的范围内复用，出了disruptor的范围后，再创建对象供后面使用。 以new LogEntry为例，我应该在NodeImpl#apply那边复用对象，在executeApplyingTasks的时候再new一份，应该就不会影响后续使用吧。 可以的，其实就是将 LogEntry 纳入复用范围。
@linking12 引入考虑双模式了，加入一个 EvenBus 抽象，这里本质上就是因为 disruptor 的复用模型引起的，在任务处理很快的情况下，批量复用的模式没有太大优势了，尤其 zgc 下。
Thank you for your report; it appears to be a bug.
@discord9 Let's update this issue status.
To support this, simply add a nullable int64 column to https://github.com/GreptimeTeam/greptimedb/blob/main/src/catalog/src/system_schema/information_schema/tables.rs with all values set to `null`.
@rohankumardubey Thanks. After some investigation, I found that this column does exist, it's just that the request sent by VSCode used uppercase field names and backticks for forced quoting. Therefore,...
Another issue with subqueries: ```SQL mysql> select * from greptime_physical_table where greptime_timestamp > '2025-05-25 00:00:00' and __table_id = (select table_id from information_schema.tables where table_name='prometheus_build_info'); ``` This SQL query hangs. @waynexia