Materialization left join rewrite

at issue. -- Mit freundlichen Grüßen, -------- *Christian Beikov*

Casts because of nullability differences

, *Christian Beikov*

Travis CI build

, *Christian Beikov*

Re: 1.14.0 Release candidate

the MongoDB adapter is considered production ready, ignore the problems or cancel the release. Mit freundlichen Grüßen, *Christian Beikov* Am 20.09.2017 um 04:18 schrieb Jesus Camacho Rodriguez: Michael, It seems nobody

Re: Travis CI build

Here is the PR for disabling parallelism on Travis CI. I also took the opportunity to fix the JDK7 problem. https://github.com/apache/calcite/pull/542 Mit freundlichen Grüßen, *Christian Beikov* Am 20.09.2017 um 03:34

Re: 1.14.0 Release candidate

I could setup test automation on TravisCI for most of the different databases if you want with some description amd scripts for how to run the docker containers for DBs locally. Would that help? It's almost as flexible as Jenkins. Regards, Christian Am 13.09.2017 22:46 schrieb "Michael Mior"

Re: [ANNOUNCE] New committer: Christian Beikov

Thank you all for the kind words! :) Mit freundlichen Grüßen, *Christian Beikov* Am 13.10.2017 um 09:45 schrieb Chris Baynes: Congrats Christian! On Fri, Oct 13, 2017 at 5:22 AM, He Zhiqiang <zhiqian...@apache.org>

Sequence support

that's only one part I guess. Currently, the planner thinks a plan like "EnumerableProject(NEXT VALUE FOR seq1) -> EnumerableValues( (0) )" is better than "JdbcProject(NEXT VALUE FOR seq1) -> JdbcValues( (0) )" which it isn't. Any ideas how I could fix that? -- Mit freundlichen Grüßen, *Christian Beikov*

Re: Materialization performance

o you have any plans to tackle that or am I not seeing how to achieve this? Mit freundlichen Grüßen, -------- *Christian Beikov* Am 29.08.2017 um 19:40 schrieb Julian Hyde: I'd rather have immutable state being CASed(compare-and-swap)

Re: adding CREATE TABLE DDL support?

Sounds like a good idea. Mit freundlichen Grüßen, *Christian Beikov* Am 08.09.2017 um 19:28 schrieb Julian Hyde: It’s in core/src/test/codegen/includes/parserImpls.ftl (i.e. a parser extension used in tests) but we don’t

Re: Fwd: ElasticSearch5 not working

