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

And I think both TABLE and DESCRIPTOR are not supported as (table)function parameters? TABLE parameter: TABLE(table_name) or TABLE table_name to specify an input table. DESCRIPTOR parameter: DESCRIPTOR(column_name, ...) to specify columns from the input table. -Rui On Thu, Aug 29, 2019 at

Re: Preserving CAST of STRING operands in comparison operator

This is kind of in the scope of implicit type coercion which is supported in CALCITE-2302. For sql dialect that does not support implicit type coercion, strip explicit cast is a mistake. I think this can be seen as a bug and we should log an issue to fix. But just like you said, if we support

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

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 doesn’t allow functions in the FROM clause. I think it’s > because tables and functions are in different

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.

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

Hi Community, I have been searching and trying Calcite's query syntax to match CALCITE-3272 (TUBME as a table function call). Currently, the closest syntax in Calcite I found is: FROM TABLE(TUMBLE(params...)) The better syntax should be: FROM

[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:

[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

EQUITAS

I was browsing the proceedings of this year's VLDB conference and came across the paper below doing something similar to Cosette (http://cosette.cs.washington.edu/), validating two SQL queries are equivalent. Pairs of queries were pulled from Calcite pre and post-optimization. I've only skimmed

Re: Using Spark 2.4.0 as Execution Engine with Apache Calcite

Hey Julian, Thanks, I have subscribed to the list now. On Wed, Aug 28, 2019 at 10:58 PM Julian Hyde wrote: > 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. >

Calcite-Master - Build # 1321 - Still Failing

The Apache Jenkins build system has built Calcite-Master (build #1321) Status: Still Failing Check console output at https://builds.apache.org/job/Calcite-Master/1321/ to view the results.

Re: row value constructors for pagination

If it is a deterministic promotion, you can write a RelOptRule to support this. Best, Danny Chan 在 2019年8月29日 +0800 AM9:13，Thomas D'Silva ，写道： > I am looking into the possibility of using row value constructors for > paging through data. The query would be of the form > > SELECT * FROM t WHERE

[jira] [Created] (CALCITE-3306) Add REGEXP_SPLIT_TO_ARRAY function

Wang Yanlin created CALCITE-3306: Summary: Add REGEXP_SPLIT_TO_ARRAY function Key: CALCITE-3306 URL: https://issues.apache.org/jira/browse/CALCITE-3306 Project: Calcite Issue Type: New