Current status of Streaming SQL standardrization

ards if so? AFAIK, there is a BEAM proposal <https://docs.google.com/document/d/138uA7VTpbF84CFrd--cz3YVe0-AQ9ALnsavaSE2JeE4/edit#heading=h.f7eonhc93kwo> in the BEAM community to move towards the new Streaming SQL extension. Thanks a lot. -- Shuyi Chen https://www.linkedin.com/in/shuyi-chen-pku/

Re: Current status of Streaming SQL standardrization

.calcite.apache.org%3E > [4]:https://jira.apache.org/jira/browse/CALCITE-3271 > > > -Rui > > On Mon, Feb 10, 2020 at 1:14 PM Shuyi Chen wrote: > > > Hi all, > > > > I am wondering what the current status of Streaming SQL standardization > is. > > Has

Re: Current status of Streaming SQL standardrization

gt; proposal. > > Julian > > > > > On Feb 10, 2020, at 1:14 PM, Shuyi Chen wrote: > > > > Hi all, > > > > I am wondering what the current status of Streaming SQL standardization > is. > > Has the work presented at the "One SQL to Rule Them

Question regarding "select * from" behavior with RelRecordType(PEEK_FIELDS, ...)

Hi all, Our team are looking into integration of Flink with Calcite. We found that when we set the RelRecordType to use the PEEK_FIELDS/PEEK_FIELDS_DEFAULT name resolution policy. A "select * from Table" will yield a recursively flatten result. For example, Table: a: Int b: Record(f1: Int, f2

Re: Question regarding "select * from" behavior with RelRecordType(PEEK_FIELDS, ...)

column > with its column family. > > If you don’t have that requirement, you probably shouldn’t use PEEK_FIELDS > or PEEK_FIELDS_DEFAULT. > > Julian > > > On Jun 16, 2017, at 6:07 PM, Shuyi Chen wrote: > > > > Hi all, > > > > Our team are lookin

Re: Question regarding "select * from" behavior with RelRecordType(PEEK_FIELDS, ...)

Can we add an option in StructKind, say, PEEK_FIELDS_NO_STAR_EXPANSION? And modify SqlValidatorImpl.java to disable star expansion optionally? Thanks a lot. Shuyi On Sun, Jun 18, 2017 at 11:59 PM, Shuyi Chen wrote: > We do want to use the PEEK_FIELDS behavior as Flink does support > Reco

Re: Question regarding "select * from" behavior with RelRecordType(PEEK_FIELDS, ...)

7 at 6:01 PM, Shuyi Chen wrote: > Can we add an option in StructKind, say, PEEK_FIELDS_NO_STAR_EXPANSION? > And modify SqlValidatorImpl.java to disable star expansion optionally? > Thanks a lot. > > Shuyi > > On Sun, Jun 18, 2017 at 11:59 PM, Shuyi Chen wrote: > >> We

ITEM + DOT operator does not work for array

Hi, It seems that the following query won't parse in Calcite. How can we fix it, or do I miss something? Thanks a lot. SELECT employees[1].empno from dept_nested Below is the error: java.lang.RuntimeException: Error while parsing query: SELECT employees[1].empno from dept_nested at or

Re: ITEM + DOT operator does not work for array

dept_nested > > Julian > > > On Oct 18, 2017, at 11:15 AM, Shuyi Chen wrote: > > > > Hi, It seems that the following query won't parse in Calcite. How can we > > fix it, or do I miss something? Thanks a lot. > > > &

Re: ITEM + DOT operator does not work for array

Hi Julian, I've created JIRA https://issues.apache.org/jira/browse/CALCITE-2016 for the issue. Could you please help take a look? I can help with the PR also. Thanks a lot. Shuyi On Wed, Oct 18, 2017 at 11:52 AM, Shuyi Chen wrote: > I just tried, it throw the same exception. I'

Support for ROW value constructor with custom CAST type

Hi, I want to use the row value constructor and CAST to create a named row, or even nested named row, e.g. CREATE TYPE myrowtype AS (f1 INTEGER, f2 VARCHAR(10)) SELECT CAST(ROW(intField, "test") AS myrowtype) AS myRow FROM myTable; So if converted to JSON, the output will be {"myRow":{"f0": ${in

Re: Support for ROW value constructor with custom CAST type

Ping, any idea? Thanks a lot. Shuyi On Tue, Nov 7, 2017 at 11:00 AM, Shuyi Chen wrote: > Hi, > > I want to use the row value constructor and CAST to create a named row, or > even nested named row, e.g. > > CREATE TYPE myrowtype AS (f1 INTEGER, f2 VARCHAR(10)) > SELECT CAS

Re: Support for ROW value constructor with custom CAST type

nished, it will be in an optional module, and it won't support > CREATE TYPE at first.) > > You can, however, create types programmatically; search for "address" > in MockCatalogReader and you will see some examples. > > Julian > > > On Wed, Nov 8, 2017 at

Re: [ANNOUNCE] New Calcite PMC chair: Michael Mior

Congratulations! On Wed, Nov 15, 2017 at 11:51 AM Jesus Camacho Rodriguez < jcama...@apache.org> wrote: > Calcite community members, > > I am pleased to announce that we have a new PMC chair and VP. I have > resigned, and Michael was duly elected by the PMC and approved unanimously > by the Board

Question regarding ProjectRemoveRule

Hi, I have a question regarding the ProjectRemoveRule. In Calcite 1980, a test case was introduced below: /** Test case for * https://issues.apache.org/jira/browse/CALCITE-1980";>[CALCITE-1980] * RelBuilder gives NPE if groupKey contains alias. * * Now, the alias does not cause a new expressi

Re: Question regarding ProjectRemoveRule

> Planner rules do their best to keep field names the same, but they don’t > guarantee it. If they did, they’d miss a lot of good opportunities to > optimize. > > By the way, the same goes for RelBuilder. > > Julian > > > > On Jan 18, 2018, at 3:50 PM, Shuyi Chen w

JDK9 test on Travis failing for recent PRs

Hi, It appears the jdk9 test on Travis are failing for all recent PRs. Anyone knows what is broken? Thanks. Shuyi -- "So you have to trust that the dots will somehow connect in your future."

Re: JDK9 test on Travis failing for recent PRs

ges detected, packing new archive [0m > > > . > > > . > > > . > > > [32;1muploading archive [0m > > > > > > travis_time:end:13ed5388:start=1517318668710481898, > > finish=1517318696409874002,duration=27699392104 > > > [0Ktravis_fold:

Re: missing file on Calcite?

SqlParserImpl.java is javaCC generated code from the parser.jj. You need to to "mvn install" to compile the project to generate the file. It is under calcite/core/target/generated-sources/javacc/org/apache/calcite/sql/parser/impl/SqlParserImpl.java. Hope it helps. On Thu, Feb 15, 2018 at 2:39 PM,

Re: [DISCUSS] Towards Calcite 1.16.0

I am working on https://issues.apache.org/jira/browse/CALCITE-2045 (Create Type DDL). I was hoping to get it in for 1.16. Do we have the deadline for the 1.16 feature cut? Thanks. On Fri, Feb 16, 2018 at 10:43 AM, Julian Hyde wrote: > Sounds good. It’s about time for 1.16, and thanks for offerin

Re: [DISCUSS] Towards Calcite 1.16.0

gt; of half-complete PRs, more than usual. If the authors want make a concerted > effort to complete them before the release they should speak up now, and we > can be flexible. > > > > Julian > > > >> On Feb 16, 2018, at 10:51 AM, Shuyi Chen suez1...@gmail.com>

Rendering of https://calcite.apache.org/docs/reference.html is broken on Safari and Chrome

Did a "git log -- site/_docs/reference.md", the last change is on Nov. 21 last year. Maybe some other things break it. Shuyi -- "So you have to trust that the dots will somehow connect in your future."

Re: Rendering of https://calcite.apache.org/docs/reference.html is broken on Safari and Chrome

:) > > -- > Michael Mior > mm...@apache.org > > 2018-02-20 19:48 GMT-05:00 Shuyi Chen : > > > Did a "git log -- site/_docs/reference.md", the last change is on Nov. > 21 > > last year. Maybe some other things break it. > > > > Shuyi >

Re: Rendering of https://calcite.apache.org/docs/reference.html is broken on Safari and Chrome

you post a > link to an image hosted somewhere? > > -- > Michael Mior > mm...@apache.org > > 2018-02-21 0:24 GMT-05:00 Shuyi Chen : > > > Here is a screenshot. > > > > On Tue, Feb 20, 2018 at 5:18 PM, Michael Mior > wrote: > > > >> Thanks

Re: [DISCUSS] Towards Calcite 1.16.0

in the next > release: > > https://issues.apache.org/jira/browse/CALCITE-2157 > > though I haven't figured out an easy way to integrate this into the > calcite > > test dataset (commented about this in the jira issue). > > > > On Sat, F

Re: [ANNOUNCE] New committer: Zhen Wang

Congratulations, Zhen! On Thu, Mar 8, 2018 at 3:57 PM, Julian Hyde wrote: > Apache Calcite's Project Management Committee (PMC) has invited Zhen Wang > to become a committer, and we are pleased to announce that he has accepted. > > Zhen has made a variety of code contributions over the last year

Re: storage of schema (json model) in a database

Just take a quick look. I think the URLStreamHandlerFactory might be the way to go, but might not work out of the box at the moment in Calcite. If you look at ModelHandler.java, it it reading the file using java.io.File which assumes the platform the default local file system. However, I think we

Re: storage of schema (json model) in a database

pecial built-in protocol called “inline:”. Let’s keep that > working. > > > On Mar 9, 2018, at 1:54 PM, Shuyi Chen wrote: > > > > Just take a quick look. I think the URLStreamHandlerFactory might be the > > way to go, but might not work out of the box at the

Re: [DISCUSS] Towards Calcite 1.16.0

> On Feb 28, 2018, at 11:02 AM, Shuyi Chen wrote: > > > > Hi Julian, I've completed the initial PR for > > https://issues.apache.org/jira/browse/CALCITE-2045. Could you please > take a > > look to see if it can make it to 1.16? Thanks a lot. > > > > S

Re: Linq4j-to-Rel converter?

I think that's a good idea. There are other open source projects that offer both Calcite SQL and LINQ style API, and convert them to Calcite relational algebra for query planning and optimization. On Tue, Mar 13, 2018 at 11:27 PM, Walaa Eldin Moustafa < wa.moust...@gmail.com> wrote: > Does Calcit

Re: Linq4j-to-Rel converter?

@walaa, AFAIK, both Flink and Spark offer LINQ style API, other than SQL. @julian, QueryableRelBuilder currently are mostly unimplemented, I think a good starting point would be to add unittests. But I think LINQ interface would be a good addition to current SQL interface, and should receive some

Re: Calcite class diagram

Those are very useful materials for people who want to learn or contribute to Calcite. Do we have a centralized place to collect them? If not, I'd suggest we collect them and put them up on the calcite website. What do you folks think? On Mon, Mar 19, 2018 at 5:59 AM, Christian Tzolov wrote: >

Re: Array element access and nested rows

Thanks a lot, Anton. This seems to be a bug in Calcite. When the statement involving record types, sql validation seems to work, but the rel plan generated might be wrong. I can also reproduce your case: MockTable deptNestedTable = MockTable.create(this, salesSchema, "DEPT_NESTED", false, 4);

Re: Array element access and nested rows

t sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.intellij.rt.execution.a

Re: Array element access and nested rows

ecause input ref index is not adjusted for the flattened > SKILLRECORD? > > Thank you, > Anton > > > On Wed, Mar 21, 2018 at 8:53 PM Shuyi Chen wrote: > > > Actually, the cause for my previous findings is: for the first case, > > SqlToRelConverterTest

Re: Array element access and nested rows

Also, you can try to patch in this PR to see if that fixes your issue, https://github.com/apache/calcite/pull/651. On Thu, Mar 22, 2018 at 12:14 AM, Shuyi Chen wrote: > I think the following is what happened: > > Calcite is trying to remove all structured type in the plan right be

Re: Array element access and nested rows

; Calcite source at the moment). > >> > >> I will build the Calcite with your fix and will report if it fixes my > >> issue. Thanks for the help! > >> > >> Regards, > >> Anton > >> > >> > >> > >> On Thu, Mar 22, 2018

Re: [DISCUSS] Committer duties

Hi Julian and Michael, Thanks a lot for starting the discussion. I think the ownership model is a good idea, and has been used by other open source communities, and we can further break down core into e.g. sql parser, sql validator, relational algebra, planner, JSON model, runtime and etc,. Also,

Supporting named row construction in Calcite SQL

Hi community, I am thinking of adding the following support in Calcite to support named row construction, e.g. SELECT (a as first_name, b as last_name, (c as zip code, d as street, e as state) as address) as record FROM example_table The output will be struct with field names specified in the SQ

Re: [v1.15] A NPE that looks inevitable !

It will be great if you can provide a test to reproduce the problem, and attach it in the JIRA. On Wed, Mar 28, 2018 at 2:50 PM, Muhammad Gelbana wrote: > Absolutely: https://issues.apache.org/jira/browse/CALCITE-2228 > > Please tell me if I should modify any of the information I supplied. Like

Re: Array element access and nested rows

Hi Anton, the fix is merged into master, and will be available in Calcite 1.17. You can also checkout and build the latest master if you need it now. Thanks. Shuyi On Thu, Mar 22, 2018 at 11:30 AM, Shuyi Chen wrote: > Hi Julian, I already logged. Please take a look at the following JIRAs

Re: [ANNOUNCE] New committer: Shuyi Chen

henaX? I know you have > blogged/spoken about AthenaX, Flink and Calcite. > > Julian > > > > On Apr 2, 2018, at 4:10 PM, Michael Mior wrote: > > > > Apache Calcite's Project Management Committee (PMC) has invited Shuyi > Chen > > to become a committer, and

Re: Supporting named row construction in Calcite SQL

Friendly ping, any thoughts? Much appreciated. Shuyi On Tue, Mar 27, 2018 at 11:59 PM, Shuyi Chen wrote: > Hi community, > > I am thinking of adding the following support in Calcite to support named > row construction, e.g. > > SELECT (a as first_name, b as last_name, (c

Re: Supporting named row construction in Calcite SQL

you're > >> proposing. Unless I'm missing something (very possible), it's not part > of > >> the SQL standard. > >> > >> -- > >> Michael Mior > >> mm...@apache.org > >> > >> 2018-04-03 18:48 GMT-04:00 Shuyi Chen : > >>

Re: Supporting named row construction in Calcite SQL

something > >> that might make it into 1.17? > >> > >> We have also had some discussion about adding DDL to Beam so a user can > >> describe the schema of a stream of JSON in pure SQL. Our current though > is > >> to use Big Query compatible STRUCT and ARRAY

Re: Supporting named row construction in Calcite SQL

> > > FYI, I talked to Julian earlier this week and he will be adding Beam to > > the > > > powered by page since he has a doc for generating the image with the > > logos. > > > > > > -- > > > Michael Mior > > > mm...@apache.o

Re: How to create user-defined data types in calcite?

Currently, user defined type is not supported in Calcite. But it's WIP, please see https://issues.apache.org/jira/browse/CALCITE-2045. With this PR, you can either use CREATE TYPE statement to define your own type or define your new type in the JSON schema. Thanks Shuyi On Fri, Apr 20, 2018 at 4

Re: How to create user-defined data types in calcite?

to master shortly. > > > On Apr 20, 2018, at 5:41 PM, Shuyi Chen wrote: > > > > Currently, user defined type is not supported in Calcite. But it's WIP, > > please see https://issues.apache.org/jira/browse/CALCITE-2045. With this > > PR, you can either use C

Re: How to create user-defined data types in calcite?

your own type or define your new type in the JSON schema. On Sat, Apr 21, 2018 at 12:48 AM, Shuyi Chen wrote: > Thanks a lot for your time , Julian. Let me know if you need anything. > > shuyi > On Fri, Apr 20, 2018 at 5:57 PM Julian Hyde wrote: > >> Yes, I’ve ignored that c

Re: [ANNOUNCE] Francis Chuang joins Calcite PMC

Congratulations! On Mon, Apr 23, 2018 at 7:25 AM Michael Mior wrote: > I'm please to announce that Francis has accepted an invitation to join the > Calcite PMC. Francis has been a consistent and helpful figure in the > Calcite community for which we are very grateful. We look forward to the > co

Re: Row expression parse problem

Thanks for raising the issue. I did remember seeing this problem before. I've created a JIRA to log the issue. On Mon, Apr 23, 2018 at 7:29 AM, Julian Hyde wrote: > I agree, this looks like a bug. > > Julian > > > On Apr 23, 2018, at 05:03, 陈硕

Re: How to create user-defined data types in calcite?

(For non product-related stuff, such as committers > and upcoming talks, we change the web site continuously. The person > maintaining the web site has to be a bit careful not to publish the wrong > stuff.) > > > > On Apr 21, 2018, at 10:13 PM, Shuyi Chen wrote: > > > >

Re: How to create user-defined data types in calcite?

ob/master/site/_docs/model.md#type>) Thanks. On Thu, Apr 26, 2018 at 3:58 AM, aishwaryaa...@gmail.com < aishwaryaa...@gmail.com> wrote: > But CREATE TYPE works only with JSON right? Is there any way other than > that? > > On 2018/04/21 00:41:23, Shuyi Chen wrote: > >

Re: Complex Types Support in DDL

Hi Anton, thanks a lot for the great questions. Yes, SqlDataTypeSpec currently only support creating simple SQL types, no row/array/map is supported. CALCITE-2045 adds support for defining custom either simple or row types through the type DDL, and you should be able to use the UDT in your Table

Re: Complex Types Support in DDL

at are capable of handling DDL, and two sets of AST classes. > But > >> I think that is OK, or at least, better than the chaos of trying to > reuse > >> too much. At least, the parsers will share 99% of their DNA with the > core > >> parser. And we can easily share test

Re: Contribution on TUMBLE Implementation! I have implemented it and I wonder if I can contribute it

Just curious, can you explain what the TUMBLE function is? There is already a TUMBLE function in Calcite for streaming queries ( https://calcite.apache.org/docs/stream.html#tumbling-windows). On Wed, May 2, 2018 at 5:53 PM, Francis Chuang wrote: > I forgot to mention in my last message, but plea

Re: Reviewers

I think this is a reasonable idea. We should have owners conceptually for each component, but not physically assigned. Also, I like the idea of sending an email to dev if no one engaged with 24 hours, maybe add a title like [REQUEST REVIEW] [], so committers can better filter the emails. On Tue, M

Re: [ANNOUNCE] Kevin Risden joins Calcite PMC

Congrats, Kevin! On Tue, Jul 10, 2018 at 9:39 AM Josh Elser wrote: > Congrats, Kevin! > > On 7/9/18 7:21 PM, Michael Mior wrote: > > I'm pleased to announce that Kevin has accepted an invitation to > > join the Calcite PMC. Kevin has been a consistent and helpful > > figure in the Calcite commun

Re: SQL Query Set Analyzer

Hi Zheng, I think the Babel parser in the latest Calcite 1.17 might be helpful here. The Babel parser (JIRA here ) can allow Calcite to accept all SQL dialects (e.g. Hive, oracle, and etc.). Before 1.17, Calcite can only parse its own SQL dialect,

Casting from BIGINT to TIMESTAMP in Calcite?

Currently, SqlValidator does not allow casting from BIGINT to TIMESTAMP. Is there any reason that we don't support such CAST rule, or it is fine that we add it in Calcite? Thanks a lot. Shuyi -- "So you have to trust that the dots will somehow connect in your future."

Support UUID type in Calcite

Do we want to add support for UUID type in Calcite? Databases like vertica and postgre are already supporting UUID type? Thanks. Shuyi -- "So you have to trust that

Re: Calcite Streaming and Mongo

That will be cool. It can also be used as an example for other projects to use Calcite streaming. I would imagine you need to translate the SQL through the calcite logical plan to a set of pipeline operators and pipeline stages in mongo. You can refer to projects like Flink, Samza or Storm for refe

Re: [VOTE] Calcite logo selection

+1 5B On Fri, Jun 28, 2019 at 9:32 AM Kevin Risden wrote: > Vote 5B > > Kevin Risden > > > On Fri, Jun 28, 2019 at 12:19 PM Haisheng Yuan > wrote: > > > Vote for 5B. > > > > > > > > > > > > Thanks~ > > Haisheng > > Yuan-- > > 发件人：M

Question on SqlFunctions.internalToTimestamp()

Hi all, I have a question regarding the usage & implementation of SqlFunctions. internalToTimestamp(long v) (I copied the implementation below). I want to clarify the definition of input parameter v. Is it milliseconds since epoch, or something else? If it is milliseconds since epoch, why do we n

Re: Question on SqlFunctions.internalToTimestamp()

timezone they think the timestamp values are in. Then we convert to a > java.sql.Timestamp which is always relative to the UTC epoch.) > > Julian > > > > On Jul 19, 2019, at 1:33 PM, Shuyi Chen wrote: > > > > Hi all, > > > > I have a question regarding

Question on partial filter push down

Hi, I am working on improving the cassandra adapter. Right now, I found that if my filter contains non-primary keys, calcite will just reject the filter and just execute a no-filter cql query which is bad. I am wondering how I can split the filter into cassandra supported part and cassandra-non-s

Re: Question on partial filter push down

s to the non-equality predicates. That > should > >> allow the CassandraFilterRule to convert the Filter with equality > >> predicates and for the rest of the predicates above to be implemented in > >> Enumerable convention. > >> > >> You can look at th

Re: Question on partial filter push down

help! > > Cheers, > -- > Michael Mior > michael.m...@gmail.com > > 2016-08-04 3:33 GMT-04:00 Shuyi Chen : > > > Thanks a lot, Michael and Jordan. I got it working with the suggestion. > > I'll send a pull request later for you guys to help review. > > &g

Non heap memory leak in Calcite?

Hi all, I was using Calcite to query data in Cassandra. I found that there is memory leak in non-heap space when doing calcite queries. Has someone spot such issues? Below is an example code snippet I used. Thanks a lot. Statement statement = someCalciteConnection.createStatement(); ResultSet res

Re: Non heap memory leak in Calcite?

te adapters’ use of those > libraries. > > Julian > > > > On Aug 25, 2016, at 3:45 PM, Shuyi Chen wrote: > > > > Hi all, I was using Calcite to query data in Cassandra. I found that > there > > is memory leak in non-heap space when doing calcite queries. Has som

Re: Non heap memory leak in Calcite?

ible that you have a statement leak? I.e. you hold > statements open after you have finished with them. If so, Calcite would be > unable to free up generated classes and their associated data in the JVM, > and I suppose that might give the symptoms you are seeing. > > Julian > &g

[jira] [Created] (CALCITE-1856) Add StructKind.PEEK_FIELDS_NO_FLATTENING option to disable star expansion

Shuyi Chen created CALCITE-1856: --- Summary: Add StructKind.PEEK_FIELDS_NO_FLATTENING option to disable star expansion Key: CALCITE-1856 URL: https://issues.apache.org/jira/browse/CALCITE-1856 Project

[jira] [Created] (CALCITE-2016) ITEM + DOT operator does not work for array

Shuyi Chen created CALCITE-2016: --- Summary: ITEM + DOT operator does not work for array Key: CALCITE-2016 URL: https://issues.apache.org/jira/browse/CALCITE-2016 Project: Calcite Issue Type

[jira] [Created] (CALCITE-2045) Support "CREATE TYPE" DDL

Shuyi Chen created CALCITE-2045: --- Summary: Support "CREATE TYPE" DDL Key: CALCITE-2045 URL: https://issues.apache.org/jira/browse/CALCITE-2045 Project: Calcite Issue Type: N

[jira] [Created] (CALCITE-2046) Support "CREATE FUNCTION" DDL

Shuyi Chen created CALCITE-2046: --- Summary: Support "CREATE FUNCTION" DDL Key: CALCITE-2046 URL: https://issues.apache.org/jira/browse/CALCITE-2046 Project: Calcite Issue Type: N

[jira] [Created] (CALCITE-2133) Allow SqlGroupedWindowFunction to specify returnTypeInference in its constructor

Shuyi Chen created CALCITE-2133: --- Summary: Allow SqlGroupedWindowFunction to specify returnTypeInference in its constructor Key: CALCITE-2133 URL: https://issues.apache.org/jira/browse/CALCITE-2133

[jira] [Created] (CALCITE-2149) RexSimplify throws indexOutOfBoundException

Shuyi Chen created CALCITE-2149: --- Summary: RexSimplify throws indexOutOfBoundException Key: CALCITE-2149 URL: https://issues.apache.org/jira/browse/CALCITE-2149 Project: Calcite Issue Type

[jira] [Created] (CALCITE-2161) Add "types" collection to the schema element in the JSON model

Shuyi Chen created CALCITE-2161: --- Summary: Add "types" collection to the schema element in the JSON model Key: CALCITE-2161 URL: https://issues.apache.org/jira/browse/CALCITE-2161 Projec

[jira] [Created] (CALCITE-2162) SqlValidatorImpl.stripDot should be recursive

Shuyi Chen created CALCITE-2162: --- Summary: SqlValidatorImpl.stripDot should be recursive Key: CALCITE-2162 URL: https://issues.apache.org/jira/browse/CALCITE-2162 Project: Calcite Issue Type

[jira] [Created] (CALCITE-2167) Travis JDK9 test always fails

Shuyi Chen created CALCITE-2167: --- Summary: Travis JDK9 test always fails Key: CALCITE-2167 URL: https://issues.apache.org/jira/browse/CALCITE-2167 Project: Calcite Issue Type: Bug

[jira] [Created] (CALCITE-2171) [Cleanup] ExampleFunctionTest is not reading model.json

Shuyi Chen created CALCITE-2171: --- Summary: [Cleanup] ExampleFunctionTest is not reading model.json Key: CALCITE-2171 URL: https://issues.apache.org/jira/browse/CALCITE-2171 Project: Calcite

[jira] [Created] (CALCITE-2209) Support loading JSON model file through URL

Shuyi Chen created CALCITE-2209: --- Summary: Support loading JSON model file through URL Key: CALCITE-2209 URL: https://issues.apache.org/jira/browse/CALCITE-2209 Project: Calcite Issue Type

[jira] [Created] (CALCITE-2214) Support CREATE FUNCTION DDL

Shuyi Chen created CALCITE-2214: --- Summary: Support CREATE FUNCTION DDL Key: CALCITE-2214 URL: https://issues.apache.org/jira/browse/CALCITE-2214 Project: Calcite Issue Type: New Feature

[jira] [Created] (CALCITE-2217) Upgrade Calcite dependency to 1.17

Shuyi Chen created CALCITE-2217: --- Summary: Upgrade Calcite dependency to 1.17 Key: CALCITE-2217 URL: https://issues.apache.org/jira/browse/CALCITE-2217 Project: Calcite Issue Type: Task

[jira] [Created] (CALCITE-2220) Wrong ordinal when flattening multiple input records during converting to REL

Shuyi Chen created CALCITE-2220: --- Summary: Wrong ordinal when flattening multiple input records during converting to REL Key: CALCITE-2220 URL: https://issues.apache.org/jira/browse/CALCITE-2220

[jira] [Created] (CALCITE-2221) RelRoot.project does not take into account flattened record type

Shuyi Chen created CALCITE-2221: --- Summary: RelRoot.project does not take into account flattened record type Key: CALCITE-2221 URL: https://issues.apache.org/jira/browse/CALCITE-2221 Project: Calcite

[jira] [Created] (CALCITE-2251) Support AS STRUCT syntax to create named STRUCT in SQL similar to Google BigQuery

Shuyi Chen created CALCITE-2251: --- Summary: Support AS STRUCT syntax to create named STRUCT in SQL similar to Google BigQuery Key: CALCITE-2251 URL: https://issues.apache.org/jira/browse/CALCITE-2251

[jira] [Created] (CALCITE-2252) Add supported SQL Dialects in Calcite website

Shuyi Chen created CALCITE-2252: --- Summary: Add supported SQL Dialects in Calcite website Key: CALCITE-2252 URL: https://issues.apache.org/jira/browse/CALCITE-2252 Project: Calcite Issue Type

[jira] [Created] (CALCITE-2276) Calcite unable to parse ROW value constructor in certain scenario

Shuyi Chen created CALCITE-2276: --- Summary: Calcite unable to parse ROW value constructor in certain scenario Key: CALCITE-2276 URL: https://issues.apache.org/jira/browse/CALCITE-2276 Project: Calcite

[jira] [Created] (CALCITE-2440) SQL with UNNEST fail in volcano planner in some cases

Shuyi Chen created CALCITE-2440: --- Summary: SQL with UNNEST fail in volcano planner in some cases Key: CALCITE-2440 URL: https://issues.apache.org/jira/browse/CALCITE-2440 Project: Calcite

[jira] [Created] (CALCITE-2466) RexSimplify incorrectly simplify conjunction statement with null literal

Shuyi Chen created CALCITE-2466: --- Summary: RexSimplify incorrectly simplify conjunction statement with null literal Key: CALCITE-2466 URL: https://issues.apache.org/jira/browse/CALCITE-2466 Project