build-time. This would help folks > build Calcite with the exact version that they want (assuming that the API > hasn't changed and the adapter actually works with that version of ES) > > We don't need to have multiple versions of ElasticSearch on the classpath > at once, right? >

Re: ElasticSearch5 not working

, *Christian Beikov* Am 28.09.2017 um 18:35 schrieb Julian Hyde: Christian, I don’t understand. The elasticsearch5 module does not depend on the elasticsearch2 module, only on core and linq4j. Therefore if it (and its dependencies) are added

Re: ElasticSearch5 not working

hen Grüßen, *Christian Beikov* Am 28.09.2017 um 19:16 schrieb Julian Hyde: I understand that. But if we remove calcite-elasticsearch2 from sqlline’s classpath, sqlline will still get calcite-elasticsearch5 and the elastic search 5.x client driver libraries that it depends upon. And the elas

Re: Does calcite have working ElasticSearch 5 adapter?

You can see what is supported by looking at the tests for the adapter. Mit freundlichen Grüßen, *Christian Beikov* Am 02.10.2017 um 10:17 schrieb kant kodali: where can I find all the operations the current ES5 adapter

Re: ElasticSearch5 not working

, *Christian Beikov* Am 27.09.2017 um 20:28 schrieb Julian Hyde: I agree with Christian that it’s just a problem with sqlline’s class path. The simplest solution is to remove elasticsearch2 from the line that builds the class path: for module in core cassandra druid elasticsearch2 elasticsearch5

Re: Materialized view case sensitivity problem

a CalciteConnectionConfig? Mit freundlichen Grüßen, *Christian Beikov* Am 24.08.2017 um 11:36 schrieb Christian Beikov: Seems org.apache.calcite.prepare.CalcitePrepareImpl#prepare2_ misses a call

Re: Materialized view case sensitivity problem

with the types from the table. Is this replacement of field types even correct? Because of that, the assertion in the substiution visitor fails. What would be the appropriate solution for this mismatch? Mit freundlichen Grüßen, *Chri

Re: Materialized view case sensitivity problem

Grüßen, *Christian Beikov* Am 24.08.2017 um 12:57 schrieb Julian Hyde: Or supply your own TableFactory? I'm not quite sure of your use case. I've only tested cases where materialized views are "internal", therefore

Re: Materialized view case sensitivity problem

er cased column names? Mit freundlichen Grüßen, ---- *Christian Beikov* Am 24.08.2017 um 21:00 schrieb Julian Hyde: Rather than "select id, name from document” could you create your view as "select `id`, `name` from document” (o

Re: Materialized view case sensitivity problem

materializations to avoid the casing problem and having to rely on a specific case. Thanks for the clarifications! Mit freundlichen Grüßen, *Christian Beikov* Am 24.08.2017 um 21:52 schrieb Jesus Camacho Rodriguez: I never hit

Materialization performance

during planning, I'd suggest doing that during materialization registration instead like it is already mentioned CalcitePrepareImpl#populateMaterializations. Would that be ok? -- Mit freundlichen Grüßen, *Christian Beikov*

Re: Materialization performance

, *Christian Beikov* Am 28.08.2017 um 08:13 schrieb Jesus Camacho Rodriguez: Hive does not use the Calcite SQL parser, thus we follow a different path and did not experience the problem on the Calcite end. However, FWIW we avoided

Re: Materialization left join rewrite

, *Christian Beikov* Am 24.08.2017 um 02:13 schrieb Julian Hyde: Jesus, Can you answer this question for Christian please? Seems like a reasonable use case, and your area of expertise. Julian On Aug 20, 2017, at 12:25 PM, Christian Beikov <christian.bei...@gmail.

Re: Casts because of nullability differences

ers might get confused. Mit freundlichen Grüßen, *Christian Beikov* Am 23.08.2017 um 21:20 schrieb Julian Hyde: It’s difficult to say for sure whether the cast is necessary. For some of us consistency, is an end

Re: Casts because of nullability differences

freundlichen Grüßen, *Christian Beikov* Am 24.08.2017 um 02:05 schrieb Julian Hyde: You didn’t say that the casts were ending up in generated SQL. That would be a bug. Probably in RelToSqlConverter. On Aug 23, 2017, at 4:35

Re: Casts because of nullability differences

, *Christian Beikov* Am 23.08.2017 um 20:01 schrieb Julian Hyde: I presume you’re talking about RexNodes. It makes a lot of things easier if the argument to function call are EXACTLY the type required by that function. The system inserts implicit casts where

Materialized view case sensitivity problem

hen Grüßen, *Christian Beikov*

Re: Materialized view case sensitivity problem

, *Christian Beikov* Am 24.08.2017 um 11:24 schrieb Christian Beikov: Hey, I have configured Lex.MYSQL_ANSI but when a query gets parsed, the column names of select items are "to-upper-cased". I'm having problems with matching the

Re: Casts because of nullability differences

after substitutions? Any idea where I should dig into? Mit freundlichen Grüßen, *Christian Beikov* Am 24.08.2017 um 21:31 schrieb Julian Hyde: Optimized away later. In fact during SQL generation. SQL has no concept

Re: Materialization performance

, *Christian Beikov* Am 28.08.2017 um 20:01 schrieb Jesus Camacho Rodriguez: Christian, The implementation of the filter tree index is what I was referring to indeed. In the initial implementation I focused on the rewriting coverage, but now that the first part is finished, it is at the top of my list

Re: JdbcAdapter Sort Limit and Offset

still have components like e.g. a SequenceExtractor or LimitOffsetRenderer, but the dialects choose the implementation based on the database metadata. What do you think? Mit freundlichen Grüßen, *Christian Beikov* Am

Re: Materialization performance

can discuss specifics. Along the way I'd try to do some general performance improvements regarding concurrency synchronization mechanisms. Would that be ok? Mit freundlichen Grüßen, *Christian Beikov* Am 31.08.2017 um 00:02

Re: Need to extract only the values in the field

l.json#L37 Mit freundlichen Grüßen, *Christian Beikov* Am 09.10.2017 um 19:40 schrieb AshwinKumar AshwinKumar: Hi Team, Could you please help here. I am stuck on this problem for like 2 days now. Thanks, Ashwin On Mon, Oct 9,

Re: Fwd: ElasticSearch5 not working

freundlichen Grüßen, -------- *Christian Beikov* Am 27.09.2017 um 01:30 schrieb Kunwar Deep Singh Toor: -- Forwarded message -- From: Kunwar Deep Singh Toor <kt...@g.clemson.edu> Date: Mon, Sep 25, 2017 at 8:16 PM Subject: ElasticSearch5 not working To: dev-i...@calcite.

Re: ElasticSearch Adapters. Calcite vs Dremio

, *Christian Beikov* Am 17.05.2018 um 13:56 schrieb Michael Mior: It's my understanding that while Dremio plugins serve a similar purpose, they are different from Calcite adapters. In any case, it could be worth looking at what Dremiois doing to see if there are any useful features

Re: ElasticSearch. Explicit Definitions, Literals and RelBuilder

1) I wasn't aware of an API to retrieve a schema. We could definitely use that to avoid the need for views. 2) I agree, seems like a bug. Mit freundlichen Grüßen, *Christian Beikov* Am 17.05.2018 um 13:51 schrieb Michael

Re: ElasticSearch. Explicit Definitions, Literals and RelBuilder

? :) Mit freundlichen Grüßen, *Christian Beikov* Am 17.05.2018 um 17:43 schrieb Andrei Sereda: Regarding (2) Lower-case problem. The issue seems to be in ElasticsearchFilter.Translator <https://github.com/apache/calcite/b

