Community and News pages "not secure", according to Chrome

When I open https://calcite.apache.org/news/ or https://calcite.apache.org/community/ pages in Chrome, I get an (i) to the left of the URL bar with the message “Your connection to this site is not fully secure” and a

[jira] [Created] (CALCITE-3387) Query with GROUP BY and JOIN ... USING wrongly fails with "Column 'DEPTNO' is ambiguous" error

Julian Hyde created CALCITE-3387: Summary: Query with GROUP BY and JOIN ... USING wrongly fails with "Column 'DEPTNO' is ambiguous" error Key: CALCITE-3387 URL: https://issues.apache.org/jira/browse/CA

Re: Ignite community is building Calcite-based prototype

Denis, I’ve been a follower and admirer of Ignite for several years, so I am delighted that you are considering Calcite. Ask questions on the dev list, log JIRA cases if you find them, and we’ll do our best to help. I’d like to bring to your attention RelBuilder. Some people want to go from

Re: Volcano Optimizer JDBC Table Scan -> Join

No need to apologize! We really appreciate you following up and saying you found a solution. Your solution may help someone else. Julian > On Oct 2, 2019, at 9:34 AM, Madhav Suresh wrote: > > I apologize for the immediate follow up, however, I found out my issue was > not adding the

[jira] [Created] (CALCITE-3383) Allow plural time units in interval literals

Julian Hyde created CALCITE-3383: Summary: Allow plural time units in interval literals Key: CALCITE-3383 URL: https://issues.apache.org/jira/browse/CALCITE-3383 Project: Calcite Issue Type

Re: [DISCUSS] Small contributions

5:56 PM >> To: dev@calcite.apache.org >> Subject: Re: [DISCUSS] Small contributions >> >> I presume 3rd party library upgrades should go through regular process >> (jira/PR etc.) ? >> >> Dependency upgrade is not considered "small change" since i

Re: [DISCUSS] Small contributions

gt; >> Francis >> >> On 26/09/2019 10:46 am, Michael Mior wrote: >>> I have mixed feelings about this, because on one hand, I'd like to >>> have these things corrected but on the other hand, we're already >>> bogged down with PRs. Perhaps a good com

[DISCUSS] Small contributions

I noticed this exchange in https://github.com/apache/calcite/pull/1475: > Q. Just curious, does Calcite accept hotfix style PR that fixes typos, > comments, etc.? > A. As long as they are large enough. But for 1 line typo fix, it is not worth >

[jira] [Created] (CALCITE-3369) In LatticeSuggester, recommend lattices based on UNION queries

Julian Hyde created CALCITE-3369: Summary: In LatticeSuggester, recommend lattices based on UNION queries Key: CALCITE-3369 URL: https://issues.apache.org/jira/browse/CALCITE-3369 Project: Calcite

Re: Integrating Calcite, Omid, Avatica, Avro, and Kafka

o decide > if what is posted is still relevant. We could perhaps include a > disclaimer. I think it's useful for newcomers to see the activity > happening around Calcite. > -- > Michael Mior > mm...@apache.org > > Le lun. 23 sept. 2019 à 18:06, Julian Hyde a écrit : >> >

Re: Trivial query simplification

A few thoughts on this. 0. I am surprised that this simplification does not happen, and I think we should do it. Specifically, "filter(x = 0 and x is not null)" should simplify to “filter(x = 0)”. 1. Enrico, please log a JIRA case now, and transcribe the key points of this discussion into

Re: Integrating Calcite, Omid, Avatica, Avro, and Kafka

A section of the web site might take quite a bit of curation, because these links go out of date. Also, we might find ourselves asked to endorse companies and products, which we shouldn’t be doing. I think a reasonable compromise is to use the @ApacheCalcite twitter account to forward

Re: [calcite] annotated tag calcite-1.21.1-looker created (now a5db2b6)

