commits  

Messages by Thread

• • Re: [PR] [CALCITE-7357] Introduce the implementation of rex operator IS DISTINCT FROM [calcite] via GitHub
  • Re: [PR] [CALCITE-7357] Introduce the implementation of rex operator IS DISTINCT FROM [calcite] via GitHub
  • Re: [PR] [CALCITE-7357] Introduce the implementation of rex operator IS DISTINCT FROM [calcite] via GitHub
  • Re: [PR] [CALCITE-7357] Introduce the implementation of rex operator IS DISTINCT FROM [calcite] via GitHub
  • Re: [PR] [CALCITE-7357] Introduce the implementation of rex operator IS DISTINCT FROM [calcite] via GitHub
  • Re: [PR] [CALCITE-7357] Introduce the implementation of rex operator IS DISTINCT FROM [calcite] via GitHub
  • Re: [PR] [CALCITE-7357] Introduce the implementation of rex operator IS DISTINCT FROM [calcite] via GitHub
  • Re: [PR] [CALCITE-7357] Introduce the implementation of rex operator IS DISTINCT FROM [calcite] via GitHub
  • Re: [PR] [CALCITE-7357] Introduce the implementation of rex operator IS DISTINCT FROM [calcite] via GitHub
  • Re: [PR] [CALCITE-7357] Introduce the implementation of rex operator IS DISTINCT FROM [calcite] via GitHub
  • Re: [PR] [CALCITE-7357] Introduce the implementation of rex operator IS DISTINCT FROM [calcite] via GitHub
  • Re: [PR] [CALCITE-7357] Introduce the implementation of rex operator IS DISTINCT FROM [calcite] via GitHub
  • Re: [PR] [CALCITE-7357] Introduce the implementation of rex operator IS DISTINCT FROM [calcite] via GitHub
• [PR] [CALCITE-7355] RelToSqlConverter throws exception when the join condi… [calcite] via GitHub
  • Re: [PR] [CALCITE-7355] RelToSqlConverter throws exception when the join condi… [calcite] via GitHub
  • Re: [PR] [CALCITE-7355] RelToSqlConverter throws exception when the join condi… [calcite] via GitHub
  • Re: [PR] [CALCITE-7355] RelToSqlConverter throws exception when the join condi… [calcite] via GitHub
  • Re: [PR] [CALCITE-7355] RelToSqlConverter throws exception when the join condi… [calcite] via GitHub
  • Re: [PR] [CALCITE-7355] RelToSqlConverter throws exception when the join condi… [calcite] via GitHub
  • Re: [PR] [CALCITE-7355] RelToSqlConverter throws exception when the join condi… [calcite] via GitHub
  • Re: [PR] [CALCITE-7355] RelToSqlConverter throws exception when the join condi… [calcite] via GitHub
  • Re: [PR] [CALCITE-7355] RelToSqlConverter throws exception when the join condi… [calcite] via GitHub