Re: ElasticSearch use of rest client (instead of TransportClient)

, that would be great :) Mit freundlichen Grüßen, *Christian Beikov* Am 18.05.2018 um 21:19 schrieb Andrei Sereda: Yes it should be, since it is just an http client (apache http). ElasticSearch Rest API (query API) didn't

Re: ElasticSearch use of rest client (instead of TransportClient)

Hey Andrei, that would be awesome! Do you know by any chance if the low level client is also compatible with older ES versions? Mit freundlichen Grüßen, *Christian Beikov* Am 18.05.2018 um 20:45 schrieb Andrei Sereda

Re: Calcite travis jdk11 failed while compilation of calcite-elasticsearch2 on travis

you can do. I'd assume other tests that use e.g. Netty would fail compilation as well. Mit freundlichen Grüßen, *Christian Beikov* Am 12.06.2018 um 14:11 schrieb Sergey Nuyanzin: Hello everyone Just I have an issue related

Re: Calcite travis jdk11 failed while compilation of calcite-elasticsearch2 on travis

I think this might actually be a JDK bug. Let's wait a bit for a new EA release. Mit freundlichen Grüßen, *Christian Beikov* Am 12.06.2018 um 22:14 schrieb Julian Hyde: What would be the command-line arguments to achieve

Re: Elasticsearch integration test failures