at a5db2b6 (tag) > tagging 069e7970ef13d6dc4a5aa015dcf01d0106f336b1 (commit) > replaces calcite-1.21.0 > by Julian Hyde > on Fri Sep 20 13:33:37 2019 -0700 > > - Log - > [maven-re

Re: Query Compilation happening more often then expected

See my comments in https://issues.apache.org/jira/browse/CALCITE-963 . > On Sep 18, 2019, at 1:58 PM, Scott Reynolds wrote: > > Hi all, > > I have submitted my pull request in github and wrote up a design document > as a comment on

[jira] [Created] (CALCITE-3361) Add a test that parses and validates a SQL statement with every built-in Redshift function

Julian Hyde created CALCITE-3361: Summary: Add a test that parses and validates a SQL statement with every built-in Redshift function Key: CALCITE-3361 URL: https://issues.apache.org/jira/browse/CALCITE-3361

Re: [DISCUSS] Release apache-calcite-1.21.0 (release candidate 1)

Stamatis, Can you mark 1.21 as released in JIRA [1]. I don’t recall whether we ever made officially added this task to an RM’s responsibilities. I don’t mind doing it if you don’t have karma. Thank you, again, for being RM. Julian [1]

Re: Query Compilation happening more often then expected

t this should not be a general issue with the > approach, or? > > JulianF > > Am 16.09.19, 23:36 schrieb "Julian Hyde" : > >I found evidence that MSSQL[1] and Sybase ASE[2] do it. > >I agree, it's not a free lunch. For instance, if a column has a >

Re: Query Compilation happening more often then expected

ction, histograms, and other optimization techniques would be > impossible) > while leaving its configuration to the end-user may not be a > straightforward decision. > > On Sat, Sep 14, 2019 at 4:29 PM Julian Hyde wrote: > > > The idea of converting literals into bind variables i

Re: auto-format or fix checkstyle by maven command

I’m sorry that we do not have the technology to auto-correct. People also complain that there are coding standards that are not captured in check style rules, so we are caught between a rock and a hard place. I agree, something like https://github.com/editorconfig/editorconfig/issues/231

Re: Query Compilation happening more often then expected

The idea of converting literals into bind variables is called “hoisting”. We had the idea a while ago but have not implemented it. https://issues.apache.org/jira/browse/CALCITE-963 Until that feature is implemented, you will need to create bind variables explicitly, and bind them before

Re: percentile_cont function -- can't get my query to parse

I don't think PERCENTILE_CONT is implemented. It appears in reference.html because it is a keyword recognized by the parser, but we have not fully implemented it. See https://issues.apache.org/jira/browse/CALCITE-1473. On Fri, Sep 13, 2019 at 4:18 PM Scott Reynolds wrote: > > Sorry for such a

[jira] [Created] (CALCITE-3344) In JDBC adapter, generate "SELECT TOP(n)" for MSSQL 2008 and earlier

Julian Hyde created CALCITE-3344: Summary: In JDBC adapter, generate "SELECT TOP(n)" for MSSQL 2008 and earlier Key: CALCITE-3344 URL: https://issues.apache.org/jira/browse/CALCITE-3344

Re: [DISCUSS] Release apache-calcite-1.21.0 (release candidate 1)

Yes, I screwed up. Everyone who voted screwed up. I should have voted ‘-1’ because the hash of the artifacts I got from svn did not match the hash in the email. Let’s all do better next time. Still, no harm done. We know now that we were voting on the correct artifacts. We have a valid

Re: Appropriate query syntax for table-value function windowing (e.g. CALCITE-3272)

a better idea?). Note that I wrote a unit test in > PlannerTest to identify blockers from parser to logical plan generation. > > > -Rui > > > > > On Fri, Sep 6, 2019 at 9:23 AM Julian Hyde wrote: > >> To be pedantic. Note that “strings” in SQL are called c

Re: JavaScript Avatica client

I have to say… if you wish to contribute this, we would definitely consider it. It would not be the first client in a non-JVM language: Francis wrote the Go driver and now it is part of Calcite/Avatica. Julian > On Sep 10, 2019, at 3:03 AM, Francis Chuang wrote: > > Hi Gabriel, > > It's

Re: Issues in exposing data via TableFunction vs TableMacro

