commits  

Messages by Thread

• [PR] [CALCITE-7403] Missing ENUMERABLE Convention for LogicalConditionalCorrelate [calcite] via GitHub
  • Re: [PR] [CALCITE-7403] Missing ENUMERABLE Convention for LogicalConditionalCorrelate [calcite] via GitHub
  • Re: [PR] [CALCITE-7403] Missing ENUMERABLE Convention for LogicalConditionalCorrelate [calcite] via GitHub
  • Re: [PR] [CALCITE-7403] Missing ENUMERABLE Convention for LogicalConditionalCorrelate [calcite] via GitHub
  • Re: [PR] [CALCITE-7403] Missing ENUMERABLE Convention for LogicalConditionalCorrelate [calcite] via GitHub
  • Re: [PR] [CALCITE-7403] Missing ENUMERABLE Convention for LogicalConditionalCorrelate [calcite] via GitHub
  • Re: [PR] [CALCITE-7403] Missing ENUMERABLE Convention for LogicalConditionalCorrelate [calcite] via GitHub
  • Re: [PR] [CALCITE-7403] Missing ENUMERABLE Convention for LogicalConditionalCorrelate [calcite] via GitHub
  • Re: [PR] [CALCITE-7403] Missing ENUMERABLE Convention for LogicalConditionalCorrelate [calcite] via GitHub
  • Re: [PR] [CALCITE-7403] Missing ENUMERABLE Convention for LogicalConditionalCorrelate [calcite] via GitHub
  • Re: [PR] [CALCITE-7403] Missing ENUMERABLE Convention for LogicalConditionalCorrelate [calcite] via GitHub
  • Re: [PR] [CALCITE-7403] Missing ENUMERABLE Convention for LogicalConditionalCorrelate [calcite] via GitHub
  • Re: [PR] [CALCITE-7403] Missing ENUMERABLE Convention for LogicalConditionalCorrelate [calcite] via GitHub
• [PR] [CALCITE-7401] Multi-level correlated subqueries cause an out-of-range error in the TopDownGeneralDecorrelator [calcite] via GitHub
  • Re: [PR] [CALCITE-7401] Multi-level correlated subqueries cause an out-of-range error in the TopDownGeneralDecorrelator [calcite] via GitHub
  • Re: [PR] [CALCITE-7401] Multi-level correlated subqueries cause an out-of-range error in the TopDownGeneralDecorrelator [calcite] via GitHub
  • Re: [PR] [CALCITE-7401] Multi-level correlated subqueries cause an out-of-range error in the TopDownGeneralDecorrelator [calcite] via GitHub
  • Re: [PR] [CALCITE-7401] Multi-level correlated subqueries cause an out-of-range error in the TopDownGeneralDecorrelator [calcite] via GitHub
  • Re: [PR] [CALCITE-7401] Multi-level correlated subqueries cause an out-of-range error in the TopDownGeneralDecorrelator [calcite] via GitHub
• [PR] [CALCITE-7278] Correlated subqueries in the join condition cannot reference both join inputs [calcite] via GitHub
  • Re: [PR] [CALCITE-7278] Correlated subqueries in the join condition cannot reference both join inputs [calcite] via GitHub
  • Re: [PR] [CALCITE-7278] Correlated subqueries in the join condition cannot reference both join inputs [calcite] via GitHub
  • Re: [PR] [CALCITE-7278] Correlated subqueries in the join condition cannot reference both join inputs [calcite] via GitHub
  • Re: [PR] [CALCITE-7278] Correlated subqueries in the join condition cannot reference both join inputs [calcite] via GitHub
  • Re: [PR] [CALCITE-7278] Correlated subqueries in the join condition cannot reference both join inputs [calcite] via GitHub
  • Re: [PR] [CALCITE-7278] Correlated subqueries in the join condition cannot reference both join inputs [calcite] via GitHub
  • Re: [PR] [CALCITE-7278] Correlated subqueries in the join condition cannot reference both join inputs [calcite] via GitHub
