Re: squashing commit already in upstream

2023-12-11 Thread Michael Mior
Since this would require a force push, I would suggest fetching from the remote first and then making sure you rebase if necessary while squashing then use --force-with-lease instead of --force to make sure any changes that may have been pushed are incorporated. If you do end up seeing that

Re: Reminder about ASF release approval

2023-12-11 Thread Ran Tao
Thanks to @Stamatis for reminding us of this. It will help us, especially those new to the ASF community and open source, familiar with the process and rules of vote. Best Regards, Ran Tao Stamatis Zampetakis 于2023年12月11日周一 17:29写道: > Hey everyone, > > The community is growing and more and

[ANNOUNCE] Apache Calcite Avatica Go 5.3.0 released

2023-12-11 Thread Francis Chuang
The Apache Calcite team is pleased to announce the release of Apache Calcite Avatica Go 5.3.0. Avatica is a framework for building database drivers. Avatica defines a wire API and serialization mechanism for clients to communicate with a server as a proxy to a database. The reference Avatica

Re: [DISCUSS] Using easy-fix label in JIRA

2023-12-11 Thread Stamatis Zampetakis
In our doc page we are already suggesting the use of the "newbie" label [1]. If someone has cycles to go over JIRA issues and label them accordingly that would be indeed very helpful for newcomers. A few months ago, I did a quick cross project JIRA search for similar labels and it appears that

Reminder about ASF release approval

2023-12-11 Thread Stamatis Zampetakis
Hey everyone, The community is growing and more and more people get involved in testing and voting for releases, which is great for the project. For this purpose, I would like to send a brief reminder around the ASF release policy [1] especially the part about approving releases. I would

Calcite tables which support multiple data retrieval patterns

2023-12-11 Thread Austin Richardson
Hello, My team is working on a feature to add a general “base table” for a collection of Calcite tables in our service. Something we’ve come across is that different tables will have different supported data retrieval patterns, which we’ve been referring to as “indices”. For example, assume we

Re: [DISCUSS] Using easy-fix label in JIRA

2023-12-11 Thread Jiajun Xie
Thanks Stamatis! In fact, the label name is not important to me. We haven't added such a tag for a long time, so I completely forgot about it As you said, I will continue to use the newbie[1] label. [1]

Re: Calcite tables which support multiple data retrieval patterns

2023-12-11 Thread Julian Hyde
PS Austin, You and the people on the cc: list should subscribe to dev@calcite. It will allow you to post without moderation (which often adds a delay of several hours) and will allow you to receive replies. > On Dec 11, 2023, at 12:05 PM, Julian Hyde wrote: > > Thanks for starting this

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

2023-12-11 Thread Apache Jenkins Server
See Changes: [mbudiu] [MINOR] Better message when no corresponding example -- [...truncated 129.22 KB...]

Re: Calcite tables which support multiple data retrieval patterns

2023-12-11 Thread Julian Hyde
Thanks for starting this conversation. I believe we should be looking for common patterns and devising ways to solve them using relational algebra. (Because that’s the hammer that we have in Calcite… and it’s a very powerful hammer. For example, we can represent all kinds of materialized

Jenkins build is back to normal : Calcite » Calcite-snapshots #727

2023-12-11 Thread Apache Jenkins Server
See