I always thought of a table function as a lightweight relational operator. You could write your own UNION function, for instance. But the moment you want it to start participating in algebraic rewrites - if you want to push filters through it, for instance - then you had better make it into a

Re: Meetup / Hackathon

You should go to the speakers’ dinner; I hope you were invited. I’m just boarding in SFO so I’ll miss most of the speakers’ dinner. Did you get the invite to the ApacheCon slack? Let’s communicate there. Julian > On Sep 9, 2019, at 16:40, Julian Feinauer > wrote: > > Hi all, > I have my

Re: [VOTE] Release apache-calcite-1.21.0 (release candidate 1)

+1 (binding) Checked LICENSE, NOTICE, checksums, compiled and ran tests on JDK 11/Ubuntu, ran RAT. Checked that tar contents match git commit. One minor thing: I was surprised that commit adc1532de does not have tag calcite-1.21.0. Not a blocker for the release, but worth fixing. The release

Re: [VOTE] Release apache-calcite-1.21.0 (release candidate 1)

Julian, It’s not one that I’ve seen before. Please log a JIRA and describe it as intermittent. Someone will find & comment on it if it happens to them. > On Sep 9, 2019, at 7:55 AM, Julian Feinauer > wrote: > > Hi Stamatis, > > thank you for your effort! > > +1 (non-binding) > > I found

Re: Meetup / Hackathon

I'm in Vegas Mon evening - Thu lunchtime. Would love to hang out and write code. IMHO, conferences are for "conferring" - chatting in corridors, and occasionally in bars - more than they are about attending talks. Who else is going? Julian On Fri, Sep 6, 2019 at 10:58 PM Julian Feinauer

[jira] [Created] (CALCITE-3328) Immutable beans, powered by reflection

Julian Hyde created CALCITE-3328: Summary: Immutable beans, powered by reflection Key: CALCITE-3328 URL: https://issues.apache.org/jira/browse/CALCITE-3328 Project: Calcite Issue Type: Bug

[jira] [Created] (CALCITE-3327) Simplify SqlValidatorTest by replacing 'boolean typeCoercion' parameter with fluent method 'Sql.withTypeCoercion(boolean)'

Julian Hyde created CALCITE-3327: Summary: Simplify SqlValidatorTest by replacing 'boolean typeCoercion' parameter with fluent method 'Sql.withTypeCoercion(boolean)' Key: CALCITE-3327 URL: https

[jira] [Created] (CALCITE-3326) SQL with invalid function throws NullPointerException if typeCoercion is disabled

Julian Hyde created CALCITE-3326: Summary: SQL with invalid function throws NullPointerException if typeCoercion is disabled Key: CALCITE-3326 URL: https://issues.apache.org/jira/browse/CALCITE-3326

Re: Appropriate query syntax for table-value function windowing (e.g. CALCITE-3272)

AL))" now. > > > -Rui > >> On Wed, Sep 4, 2019 at 8:03 PM Julian Hyde wrote: >> >> Maybe they’re keywords? If so does it help to include them in >> double-quotes? e.g. >> >> myFun(“TABLE” => ’myTable’, >> “DESCRIPTOR” => ‘

Re: [VOTE] Release apache-calcite-1.21.0 (release candidate 0)

Darn it. I had already started on this, and put in a couple of hours of work cleaning things up. I've pushed my changes anyway, to my branch https://github.com/julianhyde/calcite/tree/branch-1.21. I also made some copy edits to the release notes. Stamatis can cherry-pick it all into the official

Re: [VOTE] Release apache-calcite-1.21.0 (release candidate 0)

> On Thu, Sep 5, 2019 at 8:04 AM Danny Chan wrote: > >> I made the diff cmd and also see these outputs, it seems that pom.xml.next >> and pom.xml.tag comes from a plugin ? >> >> Best, >> Danny Chan >> 在 2019年9月5日 +0800 AM2:53，Julian Hyde ，写道： >>>

Re: Appropriate query syntax for table-value function windowing (e.g. CALCITE-3272)

ng wrote: > >> Thanks Julian for your explanation and the pointer. >> >> I will go to the direction of TABLE(Function) syntax then. >> >> >> -Rui >> >> On Thu, Aug 29, 2019 at 3:03 PM Julian Hyde wrote: >> >>> Standard SQL