• [PR] [CALCITE-7404] Mongodb aggfuntion not support condition filter [calcite] via GitHub
  • Re: [PR] [CALCITE-7404] Incorrect Field Alias in MongoDB project Stage [calcite] via GitHub
  • Re: [PR] [CALCITE-7404] Incorrect Field Alias in MongoDB project Stage [calcite] via GitHub
  • Re: [PR] [CALCITE-7404] Incorrect Field Alias in MongoDB project Stage [calcite] via GitHub
  • Re: [PR] [CALCITE-7404] Incorrect Field Alias in MongoDB project Stage [calcite] via GitHub
  • Re: [PR] [CALCITE-7404] Incorrect Field Alias in MongoDB project Stage [calcite] via GitHub
  • Re: [PR] [CALCITE-7404] Incorrect Field Alias in MongoDB project Stage [calcite] via GitHub
  • Re: [PR] [CALCITE-7404] Incorrect Field Alias in MongoDB project Stage [calcite] via GitHub
  • Re: [PR] [CALCITE-7404] Incorrect Field Alias in MongoDB project Stage [calcite] via GitHub
  • Re: [PR] [CALCITE-7404] Incorrect Field Alias in MongoDB project Stage [calcite] via GitHub
  • Re: [PR] [CALCITE-7404] Incorrect Field Alias in MongoDB project Stage [calcite] via GitHub
  • Re: [PR] [CALCITE-7404] Incorrect Field Alias in MongoDB project Stage [calcite] via GitHub
  • Re: [PR] [CALCITE-7404] Incorrect Field Alias in MongoDB project Stage [calcite] via GitHub
  • Re: [PR] [CALCITE-7404] Incorrect Field Alias in MongoDB project Stage [calcite] via GitHub
  • Re: [PR] [CALCITE-7404] Incorrect Field Alias in MongoDB project Stage [calcite] via GitHub
  • Re: [PR] [CALCITE-7404] Incorrect Field Alias in MongoDB project Stage [calcite] via GitHub
  • Re: [PR] [CALCITE-7404] Incorrect Field Alias in MongoDB project Stage [calcite] via GitHub
  • Re: [PR] [CALCITE-7404] Incorrect Field Alias in MongoDB project Stage [calcite] via GitHub
• (calcite) branch main updated: [CALCITE-7400] PruneJoinSingleValue rule causes type mismatch in IN zhenchen
• (calcite) branch main updated: [CALCITE-7394] Nested sub-query with multiple levels of correlation returns incorrect results mbudiu
• [PR] [CALCITE-7400] PruneJoinSingleValue rule causes type mismatch in IN [calcite] via GitHub
  • Re: [PR] [CALCITE-7400] PruneJoinSingleValue rule causes type mismatch in IN [calcite] via GitHub
  • Re: [PR] [CALCITE-7400] PruneJoinSingleValue rule causes type mismatch in IN [calcite] via GitHub
• (calcite) branch main updated: [CALCITE-7385] Support LEFT_MARK type for nested loop join in enumerable convention silun
• (calcite) branch main updated: [CALCITE-7398] Incorrect int cast in VariantNonNull#cast for BIGINT xuzifu666
• [PR] [CALCITE-7385] Support LEFT_MARK type for nested loop join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7385] Support LEFT_MARK type for nested loop join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7385] Support LEFT_MARK type for nested loop join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7385] Support LEFT_MARK type for nested loop join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7385] Support LEFT_MARK type for nested loop join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7385] Support LEFT_MARK type for nested loop join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7385] Support LEFT_MARK type for nested loop join in enumerable convention [calcite] via GitHub
• (calcite) branch main updated: [CALCITE-7320] AggregateProjectMergeRule throws AssertionError when Project maps multiple grouping keys to the same field mbudiu
• (calcite) branch main updated: [CALCITE-7397] Error in simplifying join condition when creating LEFT MARK JOIN silun
• [PR] [CALCITE-7398] Fix incorrect cast in VariantNonNull.cast() for BIGINT [calcite] via GitHub
  • Re: [PR] [CALCITE-7398] Fix incorrect cast in VariantNonNull.cast() for BIGINT [calcite] via GitHub
  • Re: [PR] [CALCITE-7398] Fix incorrect cast in VariantNonNull.cast() for BIGINT [calcite] via GitHub
  • Re: [PR] [CALCITE-7398] Incorrect int cast in VariantNonNull#cast for BIGINT [calcite] via GitHub
  • Re: [PR] [CALCITE-7398] Incorrect int cast in VariantNonNull#cast for BIGINT [calcite] via GitHub
  • Re: [PR] [CALCITE-7398] Incorrect int cast in VariantNonNull#cast for BIGINT [calcite] via GitHub
