Hi Abhijit,
there are actually a lot of places where time is spent. I think the most
time consuming places are jvm lazy class loading and code generation for
metadata framework.
Anyway, on a long distance the planning time will be very small.
Thanks.
--
Roman
On 24.08.2023 00:51, Abhijit
Can I get one or two reviews of
https://github.com/apache/calcite/pull/3394 /
https://issues.apache.org/jira/browse/CALCITE-5914 ?
I'm trying to introduce an architecture so that Java functions that
need to retain state for performance reasons (e.g. a cached compiled
regular expression) are
I just took a look at
https://github.com/apache/calcite/pull/3393/checks. I see an autostyle
violation, and it looks valid. That error is there so that you can fix
it and not waste reviewers' time.
On Wed, Aug 23, 2023 at 2:15 PM Julian Hyde wrote:
>
> There aren't many false positives or flaky
There aren't many false positives or flaky tests in CI,
checker-framework, error-prone. If it says that (say) you are passing
a nullable object to a method that requires a not-nullable argument,
you probably are.
I find it useful to run checker-framework on my own computer, rather
than waiting
Thanks a lot for your help.
Would you happen to have any insights into where exactly the time is spent
during the warm up?
On Tue, Aug 22, 2023 at 11:58 PM Roman Kondakov
wrote:
> Hi Abhijit,
>
> Usually the very first query is optimized a bit long in Calcite. But
> after some warm-up the next
Zoltan Haindrich created CALCITE-5953:
-
Summary: AggregateCaseToFilterRule may make inaccurate SUM
transformation
Key: CALCITE-5953
URL: https://issues.apache.org/jira/browse/CALCITE-5953
PR is ready for review, plz explain did i need to fix all of: CI /
CheckerFramework issues ?
Seems some of them are false positive.
thanks !
Evgeny Stanilovsky created CALCITE-5950:
Leonid Chistov created CALCITE-5952:
---
Summary: Semi-Join incorrectly reordered with Left-Join by
SemiJoinJoinTransposeRule
Key: CALCITE-5952
URL: https://issues.apache.org/jira/browse/CALCITE-5952
Hi Abhijit,
Usually the very first query is optimized a bit long in Calcite. But
after some warm-up the next queries will be planned faster and faster.
If you use Calcite as a part of a server application, then the problem
with a long query planning will be eliminated after a few query runs.
