ASF GitHub Bot logged work on BEAM-3995:

                Author: ASF GitHub Bot
            Created on: 11/Apr/18 08:04
            Start Date: 11/Apr/18 08:04
    Worklog Time Spent: 10m 
      Work Description: echauchot commented on issue #5051: [BEAM-3995] Add 
basic Gradle run task to Nexmark
URL: https://github.com/apache/beam/pull/5051#issuecomment-380357483
   I have recently updated the nexmark support matrix on the website after 
running all the test suites. Runners and modes that support 100% of the queries 
   - on direct runner in batch mode
   - on direct runner in streaming mode
   - on flink runner in batch mode
   - on flink runner in streaming mode
   - on spark runner in batch mode
   => I think we should schedule all these runs
   It is a pity that we can not run spark in streaming mode but we still have 
major issues with it in streaming mode:
   - state support 
   - timer support
   - pcollectionView support
   - spark does not comply to the user given timeout in `waitUntilFinish` 
probably because it forks a lot of micro-batches and, to gracefull stop the 
pipeline, the underlining spark engine needs to wait for all of them leading to 
almost never-ending benchmark suites.

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: 89838)
    Time Spent: 4h 40m  (was: 4.5h)

> Launch Nexmark suites from gradle and update web page docs
> ----------------------------------------------------------
>                 Key: BEAM-3995
>                 URL: https://issues.apache.org/jira/browse/BEAM-3995
>             Project: Beam
>          Issue Type: Sub-task
>          Components: examples-nexmark, website
>            Reporter: Kenneth Knowles
>            Assignee: Kenneth Knowles
>            Priority: Major
>          Time Spent: 4h 40m
>  Remaining Estimate: 0h
> Currently our instructions for running Nexmark benchmarks on various runners 
> is pretty tightly tied to Maven. We need a good story for running them with 
> gradle (or just building an executable with gradle and running that 
> standalone).

This message was sent by Atlassian JIRA

Reply via email to