• (calcite) branch main updated: [CALCITE-5578] RelOptRulesTest testAggregateCaseToFilter optimized plan not semantically equivalent to the original one after conversion xiong
• (calcite) branch main updated: [CALCITE-7396] PruneEmptyRules does not support LEFT_MARK JOIN silun
• [PR] [CALCITE-7397] TopDownGeneralDecorrelator can cause nullable property mismatches [calcite] via GitHub
  • Re: [PR] [CALCITE-7397] TopDownGeneralDecorrelator can cause nullable property mismatches [calcite] via GitHub
  • Re: [PR] [CALCITE-7397] TopDownGeneralDecorrelator can cause nullable property mismatches [calcite] via GitHub
  • Re: [PR] [CALCITE-7397] TopDownGeneralDecorrelator can cause nullable property mismatches [calcite] via GitHub
  • Re: [PR] [CALCITE-7397] TopDownGeneralDecorrelator can cause nullable property mismatches [calcite] via GitHub
  • Re: [PR] [CALCITE-7397] TopDownGeneralDecorrelator can cause nullable property mismatches [calcite] via GitHub
  • Re: [PR] [CALCITE-7397] TopDownGeneralDecorrelator can cause nullable property mismatches [calcite] via GitHub
  • Re: [PR] [CALCITE-7397] TopDownGeneralDecorrelator can cause nullable property mismatches [calcite] via GitHub
  • Re: [PR] [CALCITE-7397] TopDownGeneralDecorrelator can cause nullable property mismatches [calcite] via GitHub
  • Re: [PR] [CALCITE-7397] Error in simplifying join condition when creating LEFT MARK JOIN [calcite] via GitHub
  • Re: [PR] [CALCITE-7397] Error in simplifying join condition when creating LEFT MARK JOIN [calcite] via GitHub
  • Re: [PR] [CALCITE-7397] Error in simplifying join condition when creating LEFT MARK JOIN [calcite] via GitHub
• [PR] [CALCITE-7396] PruneEmptyRules does not support LEFT_MARK JOIN [calcite] via GitHub
  • Re: [PR] [CALCITE-7396] PruneEmptyRules does not support LEFT_MARK JOIN [calcite] via GitHub
  • Re: [PR] [CALCITE-7396] PruneEmptyRules does not support LEFT_MARK JOIN [calcite] via GitHub
  • Re: [PR] [CALCITE-7396] PruneEmptyRules does not support LEFT_MARK JOIN [calcite] via GitHub
  • Re: [PR] [CALCITE-7396] PruneEmptyRules does not support LEFT_MARK JOIN [calcite] via GitHub
  • Re: [PR] [CALCITE-7396] PruneEmptyRules does not support LEFT_MARK JOIN [calcite] via GitHub
• (calcite) branch main updated: [CALCITE-7395] ProjectMergeRule incorrectly merges PROJECTs with correlation variables zhenchen
• [PR] [CALCITE-7395] ProjectMergeRule incorrectly merges PROJECTs with correlation variables [calcite] via GitHub
  • Re: [PR] [CALCITE-7395] ProjectMergeRule incorrectly merges PROJECTs with correlation variables [calcite] via GitHub
  • Re: [PR] [CALCITE-7395] ProjectMergeRule incorrectly merges PROJECTs with correlation variables [calcite] via GitHub
  • Re: [PR] [CALCITE-7395] ProjectMergeRule incorrectly merges PROJECTs with correlation variables [calcite] via GitHub
• [PR] [CALCITE-7394] Nested sub-query with multiple levels of correlation returns incorrect results [calcite] via GitHub
  • Re: [PR] [CALCITE-7394] Nested sub-query with multiple levels of correlation returns incorrect results [calcite] via GitHub
  • Re: [PR] [CALCITE-7394] Nested sub-query with multiple levels of correlation returns incorrect results [calcite] via GitHub
  • Re: [PR] [CALCITE-7394] Nested sub-query with multiple levels of correlation returns incorrect results [calcite] via GitHub
  • Re: [PR] [CALCITE-7394] Nested sub-query with multiple levels of correlation returns incorrect results [calcite] via GitHub
  • Re: [PR] [CALCITE-7394] Nested sub-query with multiple levels of correlation returns incorrect results [calcite] via GitHub
  • Re: [PR] [CALCITE-7394] Nested sub-query with multiple levels of correlation returns incorrect results [calcite] via GitHub
  • Re: [PR] [CALCITE-7394] Nested sub-query with multiple levels of correlation returns incorrect results [calcite] via GitHub
  • Re: [PR] [CALCITE-7394] Nested sub-query with multiple levels of correlation returns incorrect results [calcite] via GitHub
  • Re: [PR] [CALCITE-7394] Nested sub-query with multiple levels of correlation returns incorrect results [calcite] via GitHub
  • Re: [PR] [CALCITE-7394] Nested sub-query with multiple levels of correlation returns incorrect results [calcite] via GitHub
