Re: [Question] Cannot query with Avatica on multiple nodes: connection caching issues

Hi Istvan, thanks for your reply. The client-side load balance would help with the stickiness problem but that means that: - We need to expose our deployment topology (URL to individual nodes) to dozens of consumers in our company, creating a maintenance burden unless we build additional

Index Based QueryableTable Implementation

Hello Calcite Devs, I'm working on a data mocking system that's accessible via a relational API: tables, columns, indexes, etc. I implemented a rudimentary query runner layer from scratch, so the project is already usable in MVP state. The next step would be the integration of Calcite. For

Hosting Tableau Connector in Calcite

Hi Calcite Devs, We have been working on creating a version of the Tableau connector [1] that allows Tableau Desktop and server to connect to external data sources, in this case to interface with our BI application, Looker. We created a dialect definition (TDD file) [2] conformant to the

Re: [Question] Unknown cost calculation/propagation in RelSubsets

You’re right, metadata handler methods for RelSubset would be the way to go. If there are no such methods I guess no one has tried to solve this problem before. (At least no one who contributed their changes back.) Yes, those are the papers. They are foundational for Calcite but I haven’t read

Re: Refactor reference.md

The current review process is that I hand-edit most of the submissions. (Or make detailed suggestions: ‘Convert this verb from declarative to imperative. Remove the space before the open parenthesis.') I we increase the scope of the documentation, that puts more burden on me. We should not

Re: Refactor reference.md

I am not proposing a new process, the existing review process would continue to apply. The page would still be part of the repository. Just a separate web page on the calcite site, unbundled from the SQL language page. Mihai From: Julian Hyde Sent: Wednesday,

Re: Refactor reference.md

"The documentation would be incrementally improved, like the code base." Or it might incrementally decline into a shambles. Sure, this is open source, and open source can sometimes create miracles, but we need to be realistic. We need an owner, and systems in place, to overcome the effects of

Re: Refactor reference.md

The documentation would be incrementally improved, like the codebase. We could start by just moving it to a different file. The narrow table also makes it difficult to read, so perhaps we can reformat that. A third column would be nice for examples, but it would mostly be empty initially. Some

Re: [Question] Unknown cost calculation/propagation in RelSubsets

Julian, many thanks for the insights. I'm obiously not able to know/find out where in the code those aggregate/combiner functions for RelSubsets are located. AFAIK there are no metadata handler methods inside the metadata handler implementations (in the form of `RelMdXXX implements

Re: Refactor reference.md

Extra documentation would be nice. But who is going to write (and maintain) this extra documentation? Even the current documentation takes a lot of work. When reviewing a PR to add a function, I have to tell people to remove a ‘.’ at the end of the line to be consistent with the existing doc.

RE: Re: [Question] Unknown cost calculation/propagation in RelSubsets

Hello, Right, I guess I understand what the color encoding means. Thanks for confirming my thoughts. If I remember correctly, the cost for a subset shown at a step should be the same as the best cost of all children for that particular step. Right and this is what confuses me since this

Re: Refactor reference.md

I think we should make a separate document for the functions, and in general give more details about the functions' behavior. The current model is to give a very brief description of the function, but that's often not enough, users have to resort to either experiments or to reading

[jira] [Created] (CALCITE-6222) Mysql does not have to_char function

Caican Cai created CALCITE-6222: --- Summary: Mysql does not have to_char function Key: CALCITE-6222 URL: https://issues.apache.org/jira/browse/CALCITE-6222 Project: Calcite Issue Type: Bug

Refactor reference.md

Hey Calcite Devs, I am currently working on CALCITE-6215 . During my work, I have noticed that certain functions have multiple variations with different parameter types in their respective databases. For example, in PostgreSQL, the to_char

[jira] [Created] (CALCITE-6221) Invalid query generated when the same table is joined multiple times

Ulrich Kramer created CALCITE-6221: -- Summary: Invalid query generated when the same table is joined multiple times Key: CALCITE-6221 URL: https://issues.apache.org/jira/browse/CALCITE-6221 Project: