Yes, a cache of PreparedStatement. I suppose that cache could be in Calcite but it’s better if it could be in your app server.
See https://issues.apache.org/jira/browse/CALCITE-963 <https://issues.apache.org/jira/browse/CALCITE-963>. Julian > On Aug 23, 2016, at 7:50 AM, Tajdar Siddiqui <siddi...@yahoo.com> wrote: > > 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 <jh...@apache.org> > To: dev@calcite.apache.org; "siddi...@yahoo.com" <siddi...@yahoo.com> > 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 <siddi...@yahoo.com.INVALID > > <mailto:siddi...@yahoo.com.INVALID>> 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 > >
