[
https://issues.apache.org/jira/browse/BEAM-4706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16532438#comment-16532438
]
Lukasz Gajowy commented on BEAM-4706:
-------------------------------------
Now it is possible to run this test using designated gradle tasks. Example
runs:
using perfkit high-level task:
{code}
./gradlew performanceTest -DpkbLocation="<PERFKIT_LOCATION>"
-DintegrationTestPipelineOptions='["--tempLocation=gs://<your-location>/",
"--project=<your project>", "--tempRoot=gs:/<your-temp-root>"]'
-DitModule=examples/java
-DintegrationTest=org.apache.beam.examples.cookbook.BigQueryTornadoesIT
-DintegrationTestRunner=dataflow
{code}
using low-level integration test task (all pipeline options have to be set
manually):
{code}
./gradlew integrationTest -p examples/java/
-DintegrationTestPipelineOptions='["--tempLocation=gs://<your-location>,
"--project=<gcp-project>", "--tempRoot=gs://<your-temp-root>",
"--runner=TestDataflowRunner"]' --tests
org.apache.beam.examples.cookbook.BigQueryTornadoesIT
-DintegrationTestRunner=dataflow
{code}
it can be also run using direct runner (this is described in
BigQueryTornadoesIT class' docs now).
FYI: IOIT documentation is being improved in [a separate
PR|https://github.com/apache/beam-site/pull/465]. It' doesn't cover
BigQueryTornadoes though. I wrote the examples above to be used at least until
appropriate docs appear.
> BigQueryTornadoesIT cannot be run using integrationTest and performanceTest
> tasks
> ---------------------------------------------------------------------------------
>
> Key: BEAM-4706
> URL: https://issues.apache.org/jira/browse/BEAM-4706
> Project: Beam
> Issue Type: Bug
> Components: testing
> Reporter: Lukasz Gajowy
> Assignee: Kasia Kucharczyk
> Priority: Major
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> It seems that we cannot run this test using tasks from BuildModulePlugin
> designed to run such tests. Those are not included in build.gradle of
> examples module. There's a possibility that some other tests are not able to
> run due to this reason (this also has to be checked).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
