NobiGo comments

Results 31 comments of


                                            NobiGo

[CALCITE-6592] RelMdPredicates pull up wrong predicate from UNION whe…

> Hey @NobiGo are you still planning to move this forward? Yes. If I have free time, I will handle it. After fixing the CALCITE-6599(RelMdPredicates should pull up more predicates...

[CALCITE-6592] RelMdPredicates pull up wrong predicate from UNION whe…

@zabetak As the unit test, We always extract the predicate `IS NULL($1)` when `null` or `comm = null` so the `RexUnknownAs` will not affect the results. And I have discovered...

[CALCITE-4725] Between clause operands checker should check all combi…

@paul8263 please add unit test in this patch.

[CALCITE-4696] The method of EnumerableTableScan.fieldExpression throw NullPointerException

@ns7381 please pure your PR. this PR includes other PR that has been commited.

[CALCITE-6731] Support bitwise XOR (^) operator in SQL

@Dwrite please ensure that the Commit info in the PR is consistent with the Jira summary. If the PR has implemented "

[CALCITE-6731] Support bitwise XOR (^) operator in SQL

> @NobiGo hi, thanks for your time. already add relevant descriptions to Jira. I have currently implemented support for the ^ (bitwise XOR) and

[CALCITE-4868] Elasticsearch adapter fails if GROUP BY is followed by ORDER BY

1) Please reformat the commit info like[CALCITE-XXXX] XXXXXXXXX. 2)The commit info needs to stay the same as The Jira's summary.

[CALCITE-6437]For druid sql JSON_OBJECT() function results in RUNTIME_FAILURE when querying INFORMATION_SCHEMA.COLUMNS

@AlbericByte Please create a new issue in [JIRA](https://issues.apache.org/jira/browse/CALCITE).

[Calcite-3373] Decorrelate boolean context IN or existential subquery directly into SEMI/ANTI join

@ViggoC Please create a Jira to describe the PR . For detailed instructions, please refer to https://calcite.apache.org/develop/#contributing

[CALCITE-4693] Query with Lateral Join should converted to Left Join …

> I believe this is not the root cause of the incorrect query results. It's related to #4375. > > The issue occurs in the Decorrelator. PR-4375 appears to have...