• [PR] [CALCITE-7057] NPE when decorrelating query containing nested correlated subqueries [calcite] via GitHub
  • Re: [PR] [CALCITE-7057] NPE when decorrelating query containing nested correlated subqueries [calcite] via GitHub
  • Re: [PR] [CALCITE-7057] NPE when decorrelating query containing nested correlated subqueries [calcite] via GitHub
  • Re: [PR] [CALCITE-7057] NPE when decorrelating query containing nested correlated subqueries [calcite] via GitHub
  • Re: [PR] [CALCITE-7057] NPE when decorrelating query containing nested correlated subqueries [calcite] via GitHub
  • Re: [PR] [CALCITE-7057] NPE when decorrelating query containing nested correlated subqueries [calcite] via GitHub
  • Re: [PR] [CALCITE-7057] NPE when decorrelating query containing nested correlated subqueries [calcite] via GitHub
  • Re: [PR] [CALCITE-7057] NPE when decorrelating query containing nested correlated subqueries [calcite] via GitHub
  • Re: [PR] [CALCITE-7057] NPE when decorrelating query containing nested correlated subqueries [calcite] via GitHub
  • Re: [PR] [CALCITE-7057] NPE when decorrelating query containing nested correlated subqueries [calcite] via GitHub
  • Re: [PR] [CALCITE-7057] NPE when decorrelating query containing nested correlated subqueries [calcite] via GitHub
• [PR] [CALCITE-5578] RelOptRulesTest testAggregateCaseToFilter optimized pl… [calcite] via GitHub
  • Re: [PR] [CALCITE-5578] RelOptRulesTest testAggregateCaseToFilter optimized pl… [calcite] via GitHub
  • Re: [PR] [CALCITE-5578] RelOptRulesTest testAggregateCaseToFilter optimized pl… [calcite] via GitHub
• (calcite) branch main updated: Add debug log for query plan after decorrelation completion xiong
• [PR] Add test cases for CALCITE-6504 [calcite] via GitHub
  • Re: [PR] Add test cases for CALCITE-6504 [calcite] via GitHub
  • Re: [PR] Add test cases for CALCITE-6504 [calcite] via GitHub
  • Re: [PR] Add test cases for CALCITE-6504 [calcite] via GitHub
  • Re: [PR] Add test cases for CALCITE-6504 [calcite] via GitHub
  • Re: [PR] Add test cases for CALCITE-6504 [calcite] via GitHub
  • Re: [PR] Add test cases for CALCITE-6504 [calcite] via GitHub
  • Re: [PR] [CALCITE-6504] JOIN_SUB_QUERY_TO_CORRELATE/Join SubQueryRemoveRule produces incorrect tree when using correlated sub-query in on clause of equi-join [calcite] via GitHub
  • Re: [PR] [CALCITE-6504] JOIN_SUB_QUERY_TO_CORRELATE/Join SubQueryRemoveRule produces incorrect tree when using correlated sub-query in on clause of equi-join [calcite] via GitHub
• [PR] Add debug log for query plan after decorrelation completion [calcite] via GitHub
  • Re: [PR] Add debug log for query plan after decorrelation completion [calcite] via GitHub
• (calcite) branch main updated: [CALCITE-7379] LHS correlated variables are shadowed by nullable RHS outputs in LEFT JOIN mbudiu
• [PR] [CALCITE-6907] support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-6907] Support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-6907] Support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-7393] Support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-7393] Support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-7393] Support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-7393] Support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-7393] Support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-7393] Support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-7393] Support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-7393] Support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-7393] Support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-7393] Support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-7393] Support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-7393] Support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-7393] Support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-7393] Support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-7393] Support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-7393] Support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-7393] Support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-7393] Support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-7393] Support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-7393] Support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-7393] Support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-7393] Support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-7393] Support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-7393] Support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-7393] Support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-7393] Support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-7393] Support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-7393] Support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-7393] Support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-7393] Support RelDataTypeDigest [calcite] via GitHub
  • Re: [PR] [CALCITE-7393] Support RelDataTypeDigest [calcite] via GitHub