• [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
  • Re: [PR] [CALCITE-7315] Support LEFT_MARK type for hash join in enumerable convention [calcite] via GitHub
• [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
  • Re: [PR] [CALCITE-4765] Complex correlated EXISTS sub-queries used as scalar subqueries can return wrong results [calcite] via GitHub
• [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
  • Re: [PR] [CALCITE-5093] Quantified comparison operators (e.g. ANY) should support ARRAY arguments [calcite] via GitHub
• [PR] [CALCITE-5597] SELECT DISTINCT query with ORDER BY column will get error result error result [calcite] via GitHub
  • Re: [PR] [CALCITE-5597] SELECT DISTINCT query with ORDER BY column will get error result error result [calcite] via GitHub
  • Re: [PR] [CALCITE-5597] SELECT DISTINCT query with ORDER BY column will get error result error result [calcite] via GitHub
  • Re: [PR] [CALCITE-5597] SELECT DISTINCT query with ORDER BY column will get error result error result [calcite] via GitHub
  • Re: [PR] [CALCITE-5597] SELECT DISTINCT query with ORDER BY column will get error result error result [calcite] via GitHub
  • Re: [PR] [CALCITE-5597] SELECT DISTINCT query with ORDER BY column will get error result error result [calcite] via GitHub
  • Re: [PR] [CALCITE-5597] SELECT DISTINCT query with ORDER BY column will get error result error result [calcite] via GitHub
  • Re: [PR] [CALCITE-5597] SELECT DISTINCT query with ORDER BY column will get error result error result [calcite] via GitHub
  • Re: [PR] [CALCITE-5597] SELECT DISTINCT query with ORDER BY column will get error result error result [calcite] via GitHub
• (calcite) branch main updated: [CALCITE-7351] Make getMaxNumericScale() and getMaxNumericPrecision() final asolimando
• (calcite) branch main updated: [CALCITE-7337] Add age function (enabled in PostgreSQL library) zhenchen
• (calcite) branch main updated: [CALCITE-7348] Remove redundant extraction correlation variables when Trim Project Fields xiong
• (calcite) branch main updated: [CALCITE-6066] Add HYPOT function (enabled in Spark library) xuzifu666
• (calcite-site) branch main updated: Website deployed from calcite@533a61520bbb77cab331ce931da8ee921891f144 asf-ci-deploy
• (calcite) branch site updated: Site: Add Thomas Rebele as committer github-bot
• (calcite) branch main updated: Site: Add Thomas Rebele as committer thomasrebele
• (calcite) branch main updated: [CALCITE-7352] Incorrect SqlLibrary enum value used in ClickHouse SQL test xuzifu666
• [PR] [CALCITE-7352] Incorrect SqlLibrary enum value used in ClickHouse SQL test [calcite] via GitHub
  • Re: [PR] [CALCITE-7352] Incorrect SqlLibrary enum value used in ClickHouse SQL test [calcite] via GitHub
  • Re: [PR] [CALCITE-7352] Incorrect SqlLibrary enum value used in ClickHouse SQL test [calcite] via GitHub
  • Re: [PR] [CALCITE-7352] Incorrect SqlLibrary enum value used in ClickHouse SQL test [calcite] via GitHub
• (calcite) branch main updated: [CALCITE-7350] Missing allowEmptyOutputFromRewrite parameter in TopDownGeneralDecorrelator.unnestInternal silun
• [PR] [CALCITE-6066] Add HYPOT function (enabled in Spark library) [calcite] via GitHub
  • Re: [PR] [CALCITE-6066] Add HYPOT function (enabled in Spark library) [calcite] via GitHub
  • Re: [PR] [CALCITE-6066] Add HYPOT function (enabled in Spark library) [calcite] via GitHub
  • Re: [PR] [CALCITE-6066] Add HYPOT function (enabled in Spark library) [calcite] via GitHub
  • Re: [PR] [CALCITE-6066] Add HYPOT function (enabled in Spark library) [calcite] via GitHub
  • Re: [PR] [CALCITE-6066] Add HYPOT function (enabled in Spark library) [calcite] via GitHub
  • Re: [PR] [CALCITE-6066] Add HYPOT function (enabled in Spark library) [calcite] via GitHub
  • Re: [PR] [CALCITE-6066] Add HYPOT function (enabled in Spark library) [calcite] via GitHub
  • Re: [PR] [CALCITE-6066] Add HYPOT function (enabled in Spark library) [calcite] via GitHub
  • Re: [PR] [CALCITE-6066] Add HYPOT function (enabled in Spark library) [calcite] via GitHub
  • Re: [PR] [CALCITE-6066] Add HYPOT function (enabled in Spark library) [calcite] via GitHub
• [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
  • Re: [PR] [CALCITE-6829] MSSQL dialect incorrectly translates of SELECT TRUE [calcite] via GitHub
• [PR] [CALCITE-7351] Make getMaxNumericScale() and getMaxNumericPrecision()… [calcite] via GitHub
  • Re: [PR] [CALCITE-7351] Make getMaxNumericScale() and getMaxNumericPrecision()… [calcite] via GitHub
  • Re: [PR] [CALCITE-7351] Make getMaxNumericScale() and getMaxNumericPrecision()… [calcite] via GitHub
  • Re: [PR] [CALCITE-7351] Make getMaxNumericScale() and getMaxNumericPrecision()… [calcite] via GitHub
• (calcite) branch main updated: [CALCITE-5733] Simplify "a = ARRAY[1,2] AND a = ARRAY[2,3]" to "false" zhenchen
• [PR] [CALCITE-7350] Missing allowEmptyOutputFromRewrite parameter in TopDownGeneralDecorrelator.unnestInternal [calcite] via GitHub
  • Re: [PR] [CALCITE-7350] Missing allowEmptyOutputFromRewrite parameter in TopDownGeneralDecorrelator.unnestInternal [calcite] via GitHub
  • Re: [PR] [CALCITE-7350] Missing allowEmptyOutputFromRewrite parameter in TopDownGeneralDecorrelator.unnestInternal [calcite] via GitHub
  • Re: [PR] [CALCITE-7350] Missing allowEmptyOutputFromRewrite parameter in TopDownGeneralDecorrelator.unnestInternal [calcite] via GitHub
  • Re: [PR] [CALCITE-7350] Missing allowEmptyOutputFromRewrite parameter in TopDownGeneralDecorrelator.unnestInternal [calcite] via GitHub
  • Re: [PR] [CALCITE-7350] Missing allowEmptyOutputFromRewrite parameter in TopDownGeneralDecorrelator.unnestInternal [calcite] via GitHub
  • Re: [PR] [CALCITE-7350] Missing allowEmptyOutputFromRewrite parameter in TopDownGeneralDecorrelator.unnestInternal [calcite] via GitHub
  • Re: [PR] [CALCITE-7350] Missing allowEmptyOutputFromRewrite parameter in TopDownGeneralDecorrelator.unnestInternal [calcite] via GitHub
• Re: [PR] [CALCITE-7270] Add support for a DIVIDE_0_NULL operation [calcite] via GitHub
  • Re: [PR] [CALCITE-7270] Add support for a DIVIDE_0_NULL operation [calcite] via GitHub
  • Re: [PR] [CALCITE-7270] Add support for a DIVIDE_0_NULL operation [calcite] via GitHub
  • Re: [PR] [CALCITE-7270] Add support for a DIVIDE_0_NULL operation [calcite] via GitHub
  • Re: [PR] [CALCITE-7270] Add support for a DIVIDE_0_NULL operation [calcite] via GitHub
• (calcite) branch main updated: [CALCITE-7349] Upgrade the types of FETCH and OFFSET in SORT to BigDecimal zhenchen
• (calcite) branch main updated: Move ExpandDisjunctionForJoinInputsRule test from planner.iq to hep.iq zhenchen
• [PR] [CALCITE-7349] Upgrade the types of FETCH and OFFSET in SORT to BigDecimal [calcite] via GitHub
  • Re: [PR] [CALCITE-7349] Upgrade the types of FETCH and OFFSET in SORT to BigDecimal [calcite] via GitHub
  • Re: [PR] [CALCITE-7349] Upgrade the types of FETCH and OFFSET in SORT to BigDecimal [calcite] via GitHub
• [PR] Move ExpandDisjunctionForJoinInputsRule test from planner.iq to hep.iq [calcite] via GitHub
  • Re: [PR] Move ExpandDisjunctionForJoinInputsRule test from planner.iq to hep.iq [calcite] via GitHub
  • Re: [PR] Move ExpandDisjunctionForJoinInputsRule test from planner.iq to hep.iq [calcite] via GitHub
  • Re: [PR] Move ExpandDisjunctionForJoinInputsRule test from planner.iq to hep.iq [calcite] via GitHub
  • Re: [PR] Move ExpandDisjunctionForJoinInputsRule test from planner.iq to hep.iq [calcite] via GitHub
  • Re: [PR] Move ExpandDisjunctionForJoinInputsRule test from planner.iq to hep.iq [calcite] via GitHub
• [PR] [CALCITE-7348] Remove redundant extraction correlation variables when… [calcite] via GitHub
  • Re: [PR] [CALCITE-7348] Remove redundant extraction correlation variables when… [calcite] via GitHub
  • Re: [PR] [CALCITE-7348] Remove redundant extraction correlation variables when… [calcite] via GitHub
  • Re: [PR] [CALCITE-7348] Remove redundant extraction correlation variables when… [calcite] via GitHub
  • Re: [PR] [CALCITE-7348] Remove redundant extraction correlation variables when… [calcite] via GitHub
  • Re: [PR] [CALCITE-7348] Remove redundant extraction correlation variables when… [calcite] via GitHub
• (calcite) branch main updated: [CALCITE-7274] RexFieldAccess has wrong index when use trim unused fields xiong
• (calcite) branch main updated: [CALCITE-7346] Prevent overflow in metadata row-count when LIMIT/OFFSET literal exceeds Long range zhenchen
• Re: [PR] [CALCITE-7304] Floor/Ceil can not simplify with WEEK TimeUnit [calcite] via GitHub
  • Re: [PR] [CALCITE-7304] Floor/Ceil can not simplify with WEEK TimeUnit [calcite] via GitHub
  • Re: [PR] [CALCITE-7304] Floor/Ceil can not simplify with WEEK TimeUnit [calcite] via GitHub

• Earlier messages
• Later messages