Re: Columns used in query

2020-06-03 Thread Haisheng Yuan
Hi Gaurav, You may find this useful: https://lists.apache.org/thread.html/rc38d12de860f64e8e2926b7bcf6f2e9e6bcbfbc7ca5e886a71323b47%40%3Cdev.calcite.apache.org%3E On 2020/06/04 01:41:41, Gaurav Sehgal wrote: > Hi, > > I've a use case where i want to find all the columns, and their respective

Columns used in query

2020-06-03 Thread Gaurav Sehgal
Hi, I've a use case where i want to find all the columns, and their respective tables accessed in a sql query. I'm able to find all the table names by converting the sql query to RelNode and then visiting the TableScan node but not sure what would be the right approach to find all the column

Calcite-Master - Build # 1773 - Failure

2020-06-03 Thread Apache Jenkins Server
The Apache Jenkins build system has built Calcite-Master (build #1773) Status: Failure Check console output at https://builds.apache.org/job/Calcite-Master/1773/ to view the results.

Re: Avatica results mapping

2020-06-03 Thread Julian Hyde
This problem keeps on coming up. Avatica doesn't handle extended data types very well. I think we hard-code support for everything in java.sql.Types but then we hit the wall when things are "OTHER". There are also types that are widely used that are not in java.sql.Types - e.g. GEOMETRY. They may

Avatica results mapping

2020-06-03 Thread Jon Pither
Hi, I have a data-type I'm mapping as SqlTypeName/OTHER - in this case java.util.UUID. When I return this field from an enumerator via an adapter it works OK - the UUID is passed through into the JDBC result set. Over the wire though, Avatica throws an error " Remote driver error:

[jira] [Created] (CALCITE-4040) Nonstandard SqlAggFunction rollup NPE Exception

2020-06-03 Thread xzh_dz (Jira)
xzh_dz created CALCITE-4040: --- Summary: Nonstandard SqlAggFunction rollup NPE Exception Key: CALCITE-4040 URL: https://issues.apache.org/jira/browse/CALCITE-4040 Project: Calcite Issue Type: Wish

Re: Using indexes rather than table scans with Calcite

2020-06-03 Thread Roman Kondakov
Hi Haisheng, > If I didn't get it wrong, joining with scan_A means it has to read all the > tuples from table A, this will make index meaningless, because the purpose of > using index in that example is to avoid reading all the tuples from table A. I meant 'rowId' as a physical address (ctid