Re: Expected conversion for TIMESTAMPDIFF

Why the division by 12? The SQL in that bug contains “YEAR”: {fn TIMESTAMPDIFF(SQL_TSI_YEAR,TIMESTAMP '2016-01-01 00:00:00', TIMESTAMP '2017-01-01 00:00:00’)} So I presume that we are computing the difference in months, then dividing by 12 to get years. (There are two fundamental kinds of

Re: [DISCUSS] Support Sql Hint for Calcite

tps://www.amazon.com/s?k=9781565924017> > On Sep 4, 2019, at 7:12 PM, Julian Hyde wrote: > > Thanks for continuing to push on this! > > I don’t much like the MSSQL-style syntax for table hints. It adds a new use > of the WITH keyword that is unrelated to the use

Re: [DISCUSS] Support Sql Hint for Calcite

Thanks for continuing to push on this! I don’t much like the MSSQL-style syntax for table hints. It adds a new use of the WITH keyword that is unrelated to the use of WITH for common-table expressions. Instead of select /*+ NO_HASH_JOIN, RESOURCE(mem='128mb', parallelism='24') */ from emp

Re: [VOTE] Release apache-calcite-1.21.0 (release candidate 0)

testing results: > > Local Calcite build with tests enabled on Linux: OK > > Calcite-based system test suite: OK > > > +1 (non-binding) > > On Wed, Sep 4, 2019 at 2:55 AM Julian Hyde wrote: > >> Regarding the 'ps' failures. I've added a suggestion to &g

Re: [VOTE] Release apache-calcite-1.21.0 (release candidate 0)

Regarding the 'ps' failures. I've added a suggestion to https://issues.apache.org/jira/browse/CALCITE-2816?focusedCommentId=16921772=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16921772. Let's continue conversation there. Release threads are not a place for technical

Re: Appropriate query syntax for table-value function windowing (e.g. CALCITE-3272)

Standard SQL doesn’t allow functions in the FROM clause. I think it’s because tables and functions are in different namespaces (and therefore there could be a table and a function with the same name). So you need to use the TABLE keyword to indicate that you are using a function as a table.

[jira] [Created] (CALCITE-3308) RelBuilder.literal with a string argument should create a character literal with appropriate character set

Julian Hyde created CALCITE-3308: Summary: RelBuilder.literal with a string argument should create a character literal with appropriate character set Key: CALCITE-3308 URL: https://issues.apache.org/jira/browse

[jira] [Created] (CALCITE-3307) PigRelExTest fails on Windows

Julian Hyde created CALCITE-3307: Summary: PigRelExTest fails on Windows Key: CALCITE-3307 URL: https://issues.apache.org/jira/browse/CALCITE-3307 Project: Calcite Issue Type: Bug

Re: Using Spark 2.4.0 as Execution Engine with Apache Calcite

Your message was received. I guess no one had the time to respond. Can you please subscribe to the list? I had to moderate your message through because you are not a subscriber. Julian > On Aug 28, 2019, at 9:03 AM, Shubham Kumar wrote: > > Hey, > > Does anyone have any insights on this?

Re: Mapping arithmetic '+' operator with Date and Timestamp operands to target dialect functions

I like the idea of transforming the Rex/Rel tree for the target dialect. Via a RelOptRule or other means. Or perhaps transform the SqlNode tree (which is how we deal with ORDER BY ... NULLS LAST). That’s better, in general, than making the SqlNode-to-string logic more and more complex,

Re: [DISCUSS] Towards Calcite 1.21.0

TE-2302, Julian. > > > > Best, > > Danny Chan > > 在 2019年8月26日 +0800 PM12:27，Julian Hyde ，写道： > > > Sounds good. > > > * I am reviewing 3122 and will commit shortly. > > > * I see Danny has asked me to final review 2302. I'll do that tomorrow. > >

Re: [DISCUSS] Towards Calcite 1.21.0

oks good to me. So I am +1 for the > change. > > > > Best, > Chunwei > > > On Mon, Aug 26, 2019 at 1:39 PM Stamatis Zampetakis > wrote: > >> I see that Chunwei has reviewed 1581 and he gave a +1 so I suppose it is >> ready to go. >> >> On Mon, Aug 2

Re: Preserving CAST of STRING operands in comparison operator

I might be mistaken, but disabling stripCastFromString() for some dialects and not others doesn’t sound like it’s solving the root cause of the problem. Julian > On Aug 26, 2019, at 7:49 AM, Soma Mondal wrote: > > Hi Julian, > > 2 tests failed when I made the stripCastFromString() no-op. >

Re: [DISCUSS] Towards Calcite 1.21.0

; process. I would like to kindly ask the reviewers involved to check that > there is nothing more left to do. > > I will start moving the remaining issues to 1.22.0. Let me know if there is > anything else that we should include in this release. > > Best, > Stamatis > >

Re: PLC4X Request Optimization

request which mask one bit, return >> it (padded) as byte. So 8 requests and 8 bytes data transfer (plus masking >> on the PLC). >> If I would optimize it to read the byte in one request and do the masking >> afterwards I would have one request and only 1 byte transfe

Re: Preserving CAST of STRING operands in comparison operator

I guess you’re talking about the JDBC adapter, and generating SQL for other dialects. I don’t recall why we have stripCastFromString() but I know that it was introduced for a good reason. Try making it no-op and see which tests fail. Julian > On Aug 23, 2019, at 3:32 AM, Soma Mondal wrote:

[jira] [Created] (CALCITE-3286) In LatticeSuggester, allow join conditions that use expressions

Julian Hyde created CALCITE-3286: Summary: In LatticeSuggester, allow join conditions that use expressions Key: CALCITE-3286 URL: https://issues.apache.org/jira/browse/CALCITE-3286 Project: Calcite

Re: [DISCUSS] ANTLR4 parse template for Calcite ?

>>>> Thanks, >>>> Gelbana >>>> >>>> >>>> On Thu, Aug 22, 2019 at 10:05 AM Danny Chan >> wrote: >>>> >>>>> Thanks, Julian. >>>>> >>>>> I agree this would be a hug

Re: TVF windowing and EMIT syntax support in Calcite

Calcite has not implemented the syntax in that paper. I would support an effort to add it (unsurprising, since I am a co-author of that paper). EMIT STREAM is equivalent to the current SELECT STREAM syntax. There is no equivalent in current Calcite of the EMIT AFTER WATERMARK, or EMIT STREAM

Re: [DISCUSS] Towards Calcite 1.21.0

+1 I’ve poked Khai Tran re. 3122 (Pig). > On Aug 16, 2019, at 11:20 PM, Stamatis Zampetakis wrote: > > Hi all, > > The release is advancing quite well, yet we have 22 issues marked for > 1.21.0 [1]. > > From those, the following 5 seem to be the most important: > >

Re: PLC4X Request Optimization

One tricky aspect is to optimize a *batch* of requests. The trick is to tie together the batch so that it is costed as one request. We don’t have an operator specifically for that, but you could for instance use UNION ALL. E.g. given Q1 and Q2, you could generate a plan for select count(*)

[jira] [Created] (CALCITE-3258) Upgrade jackson-databind from 2.9.9 to 2.9.9.2

Julian Hyde created CALCITE-3258: Summary: Upgrade jackson-databind from 2.9.9 to 2.9.9.2 Key: CALCITE-3258 URL: https://issues.apache.org/jira/browse/CALCITE-3258 Project: Calcite Issue

Re: Questions regarding replacing table with SQL query using calcite

That is standard view expansion. We support this. Julian > On Aug 16, 2019, at 06:12, Leon Xu wrote: > > Hi Calcite devs, > > We are modeling a usecase using a DAG. Each node in the DAG will be some > select query. We would like to use calcite to convert all these queries > into one

Re: Is group type "rollup" deduced correctly ?

The key word is "sets". I think you will agree that ((5,3), (5), ()) is a rollup. Well, it is equivalent to ((3, 5), (5), ()) because each grouping set is a SET, and therefore the order of elements does not matter: (3, 5) is the same as (5, 3). Now, if you're using MySQL, for instance, I

Our dependence on Drill and MapR's nexus server

Calcite devs, FYI, I just started a thread on Drill’s dev list about our dependence on MapR’s nexus server. (MapR was just acquired, so there is a concern that over the long term that server will disappear and our builds will stop working.) If you have opinions, please join the discussion.

[jira] [Created] (CALCITE-3240) Javadoc gives internal error "com.sun.tools.javac.code.ClassFinder$BadClassFile: bad class file: linq4j/target/classes/org/apache/calcite/linq4j/Ord$2.class [ERROR] u

Julian Hyde created CALCITE-3240: Summary: Javadoc gives internal error "com.sun.tools.javac.code.ClassFinder$BadClassFile: bad class file: linq4j/target/classes/org/apache/calcite/linq4j/Ord$2.class [ERROR] undeclared type variab

Re: Optimization of join between a small table and a large table

When you implement an equi-join as a nested loops join, the right-hand side always has a filter combining the variable set by the left-hand side and the join column on the right-hand side. You will need to do a full scan of the right-hand table every time, unless your table is organized so

[jira] [Created] (CALCITE-3234) For boolean properties, empty string should mean "true"

Julian Hyde created CALCITE-3234: Summary: For boolean properties, empty string should mean "true" Key: CALCITE-3234 URL: https://issues.apache.org/jira/browse/CALCITE-3234 Projec

Re: Some issues with release 1.20

Do you think you are running into https://issues.apache.org/jira/browse/CALCITE-3145 ? > On Aug 2, 2019, at 2:00 AM, Chunwei Lei wrote: > > Hi, Amit. Thank you for reporting this. > > I suggest you opening a jira to track this. Besides, it

Calcite at ApacheCon NA

ApacheCon North America is in Las Vegas 8 - 12 September. There are 5 talks about Calcite [1]. Yes, five! A great indication that Calcite is being widely used. (Of those 5 talks, 3 also cover Beam, 2 cover Flink, and one each MaxCompute, Drill and Samza.) Consider coming along. It’s a great

Re: [DISCUSS] Towards Calcite 1.21.0

+1 for release at end of August. +1 to figure out which PRs could make it into the release, and work on that list in FIFO order. We tend to merge PRs that are in good shape, and by active contributors, and we tend to ignore old PRs that are never going to make it, but we tend to ignore the

On vacation

I’m on vacation for the next 7 days. Don’t expect (or even hope) that I will review any PRs. There’s always a chance that I will comment on bugs... because it’s useful to point people in the right direction before they start writing code. Julian

Re: Question on SqlFunctions.internalToTimestamp()

he wrong result will change as the local JVM timezone changes across > different machines. > > Shuyi > >> On Fri, Jul 19, 2019 at 8:38 PM Julian Hyde wrote: >> >> Note that that function is for a specialized purpose: converting internal >> timestamps to java.sql.Timestamp

Re: Question on SqlFunctions.internalToTimestamp()

Note that that function is for a specialized purpose: converting internal timestamps to java.sql.Timestamp objects to be passed as arguments to user-defined functions implemented in Java. It assumes that the SQL timestamp values are in the JVM’s default time zone, and since are converting to

Re: CALCITE-3158, Avatica: migrate build system to Gradle

Before we accept this, I would like to make sure that the source artifacts are identical (in terms of name, contents, internal directory structure) to the artifacts we produce today, and the same goes for the contents of the JAR files (manifests, META-INF/service/java.sql.Driver files) and

Re: Intended behaviour in the HepPlanner union rewriting

I don’t think we ever considered that case. Can you please log it, so that it is on record. I haven’t analyzed the issue, but my instinct is that it is a reasonable behavior to want and expect, and that it is not that difficult to fix, and if so, someone should fix it. Julian > On Jul 17,

Re: [DISCUSS] Automated builds for Calcite website

I find my documentation - even for Calcite - using google. The more versions we keep on the site, the greater chance that I am looking at the wrong version. So I vote for keeping only one version, the latest release. Julian > On Jul 15, 2019, at 10:53 PM, Vladimir Sitnikov > wrote: > >

Re: Streams Query Optimization Using Rate and Window Size

Join(U1,B1); whereas, I am not > sure how considering rows per second for bounded sources can help us > estimating the output rate. > > Best, > Alireza > > On Fri, Jul 12, 2019 at 5:43 PM Julian Hyde wrote: > >> In practice, the rowCount is just a number

Re: Has anyone thought of writing a book about Apache Calcite ?

I’ve *thought* about writing a book. I wrote a book about another open source project, Mondrian, for Manning. It was an enjoyable experience, but very hard work and time-consuming, even though I had two excellent co-authors. So, I personally am not in a hurry to write another book. I’d love

Re: [DISCUSS] Automated builds for Calcite website

> On Jul 14, 2019, at 3:27 PM, Francis Chuang wrote: > > In the past, the Javadocs were only ever built right after finalizing a > release. So, in general, the javadocs do not reflect snapshot versions. > > Can Julian confirm if the javadocs must be for the latest final release? That has

Re: Add "IN REVIEW" state in JIRA Workflow

I don’t think another state is necessary/helpful. It seems like more process, when what we are suffering is lack of resources, not lack of process. I do believe that it is helpful to add a comment when I am reviewing - see e.g. https://issues.apache.org/jira/browse/CALCITE-3183

[jira] [Created] (CALCITE-3196) n Frameworks, add BasePrepareAction (a functional interface) and deprecate PrepareAction

Julian Hyde created CALCITE-3196: Summary: n Frameworks, add BasePrepareAction (a functional interface) and deprecate PrepareAction Key: CALCITE-3196 URL: https://issues.apache.org/jira/browse/CALCITE-3196

Re: Streams Query Optimization Using Rate and Window Size

In practice, the rowCount is just a number. So you can think of it as rows-per-second if you are optimizing a continuous query. If you are using a table in a streaming query, does it have a “rows per second?”. Yes - it is the number of rows in the table multiplied by the number of times per

[jira] [Created] (CALCITE-3191) In JDBC adapter, generate implement Values by generating SELECT without FROM

Julian Hyde created CALCITE-3191: Summary: In JDBC adapter, generate implement Values by generating SELECT without FROM Key: CALCITE-3191 URL: https://issues.apache.org/jira/browse/CALCITE-3191

Re: Ask for joining calcite

Please also subscribe to the mailing list, so your messages do not need to go through moderation. Julian > On Jul 11, 2019, at 1:48 AM, Francis Chuang wrote: > > Welcome to the project, Jinpeng! > > I have added your account to the contributor role on jira. > > Francis > > On 11/07/2019

Re: [DISCUSS] Draft board report for July 2019

> Francis wrote: > > We are seeing continual momentum in the project and are very happy to see new > faces, both on the mailing list as well as contributing code via pull > requests. We > believe this is a testament to our welcoming community as well as the > commercial > applicability of the

Re: Period predicates can not be shown correctly

I intended them to be (empty) yellow rectangles. In each diagram, the upper rectangle represents period1 and the lower rectangle period2, and represents the relationship between start and end times that match that particular predicate. > On Jul 4, 2019, at 10:32 PM, Danny Chan wrote: > >

Re: Calcite-Master - Build # 1226 - Still Failing

I know some companies that are still on Java 8. I don’t think we should drop Java 8 or 9 support yet. Julian > On Jul 2, 2019, at 4:24 PM, Stamatis Zampetakis wrote: > > Good point Vladimir. Given that Java 9 reached already the end of its life > I think we should remove it from our CI. > >

Re: Avatica: Gradle vs LICENSE formatting

It is difficult to build LICENSE and NOTICE files automatically. For example, if you have copied some code from a project that has a NOTICE file you only need to copy the lines of the NOTICE that pertain to the code that you have copied. If we don’t exercise judgment we will end up creating

Re: CALCITE-3158, Avatica: migrate build system to Gradle

I will support changes, such as you describe, that add a language and remove another. I am wary of changes that add a new language (or framework, for that matter) to the mix. Hence my pushback against your use of .kts files. We can’t entirely remove Maven and pom.xml files from the process.

Re: Preview repository for Calcite and Calcite Avatica releases

The web site process is not broken. There are some minor licensing bugs. Let’s fix them. Let’s talk about how we can improve the process. The existence of bugs doesn’t mean the process is broken. The release manager must review the licensing/security reports. People reviewing the release can

Re: [RESULT][VOTE] Calcite logo selection

Now we’ve had a vote to establish broad direction, I think you (Michael) should tweak the logo as you see fit, and you don’t need to ask permission from the dev list for those changes. I think the regular PR process will suffice. Thank you for driving this. > On Jul 1, 2019, at 9:54 PM,

Re: Preview repository for Calcite and Calcite Avatica releases

When I said “is there a significant problem” I meant an existing problem. I don’t think there is an existing problem. And if it ain’t broke, don’t fix it. This change would be adding another thing for people voting on releases to review. I don’t want to add that burden. Julian > On Jul 2,

Re: CALCITE-3158, Avatica: migrate build system to Gradle

Let me paraphrase. You asked for proof. No proof is needed. It is self-evident. Julian > On Jul 2, 2019, at 9:01 AM, Vladimir Sitnikov > wrote: > > Michael> I agree with Julian's point about adding maintenance > Michael> overhead. > > Frankly speaking, it is (still) extremely hard for me

Re: Preview repository for Calcite and Calcite Avatica releases

Sigh. More process, more technology. At a time when our release managers are more burdened than ever. Is there a significant problem where we publish a release and the site is screwed up? If so, let’s roll back the change to go to GitHub pages. When we generated the site locally using Jekyll

Re: Avatica: Gradle vs LICENSE formatting

Proof that the amount of knowledge required to maintain Avatica and Calcite is straightforward. There are more lines of code, the code is getting older, and the number of technologies is increasing. I don’t know how you can refute that claim. The question is what we can do to resist that

[jira] [Created] (CALCITE-3166) Make RelBuilder configurable

Julian Hyde created CALCITE-3166: Summary: Make RelBuilder configurable Key: CALCITE-3166 URL: https://issues.apache.org/jira/browse/CALCITE-3166 Project: Calcite Issue Type: Bug

Re: Avatica: Gradle vs LICENSE formatting

This change introduces yet another new language - Kotlin script (.kts extension) - as well as gradle. Vladimir made a case for adding Kotlin-based tests to Calcite a while ago. They have not been used or extended, afaict. The amount of knowledge required to maintain Avatica (and Calcite) is

Re: [VOTE] Calcite logo selection

5b Julian > On Jun 29, 2019, at 1:47 AM, Ivan Grgurina wrote: > > +1 for 5B, but using the font from 2C. > > > From: Yuva raj > Sent: Saturday, June 29, 2019 9:17 AM > To: dev@calcite.apache.org > Subject: Re: [VOTE] Calcite logo selection > > +1 for 5B >

Re: [DISCUSSION] Unify throws in sql parser

Unifying in general sounds like a good idea. I haven’t thought through the specifics in this case. Note that each time we generate a parser using JavaCC — which we do in several places in the code — it generates a new exception class. We don’t want to use those generated classes. We would like

Re: Release 1.20 and release notes

copy of the script somewhere in the repo because the only purpose of >> putting it in the HOWTO would be so someone could copy and paste and >> run it. That said, I'm not sure where a good spot for such scripts to >> live would be in the folder hierarchy. >> -- >> Michael Mior

Re: Modify Calcite Planner in Hive to remove GROUP BY

> Select count(*) from empty_table group by will produce NULL Really? I thought it should produce zero rows. Hsqldb: > select count(*) from "foodmart"."days" where false group by true; +-+ | C1| +-+ +-+ No rows selected (0.001

Re: Giving the Calcite logo some love

follow Julian's suggestion and start the nomination process >> for >>>> the >>>>>> next 48 hours. >>>>>> >>>>>> Personally, the ones that I like the most are: >>>>>> >>>>> >>>

<    11   12   13   14   15   16   17   18   19   20   >