• (calcite) branch main updated: [CALCITE-7388] Redis Adapter operand config should not support empty string xuzifu666
• (calcite) branch main updated: Opened misc and scalar iq files in CoreQuidemTest2 zhenchen
• (calcite) branch main updated: [CALCITE-7391] FILTER_REDUCE_EXPRESSIONS crashes on expression where 123 in (SELECT NULL FROM emps) mbudiu
• (calcite) branch main updated: [CALCITE-7279] ClickHouse dialect should wrap nested JOINs with explicit column aliases mbudiu
• [PR] [CALCITE-7391] FILTER_REDUCE_EXPRESSIONS crashes on expression where … [calcite] via GitHub
  • Re: [PR] [CALCITE-7391] FILTER_REDUCE_EXPRESSIONS crashes on expression where 123 in (SELECT NULL FROM emps) [calcite] via GitHub
  • Re: [PR] [CALCITE-7391] FILTER_REDUCE_EXPRESSIONS crashes on expression where 123 in (SELECT NULL FROM emps) [calcite] via GitHub
• [PR] Opened misc and scalar iq files in CoreQuidemTest2 [calcite] via GitHub
  • Re: [PR] Opened misc and scalar iq files in CoreQuidemTest2 [calcite] via GitHub
  • Re: [PR] Opened misc and scalar iq files in CoreQuidemTest2 [calcite] via GitHub
  • Re: [PR] Opened misc and scalar iq files in CoreQuidemTest2 [calcite] via GitHub
  • Re: [PR] Opened misc and scalar iq files in CoreQuidemTest2 [calcite] via GitHub
  • Re: [PR] Opened misc and scalar iq files in CoreQuidemTest2 [calcite] via GitHub
  • Re: [PR] Opened misc and scalar iq files in CoreQuidemTest2 [calcite] via GitHub
• (calcite) branch main updated: [CALCITE-7389] PruneJoinSingleValue rule causes type mismatch in EXISTS zhenchen
• (calcite) branch main updated: [CALCITE-5740] Support for AggToSemiJoinRule zhenchen
• (calcite) branch main updated: Make SqlValidatorImpl#maybeCast protected to allow using it by child classes snuyanzin
• (calcite) branch main updated: [CALCITE-7382] The TopDownGeneralDecorrelator returns an error result when a subquery contains a LIMIT 1 silun
• (calcite) branch snuyanzin-patch-1 updated (9f1edd3c01 -> a51effc8b3) snuyanzin
• [PR] [CALCITE-7389] PruneJoinSingleValue rule causes type mismatch in EXISTS [calcite] via GitHub
  • Re: [PR] [CALCITE-7389] PruneJoinSingleValue rule causes type mismatch in EXISTS [calcite] via GitHub
  • Re: [PR] [CALCITE-7389] PruneJoinSingleValue rule causes type mismatch in EXISTS [calcite] via GitHub
  • Re: [PR] [CALCITE-7389] PruneJoinSingleValue rule causes type mismatch in EXISTS [calcite] via GitHub
  • Re: [PR] [CALCITE-7389] PruneJoinSingleValue rule causes type mismatch in EXISTS [calcite] via GitHub
  • Re: [PR] [CALCITE-7389] PruneJoinSingleValue rule causes type mismatch in EXISTS [calcite] via GitHub
  • Re: [PR] [CALCITE-7389] PruneJoinSingleValue rule causes type mismatch in EXISTS [calcite] via GitHub
  • Re: [PR] [CALCITE-7389] PruneJoinSingleValue rule causes type mismatch in EXISTS [calcite] via GitHub
  • Re: [PR] [CALCITE-7389] PruneJoinSingleValue rule causes type mismatch in EXISTS [calcite] via GitHub
  • Re: [PR] [CALCITE-7389] PruneJoinSingleValue rule causes type mismatch in EXISTS [calcite] via GitHub
  • Re: [PR] [CALCITE-7389] PruneJoinSingleValue rule causes type mismatch in EXISTS [calcite] via GitHub
  • Re: [PR] [CALCITE-7389] PruneJoinSingleValue rule causes type mismatch in EXISTS [calcite] via GitHub
  • Re: [PR] [CALCITE-7389] PruneJoinSingleValue rule causes type mismatch in EXISTS [calcite] via GitHub
  • Re: [PR] [CALCITE-7389] PruneJoinSingleValue rule causes type mismatch in EXISTS [calcite] via GitHub
  • Re: [PR] [CALCITE-7389] PruneJoinSingleValue rule causes type mismatch in EXISTS [calcite] via GitHub
  • Re: [PR] [CALCITE-7389] PruneJoinSingleValue rule causes type mismatch in EXISTS [calcite] via GitHub
  • Re: [PR] [CALCITE-7389] PruneJoinSingleValue rule causes type mismatch in EXISTS [calcite] via GitHub

• Earlier messages
• Later messages