Hi Chet,
the following thins may create the error you mentioned:
* the job ID of the query must match the ID of the running job
* the job is not running anymore
* the queryableStateName does not match the string given to
setQueryable("query-name")
* the queried key does not exist (note that you need to give its hash(!) in
the getKvState() method)
* something is wrong with the keyAndNamespace serialization - the following in
Java:
final byte[] serializedKey =
KvStateRequestSerializer.serializeKeyAndNamespace(
key, keySerializer,
VoidNamespace.INSTANCE, VoidNamespaceSerializer.INSTANCE);I have only tested the Java API though which you could try for reference. Regards Nico On Monday, 13 March 2017 12:14:26 CET Fabian Hueske wrote: > Hi Chet, > > Nico or Ufuk (in CC) should be able to help you. > > Thanks, > Fabian > > 2017-03-13 11:23 GMT+01:00 Chet Masterson <chet.master...@yandex.com>: > > Any guidance on troubleshooting error > > > > Error: No KvStateLocation found for KvState instance with name XXXXX > > > > when trying to make a queryable state call in Flink 1.2.0? > > > > I do know the server is receiving the call made from the remote client. > > (query.server.enable = true on the server in flink-conf.yaml, that is the > > only setting I changed there) > > > > I'm following the guidelines documented here: > > > > https://ci.apache.org/projects/flink/flink-docs-release-1.2/dev/stream/ > > queryable_state.html > > > > under 'Managed Keyed State' > > > > I do understand this feature is 'highly experimental', and my code is in > > Scala, so I am also following the instructions under 'Note for Scala > > Users' > > in the documentation.
signature.asc
Description: This is a digitally signed message part.
