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

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

                Author: ASF GitHub Bot
            Created on: 18/Oct/18 01:07
            Start Date: 18/Oct/18 01:07
    Worklog Time Spent: 10m 
      Work Description: aaltay commented on issue #6651: [BEAM-5714] Fix 
RedisIO EXEC without MULTI error
URL: https://github.com/apache/beam/pull/6651#issuecomment-430840645
 
 
   Based on my read on https://redis.io/topics/transactions this change looks 
correct. I will merge this since it has been open for a week, and it is a small 
change passing tests. (Feel free to revert if this does not make sense.)
   
   Thank you @kkpoon!

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 155665)
    Time Spent: 50m  (was: 40m)

> RedisIO emit error of EXEC without MULTI
> ----------------------------------------
>
>                 Key: BEAM-5714
>                 URL: https://issues.apache.org/jira/browse/BEAM-5714
>             Project: Beam
>          Issue Type: Bug
>          Components: io-java-redis
>    Affects Versions: 2.7.0
>            Reporter: K.K. POON
>            Assignee: Jean-Baptiste Onofré
>            Priority: Major
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> RedisIO has EXEC without MULTI error after SET a batch of records.
>  
> By looking at the source code, I guess there is missing `pipeline.multi();` 
> after exec() the last batch.
> [https://github.com/apache/beam/blob/master/sdks/java/io/redis/src/main/java/org/apache/beam/sdk/io/redis/RedisIO.java#L555]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to