ASF GitHub Bot logged work on BEAM-3485:

                Author: ASF GitHub Bot
            Created on: 13/Apr/18 13:41
            Start Date: 13/Apr/18 13:41
    Worklog Time Spent: 10m 
      Work Description: adejanovski commented on issue #5124: [BEAM-3485] Fix 
split generation for Cassandra clusters
URL: https://github.com/apache/beam/pull/5124#issuecomment-381138950
   Hi @iemejia, I was actually working on BEAM-4049 when I noticed that split 
generation was broken.
   Since I could tackle it in a very short time, that there didn't seem to be 
activity on the ticket and that the tickets seem to be assigned automatically 
upon creation, I assumed it was ok to send a PR.
   I'll follow your guidelines in the future and get a green light before 
working on existing tickets.

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:

Issue Time Tracking

    Worklog Id:     (was: 90813)
    Time Spent: 1h 20m  (was: 1h 10m)

> CassandraIO.read() splitting produces invalid queries
> -----------------------------------------------------
>                 Key: BEAM-3485
>                 URL: https://issues.apache.org/jira/browse/BEAM-3485
>             Project: Beam
>          Issue Type: Bug
>          Components: io-java-cassandra
>            Reporter: Eugene Kirpichov
>            Assignee: Alexey Romanenko
>            Priority: Major
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
> See 
> [https://stackoverflow.com/questions/48090668/how-to-increase-dataflow-read-parallelism-from-cassandra/48131264?noredirect=1#comment83548442_48131264]
> As the question author points out, the error is likely that token($pk) should 
> be token(pk). This was likely masked by BEAM-3424 and BEAM-3425, and the 
> splitting code path effectively was never invoked, and was broken from the 
> first PR - so there are likely other bugs.
> When testing this issue, we must ensure good code coverage in an IT against a 
> real Cassandra instance.

This message was sent by Atlassian JIRA

Reply via email to