gt; > Best Regards,
> >
> > Jiayi Liao
> >
> > Original Message
> > *Sender:* vino yang
> > *Recipient:* Georgi Stoyanov
> > *Cc:* dev; user; Stefan
> > Richter; Aljoscha Krettek;
> > kklou...@gmail.com; Stephan Ewen;
> > l...@apache.org; Tz
Tai
> *Date:* Tuesday, Jul 2, 2019 16:45
> *Subject:* Re: RE: [DISCUSS] Improve Queryable State and introduce
> aQueryServerProxy component
>
> Hi all,
>
> In the past, I have tried to further refine the design of this topic
> thread and wrote a design document to give mor
richters.rich...@ververica.com; Aljoscha krettekaljos...@apache.org;
kkloudas@gmail.comkklou...@gmail.com; Stephan ewense...@apache.org;
liyu@apache.orgl...@apache.org; Tzu-Li (Gordon) taitzuli...@apache.org
Date:Tuesday, Jul 2, 2019 16:45
Subject:Re: RE: [DISCUSS] Improve Queryable State and introduce
.apache.org
> Date:Friday, Apr 26, 2019 16:41
> Subject:Re: [DISCUSS] Improve Queryable State and introduce
> aQueryServerProxy component
>
>
> Hi Paul, Thanks for your reply. You are right, currently, the queryable
> state has few users. And I totally agree with you, it makes t
: [DISCUSS] Improve Queryable State and introduce aQueryServerProxy
component
Hi Paul, Thanks for your reply. You are right, currently, the queryable state
has few users. And I totally agree with you, it makes the streaming works more
like a DB. About the architecture and the problem you concern
