[jira] [Created] (CALCITE-5043) GROUP BY alias or SELECT field should be determined by using sql dialect when alias and field are same

yanjing.wang created CALCITE-5043: - Summary: GROUP BY alias or SELECT field should be determined by using sql dialect when alias and field are same Key: CALCITE-5043 URL: https://issues.apache.org/jira/browse/CALC

[jira] [Created] (CALCITE-5044) OrderBy constant executing RelToSql ambiguously

Xurenhe created CALCITE-5044: Summary: OrderBy constant executing RelToSql ambiguously Key: CALCITE-5044 URL: https://issues.apache.org/jira/browse/CALCITE-5044 Project: Calcite Issue Type: Impro

[jira] [Created] (CALCITE-5045) Alias within GroupingSets throws type mis-match exception

yanjing.wang created CALCITE-5045: - Summary: Alias within GroupingSets throws type mis-match exception Key: CALCITE-5045 URL: https://issues.apache.org/jira/browse/CALCITE-5045 Project: Calcite

[jira] [Created] (CALCITE-5046) SqlTypeFactorylmpl#leastRestrictiveByCast incorrect results with MAP types

Francesco Guardiani created CALCITE-5046: Summary: SqlTypeFactorylmpl#leastRestrictiveByCast incorrect results with MAP types Key: CALCITE-5046 URL: https://issues.apache.org/jira/browse/CALCITE-5046

Re: [RESULT] [VOTE] Release apache-calcite-1.30.0 (release candidate 2)

Liya, The PR has a couple of LGTMs, and it has passed my internal tests. I think you should cherry-pick it into master, revise release notes, and start a new RC. (Will require a small force-push.) Julian On 2022/03/15 05:50:30 Fan Liya wrote: > Hi Julian, > > Thanks for your feedback and you

Setting the "defaultSchema" of a live CalciteConnection?

I have a scenario in which I have a rootSchema that holds multiple datasource schemas There's a tool I'd like to integrate it with, but it can't handle (catalog -> schema -> schema) structure I figured an easy way around this would be to iterate the names of the datasource schemas, and then and t

Re: Is the web broken?

Hi Gavin, Do you have any idea why hive.apache.org is broken after the hive-site change? Thanks, Chao On Thu, Mar 10, 2022 at 7:16 PM Chao Sun wrote: > > Sorry, we are in the process of migrating to hive-site.git from CMS. There > are a few issues to be fixed and I’m talking with ASF infra on

Re: Setting the "defaultSchema" of a live CalciteConnection?

An ancestor project of Calcite, Eigenbase (aka Farrago) used to have a SET SCHEMA command. It would be nice if we added that back. (Maybe only in the “server” module, since in “core” the connections are stateless.) I’m a bit surprised that "CalciteConnection.setSchema(String)" doesn’t work. Put

Re: [RESULT] [VOTE] Release apache-calcite-1.30.0 (release candidate 2)

Sure. Thanks for your kind reminder. I will do it and prepare a new build ASAP. Best, Liya Fan Julian Hyde 于2022年3月16日周三 01:38写道： > Liya, > > The PR has a couple of LGTMs, and it has passed my internal tests. I think > you should cherry-pick it into master, revise release notes, and start a >

Build failed in Jenkins: Calcite » Calcite-snapshots #88

See Changes: [fan_li_ya] [CALCITE-4976] Release Calcite 1.30.0 -- [...truncated 232.25 KB...]  3.5sec, org.apache.calcite.test.Fixt

[VOTE] Release Apache Calcite 1.30.0 (release candidate 3)

Hi all, I have created a build for Apache Calcite 1.30.0, release candidate 3. Thanks to everyone who has contributed to this release. You can read the release notes here: https://github.com/apache/calcite/blob/calcite-1.30.0-rc3/site/_docs/history.md The commit to be voted upon: https://gitbox

[jira] [Created] (CALCITE-5047) avatica-server integrated with spring-boot

itxiangkui created CALCITE-5047: --- Summary: avatica-server integrated with spring-boot Key: CALCITE-5047 URL: https://issues.apache.org/jira/browse/CALCITE-5047 Project: Calcite Issue Type: Imp

Re: [VOTE] Release Apache Calcite 1.30.0 (release candidate 3)

Thanks, Liya! My vote is: +1 (binding) - Verified GPG signature - OK - Verified SHA512 - OK - Checked release notes on tag (https://github.com/apache/calcite/blob/calcite-1.30.0-rc3/site/_docs/history.md) - OK - Ran tests (gradle check) - OK - Ran failing test in rc2 (gradle cleanTest :core:t