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
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
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
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
async
session, I think because it was easier just to use the sync client for
writing.
- Dan
On Mon, Apr 9, 2018 at 3:10 AM, José Ribeiro
wrote:
> Hello, I'm having difficulties in the AsyncKudu API. Since there isn't any
> valuable examples with asynchronous kudu client, can you
Hello, I'm having difficulties in the AsyncKudu API. Since there isn't any
valuable examples with asynchronous kudu client, can you please help me in this
example?
I want to use AsyncKudu to write in the kudu database. The steps i want to use
are:
1. verify that the table exists
