Hi Amit, Access to Kudu via the Impala JDBC interface do go through Impala, and should be accounted for in Impala resource and capacity planning. Access to Kudu via the Kudu Java client API do not go through Impala, and therefore do not need to be accounted for in Impala capacity planning. Usage of Kudu through Impala and through direct Java client access share Kudu, and therefore both should be accounted for when capacity planning for Kudu.
Hope this answers your question, Dan On Thu, Sep 14, 2017 at 10:37 AM, Amit Adhau <[email protected]> wrote: > Hi Team Kudu, > > I am not sure if it is a valid question or not, but their is below query, > which came up to me. > > Does Kudu uses the Impala query engine when we make a call to kudu tables > via Impala JDBC as well as via Kudu java API, if yes is their any impact at > resources and performance levels if it shares the Impala engine. > > Thanks, > Amit > > The information contained in this e-mail may be confidential. It has been > sent for the sole use of the intended recipient(s). If the reader of this > message is not an intended recipient, you are hereby notified that any > unauthorized review, use, disclosure, dissemination, distribution or > copying of this communication, or any of its contents, > is strictly prohibited. If you have received it by mistake please let us > know by e-mail immediately and delete it from your system. Many thanks. > > > > La información contenida en este mensaje puede ser confidencial. Ha sido > enviada para el uso exclusivo del destinatario(s) previsto. Si el lector de > este mensaje no fuera el destinatario previsto, por el presente queda Ud. > notificado que cualquier lectura, uso, publicación, diseminación, > distribución o copiado de esta comunicación o su contenido está > estrictamente prohibido. En caso de que Ud. hubiera recibido este mensaje > por error le agradeceremos notificarnos por e-mail inmediatamente y > eliminarlo de su sistema. Muchas gracias. > >
