[ 
https://issues.apache.org/jira/browse/BEAM-10305?focusedWorklogId=451005&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-451005
 ]

ASF GitHub Bot logged work on BEAM-10305:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 25/Jun/20 13:04
            Start Date: 25/Jun/20 13:04
    Worklog Time Spent: 10m 
      Work Description: mxm commented on pull request #12062:
URL: https://github.com/apache/beam/pull/12062#issuecomment-649527323


   Unrelated test failures in 
https://ci-beam.apache.org/job/beam_PreCommit_Java_Phrase/2367/
   
   ```
   14:39:21 FAILURE: Build completed with 2 failures.
   14:39:21 
   14:39:21 1: Task failed with an exception.
   14:39:21 -----------
   14:39:21 * What went wrong:
   14:39:21 Execution failed for task ':sdks:java:io:jdbc:test'.
   14:39:21 > There were failing tests. See the report at: 
file:///home/jenkins/jenkins-slave/workspace/beam_PreCommit_Java_Phrase/src/sdks/java/io/jdbc/build/reports/tests/test/index.html
   14:39:21 
   14:39:21 * Try:
   14:39:21 Run with --stacktrace option to get the stack trace. Run with 
--info or --debug option to get more log output. Run with --scan to get full 
insights.
   14:39:21 
==============================================================================
   14:39:21 
   14:39:21 2: Task failed with an exception.
   14:39:21 -----------
   14:39:21 * What went wrong:
   14:39:21 Execution failed for task ':sdks:java:io:rabbitmq:test'.
   14:39:21 > Process 'Gradle Test Executor 124' finished with non-zero exit 
value 143
   14:39:21   This problem might be caused by incorrect test process 
configuration.
   14:39:21   Please refer to the test execution section in the User Manual at 
https://docs.gradle.org/5.2.1/userguide/java_testing.html#sec:test_execution
   14:39:21 
   ```


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 451005)
    Time Spent: 3h  (was: 2h 50m)

> InMemoryBagUserStateFactory creates a cache token per state cell
> ----------------------------------------------------------------
>
>                 Key: BEAM-10305
>                 URL: https://issues.apache.org/jira/browse/BEAM-10305
>             Project: Beam
>          Issue Type: Bug
>          Components: java-fn-execution, runner-flink, sdk-py-harness
>            Reporter: Maximilian Michels
>            Assignee: Maximilian Michels
>            Priority: P3
>          Time Spent: 3h
>  Remaining Estimate: 0h
>
> When the state cache is enabled in the Python SDK, the batch mode of the 
> Flink Runner currently only allows a single user state cell because a new 
> cache token is generated for each state cell; the caching code in the Python 
> SDK Harness only supports one cache token per user state handler. 
> Theoretically multiple cache tokens would work but would just be adding to 
> the payload. We should make sure to just send a single cache token in batch 
> mode (which is already the case in streaming)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to