Re: Override built-in function signature for query parsing

2024-03-05 Thread Xiaoying Wang
> > > On Mar 5, 2024, at 2:18 PM, Xiaoying Wang > wrote: > > > > Hi community, > > > > I want to override the `trim` function. Currently the function it cannot > > support signature like this: `trim(string, characters)`, which is > supported > >

Override built-in function signature for query parsing

2024-03-05 Thread Xiaoying Wang
Hi community, I want to override the `trim` function. Currently the function it cannot support signature like this: `trim(string, characters)`, which is supported by database like DuckDB[1]. I implemented a function like the following: ``` public class SqlTrim2Function extends SqlFunction {

Re: JDBC join order question

2022-03-29 Thread Xiaoying Wang
> should consider adding the Enumerable rules/operators in your planner to be > able to deal with those cases as well. > > Best, > Stamatis > > On Mon, Mar 28, 2022 at 9:30 PM Xiaoying Wang > wrote: > > > Hi Julian, > > > > Oh, I see. Thank you for

Re: JDBC join order question

2022-03-29 Thread Xiaoying Wang
ld be improved about this. > I will open a jira issue and try to fix this. > > [1] > > https://github.com/apache/flink/blob/master/flink-table/flink-table-planner/src/main/scala/org/apache/flink/table/planner/plan/rules/logical/JoinConditionEqualityTransferRule.scala > > Xi

Re: JDBC join order question

2022-03-28 Thread Xiaoying Wang
to dev@calcite. > Please subscribe. > > > On Mar 28, 2022, at 11:10 AM, Xiaoying Wang > wrote: > > > > Hi Benchao, > > > > Thank you so much for the reply! I don't know why I didn't receive the > > email but I found your answer at the archive website. > &

RE: Re: JDBC join order question

2022-03-28 Thread Xiaoying Wang
LE convention as you can see here[2] > > [1] > https://github.com/apache/calcite/blob/master/core/src/main/java/org/apache/calcite/rel/rules/FilterJoinRule.java#L281 > [2] > https://github.com/apache/calcite/blob/master/core/src/main/java/org/apache/calcite/adapter/jdbc/JdbcRules.java#

JDBC join order question

2022-03-25 Thread Xiaoying Wang
Hi all, I have a query joins three tables (star schema, T is the fact table): "select * from R, S, T where R.key = T.key and S.key = T.key" and want to use calcite to parse and generate the physical plan. When I pass the query to a volcano planner, it throws the CannotPlanException: