[GitHub] [beam] damccorm opened a new issue, #19784: Support passing stateBackend through pipeline options in python sdks

[GitBox <gi...@apache.org>]

damccorm opened a new issue, #19784:
URL: https://github.com/apache/beam/issues/19784

   Currently the only way for python sdks to instruct flink to use a StateBackend different than the default (MemoryStateBackend) would be to specify state.backend in flink-conf.yaml, which creates the limitation of using the same statebackend for every job running on the same flink cluster. Ideally we should be able to pass it in to flink runner through PipelineOptions. Here's the error it spits out when I flag  \--state_backend=RocksDBStateBackend:
   
    
   ```
   
   RuntimeError: Pipeline failed in state FAILED: com.fasterxml.jackson.databind.exc.InvalidDefinitionException:
   Cannot construct instance of `org.apache.flink.runtime.state.StateBackend` (no Creators, like default
   construct, exist): abstract types either need to be mapped to concrete types, have custom deserializer,
   or contain additional type information
    at [Source: (String)""RocksDBStateBackend""; line: 1, column:
   1]
   
   ```
   
   Acceptance Criteria:
   
   Flink StateBackend is configurable via command line options from python.
   
    
   
   Imported from Jira [BEAM-8112](https://issues.apache.org/jira/browse/BEAM-8112). Original Jira may contain additional context.
   Reported by: catlynk.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org