We extend the official container and the jar is available under ./lib – so it wasn't enabled by default, we moved the jar under ./lib and then build the container+application.
--- Oytun Tez *M O T A W O R D* The World's Fastest Human Translation Platform. oy...@motaword.com — www.motaword.com On Tue, Jul 30, 2019 at 3:42 AM Fabian Hueske <fhue...@gmail.com> wrote: > Hi Oytun, > > Is QS enabled in your Docker image or did you enable QS by copying/moving > flink-queryable-state-runtime_2.11-1.8.0.jar from ./opt to ./lib [1]? > > Best, Fabian > > [1] > https://ci.apache.org/projects/flink/flink-docs-stable/dev/stream/state/queryable_state.html#activating-queryable-state > > Am Mo., 29. Juli 2019 um 22:46 Uhr schrieb Oytun Tez <oy...@motaword.com>: > >> And, Flink version: 1.8, incl. Docker container (official flink:1.8 tag) >> >> --- >> Oytun Tez >> >> *M O T A W O R D* >> The World's Fastest Human Translation Platform. >> oy...@motaword.com — www.motaword.com >> >> >> On Mon, Jul 29, 2019 at 4:32 PM Oytun Tez <oy...@motaword.com> wrote: >> >>> Hi there, >>> >>> We have a job that is run inside Docker via `standalone-job.sh >>> start-foreground --job-classname`, with 1 task manager. I've been >>> trying to make QueryableState available in this setup for 2 days now and I >>> can't seem to enable it. >>> >>> If I create a LocalEnvironment within the code itself and provide >>> queryable-state.enable: >>> true config directly via Configuration, then I can at least see that >>> the queryable state server is spinning up. >>> >>> Any pointers? With standalone-job.sh, it seems that it doesn't care >>> about queryable-state.enable config inside flink-conf.yaml. >>> >>> --- >>> Oytun Tez >>> >>> *M O T A W O R D* >>> The World's Fastest Human Translation Platform. >>> oy...@motaword.com — www.motaword.com >>> >>
