Thanx for your response.
I was playing around with kylin 1.5.2.1/calcite 1.6.0.Yes, the queries are
limited and similar (params differ based on the user executing this query).
So the approach would be to use a PreparedStatement Cache ?
From: Julian Hyde <[email protected]>
To: [email protected]; "[email protected]" <[email protected]>
Sent: Thursday, August 11, 2016 6:20 PM
Subject: Re: Bindable cache
I guess it could cache them. What usage pattern do you have? If you are
executing a lot of similar or identical queries, would it be possible to use
Connection.prepareStatement instead?
Julian
> On Aug 11, 2016, at 3:55 PM, Tajdar Siddiqui <[email protected]>
> wrote:
>
> Newbie to Calcite.
> The class org.apache.calcite.adapter.enumerable.EnumerableInterpretable
> toBindable call, could it cache the generated Bindable classes ?
> Thanx,
>
> Sent from Yahoo Mail on Android