If you migrate the existing tests to use the local node in that PR, I'd consider merging that PR given that Travis CI reports no test failures. Mit freundlichen Grüßen, *Christian Beikov* Am 11.06.2018 um 14:33 schrieb

Re: Elasticsearch integration test failures

8 at 3:48 PM, Christian Beikov < > christian.bei...@gmail.com> wrote: > > > If you migrate the existing tests to use the local node in that PR, I'd > > consider merging that PR given that Travis CI reports no test failures.

Re: Elasticsearch integration test failures

So I'm all in on using just a local node which is also something I wanted to do for a long time, but you got to it before I did. Do the tests succeed with the local node? Mit freundlichen Grüßen, *Christian Beikov* Am 07.

Re: Elasticsearch integration test failures

rate) commit > ? > > I was planning to do it just not in the same PR. > > On Mon, Jun 11, 2018 at 4:31 PM, Christian Beikov < > christian.bei...@gmail.com> wrote: > > > For me that's fine, though it would be great if you could fix those given > > your time permits

Re: ElasticSearch use of rest client (instead of TransportClient)

Looks great! Mit freundlichen Grüßen, *Christian Beikov* Am 22.06.2018 um 20:24 schrieb Michael Mior: Looks good to me but I'll defer to Christian since I know little about ES. Thanks for this Andrei! -- Michael Mior mm

Re: [2/2] calcite git commit: [CALCITE-2347] running ElasticSearch in embedded mode for unit tests of ES adapter (Andrei Sereda)

Huh? How is that possible? I thought the checks that are run by the Travis CI build catch these kinds of errors. Mit freundlichen Grüßen, *Christian Beikov* Am 22.06.2018 um 23:11 schrieb Julian Hyde: Looks like

Re: ElasticSearch use of rest client (instead of TransportClient)

for unifying the adapters. Changing the dependency and the schema factory name are IMO not problematic. Mit freundlichen Grüßen, *Christian Beikov* Am 22.06.2018 um 19:07 schrieb Andrei Sereda: 1) If we go single

Re: Elasticsearch Adapter. Removal of Mapping Types (by vendor). Index == Table

freundlichen Grüßen, *Christian Beikov* Am 29.06.2018 um 20:19 schrieb Julian Hyde: Andrei, I'm not an ES user so I don't fully understand this issue, but my two cents anyway... Can you show how those examples affect SQL

Re: Elasticsearch Adapter. Removal of Mapping Types (by vendor). Index == Table

"${index}_${type}" // most generic. supports multiple types per index On Fri, Jun 29, 2018 at 9:26 AM Michael Mior wrote: I think it sounds like you and Andrei are in a good position to tackle this one so I'm happy to have you both work on whatever solution you think

Re: Maven wrapper

, *Christian Beikov* Am 29.12.2017 um 21:42 schrieb Julian Hyde: We have a pull request for a maven wrapper[1]. People would not need to install maven to build Calcite, but we would include shell/cmd scripts and a bootstrap .jar. It would allow us to use a specific version of maven

Re: Use Calcite adapter with Elastic search and Java

. Mit freundlichen Grüßen, *Christian Beikov* Am 14.02.2018 um 10:15 schrieb Saurabh Pathak: Hello, I want to use calcite adapter with elastic search and java. But i haven't idea how to use calcite elastic search adapter

Re: [VOTE] [CALCITE-490] Remove "End File.java" comments from the end of files

+1 Am 10.09.2018 um 10:49 schrieb Vladimir Sitnikov: Hi, Could we have a vote on coding style regarding "// End File.java" in Calcite source files? "//End..." comments clutter Git history, they consume screen space, and they slow down the development by causing Checkstyle violations. Could we

Re: Elasticsearch Adapter. Removal of Mapping Types (by vendor). Index == Table

scenarios. Mit freundlichen Grüßen, *Christian Beikov* Am 29.06.2018 um 00:12 schrieb Andrei Sereda: 1) What's the time horizon for the current adapter no longer working with these changes to ES ? Current adapter

