Mailing-List: contact user-help@flink.apache.org; run by ezmlm
Precedence: bulk
MIME-Version: 1.0
In-Reply-To: <1501500278159-14555.post@n4.nabble.com>
References: <1501248861742-14514.post@n4.nabble.com> <CAAdrtT1uFjNSmrZy80AE9y3pFOcG2Z1up2BR1u4ZLwAiHC=Eww@mail.gmail.com>
 <1501487551698-14549.post@n4.nabble.com> <CAAdrtT0aC+X32-SoPmPq82f01zWU2UA-HSwP-un21pAWJM_c8w@mail.gmail.com>
 <1501489185069-14551.post@n4.nabble.com> <1501500278159-14555.post@n4.nabble.com>
From: Fabian Hueske <fhueske@gmail.com>
Date: Mon, 31 Jul 2017 15:08:42 +0200
Message-ID: <CAAdrtT3MbCjKeN1Xj95r71sKMVaF=H_ifuQi+9Vr3brAHUyCFg@mail.gmail.com>
Subject: Re: Flink QueryableState with Sliding Window on RocksDB
To: Biplob Biswas <revolutionisme@gmail.com>
Cc: user <user@flink.apache.org>
Content-Type: multipart/alternative; boundary="f4030437a0a0b4ee1f05559cbc83"
archived-at: Mon, 31 Jul 2017 13:09:30 -0000

--f4030437a0a0b4ee1f05559cbc83
Content-Type: text/plain; charset="UTF-8"

I am not sure that this is impossible, but it is not the use case queryable
state was designed for.
I don't know the details of your application, but you could try to merge
the updating and the querying operators into a single one.

You could connect two streams with connect() and use a keyed
CoProcessFunction. This will have the advantages that all state access are
local.

Cheers, Fabian

2017-07-31 13:24 GMT+02:00 Biplob Biswas <revolutionisme@gmail.com>:

> Hi Fabian,
>
> I read about the process function and it seems a perfect fit for my
> requirement. Although while reading more about queryable-state I found that
> its not meant to do lookups within job (Your comment in the following
> link).
>
> http://apache-flink-user-mailing-list-archive.2336050.
> n4.nabble.com/Best-practices-to-maintain-reference-data-
> for-Flink-Jobs-td13215.html#a13233
>
> The thing is I wanted to maintain a local state store which is queryable
> within the same job such that one operator creates and updates it and then
> another operator queries the store based on a given key.
>
> I was hoping this to be possible but it seems not to be the case, can you
> shed some light and if possible recommend some alternatives?
>
> Regards,
> Biplob
>
>
>
> --
> View this message in context: http://apache-flink-user-
> mailing-list-archive.2336050.n4.nabble.com/Flink-
> QueryableState-with-Sliding-Window-on-RocksDB-tp14514p14555.html
> Sent from the Apache Flink User Mailing List archive. mailing list archive
> at Nabble.com.
>

--f4030437a0a0b4ee1f05559cbc83
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div>I am not sure that this is impossible, but =
it is not the use case queryable state was designed for.<br></div>I don&#39=
;t know the details of your application, but you could try to merge the upd=
ating and the querying operators into a single one.<br><br></div>You could =
connect two streams with connect() and use a keyed CoProcessFunction. This =
will have the advantages that all state access are local.<br><br></div>Chee=
rs, Fabian<br></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quot=
e">2017-07-31 13:24 GMT+02:00 Biplob Biswas <span dir=3D"ltr">&lt;<a href=
=3D"mailto:revolutionisme@gmail.com" target=3D"_blank">revolutionisme@gmail=
.com</a>&gt;</span>:<br><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Fabian,<br>
<br>
I read about the process function and it seems a perfect fit for my<br>
requirement. Although while reading more about queryable-state I found that=
<br>
its not meant to do lookups within job (Your comment in the following link)=
.<br>
<br>
<a href=3D"http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.=
com/Best-practices-to-maintain-reference-data-for-Flink-Jobs-td13215.html#a=
13233" rel=3D"noreferrer" target=3D"_blank">http://apache-flink-user-<wbr>m=
ailing-list-archive.2336050.<wbr>n4.nabble.com/Best-practices-<wbr>to-maint=
ain-reference-data-<wbr>for-Flink-Jobs-td13215.html#<wbr>a13233</a><br>
<br>
The thing is I wanted to maintain a local state store which is queryable<br=
>
within the same job such that one operator creates and updates it and then<=
br>
another operator queries the store based on a given key.<br>
<br>
I was hoping this to be possible but it seems not to be the case, can you<b=
r>
shed some light and if possible recommend some alternatives?<br>
<br>
Regards,<br>
Biplob<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href=3D"http://apache-flink-user-mailing-l=
ist-archive.2336050.n4.nabble.com/Flink-QueryableState-with-Sliding-Window-=
on-RocksDB-tp14514p14555.html" rel=3D"noreferrer" target=3D"_blank">http://=
apache-flink-user-<wbr>mailing-list-archive.2336050.<wbr>n4.nabble.com/Flin=
k-<wbr>QueryableState-with-Sliding-<wbr>Window-on-RocksDB-<wbr>tp14514p1455=
5.html</a><br>
<div class=3D"HOEnZb"><div class=3D"h5">Sent from the Apache Flink User Mai=
ling List archive. mailing list archive at Nabble.com.<br>
</div></div></blockquote></div><br></div>

--f4030437a0a0b4ee1f05559cbc83--