Re: ElasticSearch. Explicit Definitions, Literals and RelBuilder

> > Seems like an easy fix. Would you mind creating the PR? :) https://github.com/apache/calcite/pull/692 Any chance to get a patch release ? On Thu, May 17, 2018 at 12:32 PM, Christian Beikov < christian.bei...@gmail.com> wrote: > I honestly don't know the reason for that. I mainly just

Re: ElasticSearch. Explicit Definitions, Literals and RelBuilder

I honestly don't know the reason for that. I mainly just reused the original implementation which was comitted here: https://github.com/apache/calcite/commit/f3caf13b9f1cd92f95dcf27716466bf2133e1ed7#diff-3ebf1b729d2fdd03596ff01088977e63 Seems like an easy fix. Would you mind creating the PR?

Re: ElasticSearch. Explicit Definitions, Literals and RelBuilder

Regarding (2) Lower-case problem. The issue seems to be in ElasticsearchFilter.Translator which can be easily fixed : return "\"query\" : " +

Re: ElasticSearch. Explicit Definitions, Literals and RelBuilder

I'm not too familiar with the RelBuilder API myself unfortunately. I think for your ???, you want builder.field(0) although builder.field("_MAP") may also work. -- Michael Mior mm...@uwaterloo.ca Le jeu. 17 mai 2018 à 10:39, Andrei Sereda a écrit : > Hi Michael and

Re: ElasticSearch. Explicit Definitions, Literals and RelBuilder

Hi Michael and Christian, Thanks for your replies. Regarding (3) RelBuilder below is the query plan. I'm not sure how to express element =(ITEM($0, 'Foo') using API. Query Plan 0: jdbc:calcite:model=target/test-classes/mod> explain plan for select * from "elasticsearch_raw"."table" where

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

1) I'm not too familiar with ES so I didn't realize you could define mappings. I don't see any obvious reason why we couldn't use those assuming they're exposed via the ES API. 2) I was not aware of this and not sure whether it was intentional. It seems like a bug to me though. 3) Whenever you