Re: Elasticsearch Adapter. Removal of Mapping Types (by vendor). Index == Table

ation and the default for "table_mapping" is "type" This would also allow to discover indexes but still use "type" as "table_mapping". What do you think? Mit freundlichen Grüßen, *Christi

Re: scrolling in ElasticSearch adapter

Hey, not sure if this should be an SQL keyword. JDBC specifies various constants that can be used at statement creation time: https://docs.oracle.com/javase/7/docs/api/java/sql/ResultSet.html Not sure though if or how these configurations are accessible for data stores or dialects, but IMO

Re: scrolling in ElasticSearch adapter

tement across page requests. Julian [1] https://docs.oracle.com/cd/B10500_01/server.920/a96533/hintsref.htm#4924 On Oct 24, 2018, at 11:19 AM, Christian Beikov < christian.bei...@gmail.com> wrote: Hey, not sure if this should be an SQL keyword. JDBC specifies various constants that

Re: scrolling in ElasticSearch adapter

but have some reservations (questions) : How to pass resultSetType / fetchSize from PreparedStatement to RelNodes ? What if user doesn’t use JDBC (eg. RelBuilders) ? On Wed, Oct 24, 2018 at 6:28 PM Christian Beikov wrote: In JDBC one can configure a fetch size which would reflect the amount of rows

Re: [DISCUSS] Move gitbox notification emails to another list?

