[jira] [Created] (CALCITE-2759) Update maven-remote-resources-plugin to 1.6.0

Vladimir Sitnikov created CALCITE-2759: -- Summary: Update maven-remote-resources-plugin to 1.6.0 Key: CALCITE-2759 URL: https://issues.apache.org/jira/browse/CALCITE-2759 Project: Calcite

Re: ElasticSearch adapter. Exposing meta fields (like _id, _uid etc.)

Let’s take an example of a simple query: -- note _id fieldselect _MAP['a'], _MAP['_id'] from elastic order by _MAP['c'] Logical plan is as follows: ElasticsearchToEnumerableConverter ElasticsearchSort(sort0=[$2], dir0=[ASC]) ElasticsearchProject(EXPR$0=[ITEM($0, 'a')], EXPR$1=[ITEM($0,

Re: JSON(B) Support like in Postgres

Hey Hongze, thanks for your response. I'm not sure if it would be the right way to overwrite the Built-In Functions in Calcite (or disable them). I thought about translating them to different Postgres calls, i.e., implement a suitable Postgres Adapter that Maps Calcites Built-in functions to

Re:JSON(B) Support like in Postgres

Hi Julian, If I remember right, Calcite does not support Postgres's json and jsonb datatype in current version (1.18). Calcite has built-in JSON support (see CALCITE-2266[1]) similar to what has been implemented in Oracle and MS SQL, It is a earlier version of the whole JSON things described

JSON(B) Support like in Postgres

Hi all, we use Postgres a lot and make heavy use of the JSONB datatype [1]. Is there support for something similar in Calcite? If so, can someone point me to the docs as I’ve not found anything in the list of builtin functions. There are several reasons why it would be cool for us to have

Re: ElasticSearch adapter. Exposing meta fields (like _id, _uid etc.)

I think a concrete example of a query with its respective logical plan could clarify a few things. I would expect that the logical plan contains all the necessary information to decide which fields need to be fetched from Elastic without requiring additional aliases. If that information is lost