Re: Expanding the Web of trust in the Calcite community / PGP Key signing

Hi Francis, Yes you are right. To remove the warning the release signing key needs to be either signed directly by myself or transitively through the notion of trust [1]. I am hoping that signing each other's keys will also make the warning disappear along with the other benefits. I am in UTC+2 b

Re: Review Request: CALCITE-5064

I will have another look at CALCITE-4992 in the following days. Best, Stamatis On Mon, Mar 28, 2022 at 7:45 AM James Turton wrote: > Excuse me freeloading on this thread but another PR that originated from > our end (Drill) and is once again ready for review is CALCITE-4992 > (https://github.co

Re: Expanding the Web of trust in the Calcite community / PGP Key signing

Hello, thanks Stamatis for starting this discussion. I agree with your proposals. I'm in UTC+1 right now (UTC in winter). Best, Ruben On Mon, Mar 28, 2022 at 9:22 AM Stamatis Zampetakis wrote: > Hi Francis, > > Yes you are right. To remove the warning the release signing key needs to > be ei

Re: [DISCUSS] Best practice for synchronizing master and site branches

Would it be clearer if we had different API versions on the site? We could have one API link per Calcite version (or at least for the latest X versions) + an API link of the current master head (that could be updated automatically). I think this "multiple API" idea has been already discussed in the

Re: [DISCUSS] Best practice for synchronizing master and site branches

Having multiple APIs versions in the website has been discussed here [1]. Since this work of automation is important and has been postponed many times in the past I think it is important to get something simple to begin with and add "new features" like versioned documentation later on and if there

Re: [DISCUSS] Best practice for synchronizing master and site branches

If all version specific documentation is siloed into their own respective folders for each version, then this will be much easier to automate as we can just simply build and publish the site on every push to master. Each version would be in each folder, with the unreleased version being in th

Re: [DISCUSS] Best practice for synchronizing master and site branches

Hi all, Thanks for the fruitful discussion. It seems there is not a "single formula" that is safe for all scenarios. In addition, it requires some effort to recognize the particular scenario we are in (commits out of order, missing commits, etc.). Sometimes it is not reliable to simply check the

Optimizations of queries containing non-deterministic functions - difference between Calcite and Hive

Hi all, When I read source code from Calcite and Hive, I notice that Hive invests more logic than Calcite in checking whether a function call will result in non-deterministic output. On the other hand, Calcite seems by default to assume that a function is deterministic. Can someone provide any ins

RE: Re: Exception parsing "SELECT @@character_set_server"

Would you be open to a patch to add proper support for this kind of MySQL variables, or do you consider it to be outside the scope of Calcite? On 2022/03/22 21:52:09 Justin Swanhart wrote: > MySQL support two categories of variables, user variables which are > prefixed with the @character and ses

RE: Re: JDBC join order question

Hi Benchao, Thank you so much for the reply! I don't know why I didn't receive the email but I found your answer at the archive website. I tried to add the `JoinConditionPushRule` as you suggested but the filter cannot be pushed from the second join to the first, and the code throws the same erro

Re: JDBC join order question

Xiaoying, I know why you didn’t receive the email. Your reply went through moderation, which indicates that you are not subscribed to dev@calcite. Please subscribe. > On Mar 28, 2022, at 11:10 AM, Xiaoying Wang > wrote: > > Hi Benchao, > > Thank you so much for the reply! I don't know why I

Re: Exception parsing "SELECT @@character_set_server"

A couple more questions. Do these variables have well-defined types? Do they have to be valid expressions? If the answer to either of these questions is ’no’ then maybe they are what Oracle calls ’substitution variables’. Substitution variables have a behavior more like C macros than real variab

Re: Exception parsing "SELECT @@character_set_server"

We’d be open to adding support, but it must not be the default behavior, so there will be need to be some kind of flag. Can you log a JIRA case with the subject ’Support variables with “@" and “@@" prefixes (like MySQL)’. Then we can write a specification and you can submit a pull request. At

Re: JDBC join order question

Hi Julian, Oh, I see. Thank you for the hint! I just subscribed to the list. Best, Xiaoying On Mon, Mar 28, 2022 at 11:53 AM Julian Hyde wrote: > Xiaoying, I know why you didn’t receive the email. Your reply went through > moderation, which indicates that you are not subscribed to dev@calcite

Re: Contributing a custom SQL dialect of Firebolt to Calcite

Gentle reminder! We are expecting a response so that we can move ahead with this potential contribution. Thanks & Regards, Raghav Sharma | SDE 1 | Data Engineering M: +91 7087637086 I Mail: ragh...@sigmoidanalytics.com On Thu, Mar 24, 2022 at 3:47 PM Raghav Sharma wr

Re: Contributing a custom SQL dialect of Firebolt to Calcite

You did receive a response[1]. But you didn't receive it because you are not subscribed to this list. Please subscribe[2]. Julian [1] https://lists.apache.org/thread/39obrhwpd95bvhc9sb2n4z6zrrwbc21x [2] https://calcite.apache.org/community/#mailing-lists On Mon, Mar 28, 2022 at 1:11 PM Raghav S

Re: Contributing a custom SQL dialect of Firebolt to Calcite

Thank you for the clarification Julian. I will send a mail to dev-subscr...@calcite.apache.org for subscribing. On Tue, 29 Mar 2022 at 1:45 AM Julian Hyde wrote: > You did receive a response[1]. But you didn't receive it because you > are not subscribed to this list. Please subscribe[2]. > > J

Re: [DISCUSS] Best practice for synchronizing master and site branches

To respond to Stamatis’ query: I do use the generated javadoc. For example, if I am talking about a connection property I might email the following link: https://calcite.apache.org/javadocAggregate/org/apache/calcite/config/CalciteConnectionProperty.html#FORCE_DECORRELATE

Re: Exception parsing "SELECT @@character_set_server"

Hi, They are strongly typed. Many are strings that can only be set to certain legal values (like optmizer_switch). These variables can also be used in MySQL SET statements. Note that there is no way to easily type the variables except by examining their values, in the performance_schema (at lea

Re: Exception parsing "SELECT @@character_set_server"

Thanks, Justin. For now, it’s enough to know that they have types. If we hit the requirement that Calcite’s validator needs to know that (say) there is a variable called ‘FOO’ and its type is ’TIMESTAMP’ then we can use a plug-in map or even the SqlOperatorTable (modeling variables as functions

Re: [DISCUSS] Best practice for synchronizing master and site branches

Hey Julian, All very good points. I can definitely see the utility of the javadocs. The analogue in Go would be godoc, with the difference being that the godoc server automatically crawls the code across all versions to generate the documentation. As an example, see the godoc for protobuf [1

Calcite jars with shaded guava

Hi, I am trying to upgrade calcite in the druid codebase. But because of the guava version mismatch between druid and calcite, a straightforward upgrade is not possible. We also can't upgrade guava in druid itself since Hadoop-2 still requires old guava jars. As a workaround, I created shaded artif

[jira] [Created] (CALCITE-5065) Update phoenixdb information on website

Istvan Toth created CALCITE-5065: Summary: Update phoenixdb information on website Key: CALCITE-5065 URL: https://issues.apache.org/jira/browse/CALCITE-5065 Project: Calcite Issue Type: Task

[jira] [Created] (CALCITE-5066) Support variables with “@" and “@@" prefixes (like MySQL)

Adolfo Ochagavía created CALCITE-5066: - Summary: Support variables with “@" and “@@" prefixes (like MySQL) Key: CALCITE-5066 URL: https://issues.apache.org/jira/browse/CALCITE-5066 Project: Calcite

[jira] [Created] (CALCITE-5067) Support using "LANGUAGE" as a variable name (like MySQL)

Adolfo Ochagavía created CALCITE-5067: - Summary: Support using "LANGUAGE" as a variable name (like MySQL) Key: CALCITE-5067 URL: https://issues.apache.org/jira/browse/CALCITE-5067 Project: Calcite