Forward Xu created CALCITE-3706:
---
Summary: IMPLEMENT POWEROFTWOF FUNCTION
Key: CALCITE-3706
URL: https://issues.apache.org/jira/browse/CALCITE-3706
Project: Calcite
Issue Type: Improvement
Forward Xu created CALCITE-3705:
---
Summary: IMPLEMENT POWEROFTWOD FUNCTION
Key: CALCITE-3705
URL: https://issues.apache.org/jira/browse/CALCITE-3705
Project: Calcite
Issue Type: Improvement
Forward Xu created CALCITE-3704:
---
Summary: IMPLEMENT TWOTOTHEDOUBLESCALEDOWN FUNCTION
Key: CALCITE-3704
URL: https://issues.apache.org/jira/browse/CALCITE-3704
Project: Calcite
Issue Type:
Forward Xu created CALCITE-3703:
---
Summary: IMPLEMENT TWOTOTHEDOUBLESCALEUP FUNCTION
Key: CALCITE-3703
URL: https://issues.apache.org/jira/browse/CALCITE-3703
Project: Calcite
Issue Type:
Forward Xu created CALCITE-3701:
---
Summary: IMPLEMENT NEXTDOWN FUNCTION
Key: CALCITE-3701
URL: https://issues.apache.org/jira/browse/CALCITE-3701
Project: Calcite
Issue Type: Improvement
Forward Xu created CALCITE-3702:
---
Summary: IMPLEMENT SCALB FUNCTION
Key: CALCITE-3702
URL: https://issues.apache.org/jira/browse/CALCITE-3702
Project: Calcite
Issue Type: Improvement
Forward Xu created CALCITE-3700:
---
Summary: IMPLEMENT NEXTUP FUNCTION
Key: CALCITE-3700
URL: https://issues.apache.org/jira/browse/CALCITE-3700
Project: Calcite
Issue Type: Improvement
Forward Xu created CALCITE-3699:
---
Summary: IMPLEMENT NEXTAFTER FUNCTION
Key: CALCITE-3699
URL: https://issues.apache.org/jira/browse/CALCITE-3699
Project: Calcite
Issue Type: Improvement
Forward Xu created CALCITE-3698:
---
Summary: IMPLEMENT GETEXPONENT FUNCTION
Key: CALCITE-3698
URL: https://issues.apache.org/jira/browse/CALCITE-3698
Project: Calcite
Issue Type: Improvement
Forward Xu created CALCITE-3696:
---
Summary: IMPLEMENT HYPOT FUNCTION
Key: CALCITE-3696
URL: https://issues.apache.org/jira/browse/CALCITE-3696
Project: Calcite
Issue Type: Improvement
Forward Xu created CALCITE-3697:
---
Summary: IMPLEMENT COPYSIGN FUNCTION
Key: CALCITE-3697
URL: https://issues.apache.org/jira/browse/CALCITE-3697
Project: Calcite
Issue Type: Improvement
Forward Xu created CALCITE-3695:
---
Summary: IMPLEMENT TANH FUNCTION
Key: CALCITE-3695
URL: https://issues.apache.org/jira/browse/CALCITE-3695
Project: Calcite
Issue Type: Improvement
Forward Xu created CALCITE-3694:
---
Summary: IMPLEMENT SINH FUNCTION
Key: CALCITE-3694
URL: https://issues.apache.org/jira/browse/CALCITE-3694
Project: Calcite
Issue Type: Improvement
Forward Xu created CALCITE-3693:
---
Summary: IMPLEMENT ULP FUNCTION
Key: CALCITE-3693
URL: https://issues.apache.org/jira/browse/CALCITE-3693
Project: Calcite
Issue Type: Improvement
Forward Xu created CALCITE-3691:
---
Summary: IMPLEMENT NEGATEEXACT FUNCTION
Key: CALCITE-3691
URL: https://issues.apache.org/jira/browse/CALCITE-3691
Project: Calcite
Issue Type: Improvement
Forward Xu created CALCITE-3692:
---
Summary: IMPLEMENT TOINTEXACT FUNCTION
Key: CALCITE-3692
URL: https://issues.apache.org/jira/browse/CALCITE-3692
Project: Calcite
Issue Type: Improvement
Forward Xu created CALCITE-3690:
---
Summary: IMPLEMENT DECREMENTEXACT FUNCTION
Key: CALCITE-3690
URL: https://issues.apache.org/jira/browse/CALCITE-3690
Project: Calcite
Issue Type: Improvement
Forward Xu created CALCITE-3689:
---
Summary: IMPLEMENT INCREMENTEXACT FUNCTION
Key: CALCITE-3689
URL: https://issues.apache.org/jira/browse/CALCITE-3689
Project: Calcite
Issue Type: Improvement
Forward Xu created CALCITE-3688:
---
Summary: IMPLEMENT MULTIPLYEXACT FUNCTION
Key: CALCITE-3688
URL: https://issues.apache.org/jira/browse/CALCITE-3688
Project: Calcite
Issue Type: Improvement
Forward Xu created CALCITE-3687:
---
Summary: IMPLEMENT SUBTRACTEXACT FUNCTION
Key: CALCITE-3687
URL: https://issues.apache.org/jira/browse/CALCITE-3687
Project: Calcite
Issue Type: Improvement
Forward Xu created CALCITE-3686:
---
Summary: IMPLEMENT ADDEXACT FUNCTION
Key: CALCITE-3686
URL: https://issues.apache.org/jira/browse/CALCITE-3686
Project: Calcite
Issue Type: Improvement
Forward Xu created CALCITE-3685:
---
Summary: IMPLEMENT RINT FUNCTION
Key: CALCITE-3685
URL: https://issues.apache.org/jira/browse/CALCITE-3685
Project: Calcite
Issue Type: Improvement
Forward Xu created CALCITE-3684:
---
Summary: IMPLEMENT CBRT FUNCTION
Key: CALCITE-3684
URL: https://issues.apache.org/jira/browse/CALCITE-3684
Project: Calcite
Issue Type: Improvement
Forward Xu created CALCITE-3683:
---
Summary: Enhanced MATH Function
Key: CALCITE-3683
URL: https://issues.apache.org/jira/browse/CALCITE-3683
Project: Calcite
Issue Type: Improvement
>I think we should try to make our cost
estimations more realistic in terms of cpu and io and don't try to put
everything in rows as it is the case for various operators.
This of course requires the VolcanoCost to be adapted.
Well. The more I revise costs, the more I incline to that opinion as
The Apache Jenkins build system has built Calcite-Master (build #1540)
Status: Still Failing
Check console output at https://builds.apache.org/job/Calcite-Master/1540/ to
view the results.
Hi Vladimir,
I think we should leave it as it was.
The fact that VolcanoCost does not exploit the cpu and io information is a
problem of that class and not of the Sort#computeSelfCost method. Note that
the VolcanoPlanner can be configured with a RelOptCostFactory which means
that people who use
Technically speaking, single-block read time for HDDs is pretty much
stable, so the use of seconds might be not that bad.
However, it seconds might be complicated to measure CPU-like activity (e.g.
different machines might execute EnumerableJoin at different rate :( )
What if we benchmark a
Hi,
It looks like testAggregateMaterializationOnCountDistinctQuery1 is invalid.
The test creates materialization for
select deptno, empid, salary from emps group by deptno, empid, salary
Then it issues the SQL:
select deptno, count(distinct empid) as c from (
select deptno, empid
from emps
Vladimir Sitnikov created CALCITE-3682:
--
Summary: MaterializationService#defineMaterialization loses
information on unique keys
Key: CALCITE-3682
URL: https://issues.apache.org/jira/browse/CALCITE-3682
I understand the cost doesn't have to match actual execution duration
and it doesn't really matter if it does as long as we can get the
relative ordering of plans roughly similar. That's why I'm suggesting
not calling the cost seconds, even if we are trying to roughly
approximate them. But I don't
Michael>although I would be hesitant to refer to "seconds"
Do you have better ideas?
If my memory serves me well, PostgreSQL uses seconds as well for cost units.
OracleDB is using "singleblock read" for the cost unit.
Michael>how long execution will take on any particular system
The idea for
A cost unit sounds fine to me, although I would be hesitant to refer
to "seconds" or other concrete measurements since there's no easy way
to guess how long execution will take on any particular system.
--
Michael Mior
mm...@apache.org
Le sam. 4 janv. 2020 à 10:56, Vladimir Sitnikov
a écrit :
>
Jin>In ReflectiveSchema, Statistics of FieldTable is given as UNKNOWN[1][2].
Please check[CALCITE-3661] Derive rowCount statistics for tables in
ReflectiveSchema that are based on arrays/collections
and [CALCITE-3680] Add ability to express unique constraints in
ReflectiveSchema
commits in
Hi, Vladimir ~
In ReflectiveSchema, Statistics of FieldTable is given as UNKNOWN[1][2].
When reading a table's row count, if no statistics given, a default value
of 100 will be returned [3] -- this is relatively a bigger value compared
with the fields defined in HRFKUKSchema.
When a materialized
Vladimir Sitnikov created CALCITE-3681:
--
Summary: Refine RelMdColumnUniqueness and RelMdRowCount for
Aggregate
Key: CALCITE-3681
URL: https://issues.apache.org/jira/browse/CALCITE-3681
Project:
Vladimir Sitnikov created CALCITE-3680:
--
Summary: Add ability to express unique constraints in
ReflectiveSchema
Key: CALCITE-3680
URL: https://issues.apache.org/jira/browse/CALCITE-3680
Project:
Hi,
I've spent some time on stabilizing the costs (see
https://github.com/apache/calcite/pull/1702/commits ), and it looks like we
might want to have some notion of "cost unit".
For instance, we want to express that sorting table with 2 int columns is
cheaper than sorting table with 22 int
Ritesh created CALCITE-3679:
---
Summary: Calcite to support Lamda Expressions
Key: CALCITE-3679
URL: https://issues.apache.org/jira/browse/CALCITE-3679
Project: Calcite
Issue Type: New Feature
Ritesh created CALCITE-3678:
---
Summary: Calcite to support map_filter function
Key: CALCITE-3678
URL: https://issues.apache.org/jira/browse/CALCITE-3678
Project: Calcite
Issue Type: New Feature
40 matches
Mail list logo
