Re: AsyncKudu

lient in that scenario. - Dan > > -José > -- > *De:* Dan Burkert > *Enviado:* 9 de abril de 2018 18:32:43 > > *Para:* user@kudu.apache.org > *Assunto:* Re: AsyncKudu > > Hi José, > > I would consider doing this a little bit diff

Re: AsyncKudu

Enviado: 9 de abril de 2018 18:32:43 Para: user@kudu.apache.org Assunto: Re: AsyncKudu Hi José, I would consider doing this a little bit differently. The only circumstances I'm aware of where it's necessary to use the async session is when you are attempting to write to Kudu from a

Re: AsyncKudu

duClient.tableExists(tableName)); > } > > > A little of the background of my project. The clients read and write on > other Database, and when they write something, the same information is sent > to Kudu. I don't want to block the client with the Kudu part, because the > client only need

Re: AsyncKudu

thing, the same information is sent to Kudu. I don't want to block the client with the Kudu part, because the client only needs the other DataBase to work. José Ribeiro ________ De: Dan Burkert Enviado: 9 de abril de 2018 17:21 Para: user@kudu.apache.org Assunto: Re: A

Re: AsyncKudu

Hi José, The Deferred class is indeed pretty difficult to come to grips with, which is why we don't really recommend the async API for most use cases. I've personally found the Deferred class docs to be pretty useful when getting u