Hey, yeah just make those E-Mails stop please. They are pretty annoying. Am 27.02.2019 um 11:13 schrieb Francis Chuang: Hey all, I wanted to gauge your opinions regarding the gitbox emails being sent to the dev@ list. I am finding these emails to be quite noisy (there is an email every time

Re: Correlation with a variable

Chan: From the case you gave, the “variable” seems a view ? Sorry I’m not familiar with the traditional RDBMS. Best, Danny Chan 在 2020年2月17日 +0800 PM1:27，Christian Beikov ，写道： Hello, I asked this before but I guess the question got too big, so I thought splitting it up might be better. I am

Re: Correlation with a variable

clause can be used to introduce a temporary view for an old and new relation. Best, Stamatis On Tue, Feb 18, 2020 at 7:03 PM Christian Beikov wrote: My issue is not about parsing. I already have the relational model, I parsed a query to which I want to add add a condition to a RelNode. Now I

Translation of SQL EXISTS

Hello, I'm a bit confused about how the SQL EXISTS predicate is translated. I'd assume that an EXISTS is translated in relational algebra to a SEMI- and NOT EXISTS to an ANTI-join, but it's not. PlannerImpl p = new PlannerImpl(config); SqlNode sqlNode = p.parse("delete from _order o where

Re: How to optimize repeated RelNode Structures? (CALCITE-3806)

I guess what you are looking for is something like the SubPlan node of PostgreSQL? Such a node would materialize the results to be used by multiple other nodes or in a nested loop context to avoid accessing a source relation multiple times. Would be cool if Calcite could create a SubPlan and let

Re: Translation of SQL EXISTS

this process in Calcite is counter intuitive. It should be in reverse order, first generate a semi or anti-semi join, then generate an inner/outer join. - Haisheng -- 发件人：Christian Beikov 日　期：2020年02月19日 21:12:13 收件人： 主　题：Translation

Re: Translation of SQL EXISTS

in Calcite is counter intuitive. It should be in reverse order, first generate a semi or anti-semi join, then generate an inner/outer join. - Haisheng -- 发件人：Christian Beikov 日　期：2020年02月19日 21:12:13 收件人： 主　题

Re: Translation of SQL EXISTS

Yeah right, somehow forgot to add the link. Am 20.02.2020 um 21:46 schrieb Julian Hyde: Thanks. I guess you mean https://issues.apache.org/jira/browse/CALCITE-3810 <https://issues.apache.org/jira/browse/CALCITE-3810>. On Feb 20, 2020, at 11:21 AM, Christian Beikov wrote: Alright, s

Correlation with a variable

Hello, I asked this before but I guess the question got too big, so I thought splitting it up might be better. I am trying to generate a query from a relational model on which I did a few tranformations but I don't know how to refer to a "variable". In a SQL trigger, there usually are two

RelNode rewrite

Hello, I'm trying to generate SQL for a trigger that requires a little rewrite of a RelNode structure and I wanted to know if anyone could help me figure out how to do a few things * I need to swap left and right of a LogicalJoin. Doing that messes up predicates and projections though.

Re: RelNode rewrite

Hey Jess! Am 14.02.2020 um 02:16 schrieb Jess Balint: Hey Christian, On Thu, Feb 13, 2020 at 6:30 PM Christian Beikov wrote: Hello, I'm trying to generate SQL for a trigger that requires a little rewrite of a RelNode structure and I wanted to know if anyone could help me figure out how

Re: Correlation with a variable

converting the RelNode to SQL. Do I have to extend the SqlDialect to support that? Danny Chan schrieb am Di., 18. Feb. 2020, 15:12: > If you want to make NEW a normal sql identifier, you should override it in > the parser to make it unreserved. > > Christian Beikov 于2020年2月18日 周二下午3

Re: TableModify does not keep UPSERT keyword

a lot of effort keeping like-things-like. On Tue, Mar 17, 2020 at 1:11 AM Christian Beikov wrote: AFAIK MERGE has different concurrency semantics than what some DBMS call UPSERT. PostgreSQL for example has a guaranteed insert or update semantics whereas MERGE could end with constraint violation

Re: TableModify does not keep UPSERT keyword

AFAIK MERGE has different concurrency semantics than what some DBMS call UPSERT. PostgreSQL for example has a guaranteed insert or update semantics whereas MERGE could end with constraint violation errors: https://wiki.postgresql.org/wiki/UPSERT Maybe it's worth adding that to the relational

EnumerableTableScan array/multiset handling

Hello, in my recent experiments I ran into some issues when trying to unnest an array of struct. The query is roughly this: select t.id, e.value1 from MyTable t, unnest(t.structArray) e EnumerableTableScan#fieldExpression will then try to generate code that converts the value of the

[jira] [Created] (CALCITE-1940) Implement dialect specific support for sequences

Christian Beikov created CALCITE-1940: - Summary: Implement dialect specific support for sequences Key: CALCITE-1940 URL: https://issues.apache.org/jira/browse/CALCITE-1940 Project: Calcite

[jira] [Created] (CALCITE-1967) Add support for elastic search 5

Christian Beikov created CALCITE-1967: - Summary: Add support for elastic search 5 Key: CALCITE-1967 URL: https://issues.apache.org/jira/browse/CALCITE-1967 Project: Calcite Issue Type

[jira] [Created] (CALCITE-1965) Support outer joins for materialized views

Christian Beikov created CALCITE-1965: - Summary: Support outer joins for materialized views Key: CALCITE-1965 URL: https://issues.apache.org/jira/browse/CALCITE-1965 Project: Calcite

[jira] [Created] (CALCITE-3840) Re-aliasing of VALUES that has column aliases produces wrong SQL in the JDBC adapter

Christian Beikov created CALCITE-3840: - Summary: Re-aliasing of VALUES that has column aliases produces wrong SQL in the JDBC adapter Key: CALCITE-3840 URL: https://issues.apache.org/jira/browse/CALCITE-3840

[jira] [Created] (CALCITE-3810) Implement Rel-to-Sql translation for ANTI and SEMI join

Christian Beikov created CALCITE-3810: - Summary: Implement Rel-to-Sql translation for ANTI and SEMI join Key: CALCITE-3810 URL: https://issues.apache.org/jira/browse/CALCITE-3810 Project: Calcite