calcite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dylan Heitz <>
Subject Re: Bindable Baz.bind(DataContext) issue
Date Thu, 09 Aug 2018 14:52:35 GMT
Thank you Vladimir and Andrei, 

Well I thought that the query wasn't executed correctly since it gave me no results but I
just found out this was another issue... So this is working fine even with an array of terms
for filters. 
But it can be useful later to know where this is done :) 

Thanks again, 


From: "Andrei Sereda" <> 
Sent: Thursday, August 9, 2018 3:28:56 PM 
Subject: Re: Bindable Baz.bind(DataContext) issue 


The query translation is happening in PredicateAnalyzer 

(called inside ElasticsearchFilter). 
Any reason why you want match query instead of term 


On Thu, Aug 9, 2018 at 6:06 AM Vladimir Sitnikov <> wrote: 

> Dylan>What can I do to see the source code of the method bindable.bind() to 
> change the way of serializing the SQL query into JSON query ? 
> You might find adding -Dcalcite.debug=true entertaining (see 
> ) 
> Baz code is generated on the fly, so there's no sources in git for it, 
> however if you supply `-Dcalcite.debug=true`, then the sources will be 
> printed to the console. 
> However, it looks like you want to inspect 

> or something like that since translation of rel expressions to JSON query 
> is placed there. 
> PS. We might want to add an option to actually save the generated sources 
> in the file system, so IDE might be able to set breakpoints and 
> step-by-step execute the generated on the fly sources as well. 
> Vladimir 

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message