beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Work logged] (BEAM-4399) Change CassandraIOIT to write-then-read Performance Tests
Date Mon, 18 Jun 2018 15:04:00 GMT


ASF GitHub Bot logged work on BEAM-4399:

                Author: ASF GitHub Bot
            Created on: 18/Jun/18 15:03
            Start Date: 18/Jun/18 15:03
    Worklog Time Spent: 10m 
      Work Description: lgajowy commented on issue #5632: [BEAM-4399] Change CassandraIOIT
to write-then-read
   LGTM, thanks!
   I agree that the problems discovered by this test should be addressed by some different
JIRA ticket. Could you create one @iemejia? 

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: 112776)
    Time Spent: 4h  (was: 3h 50m)

> Change CassandraIOIT to write-then-read Performance Tests
> ---------------------------------------------------------
>                 Key: BEAM-4399
>                 URL:
>             Project: Beam
>          Issue Type: Sub-task
>          Components: testing
>            Reporter: Łukasz Gajowy
>            Assignee: Ismaël Mejía
>            Priority: Minor
>          Time Spent: 4h
>  Remaining Estimate: 0h
> CassandraIOIT is different than other IOITs (such as JdbcIOIT or MongodbIOIT) and does
not fulfil the rules described in the documentation: []. 
> We should make it coherent with other tests, more specifically: 
>  - write it in writeThenReadAll style
>  - enable running it with Perfkit
>  - provide Jenkins job to run it periodically

This message was sent by Atlassian JIRA

View raw message