Hi Robert,
It seems "type" was what I needed. This it also looks like the test
jar has an undeclared dependency. In the end, the following allowed me
to use TestStreamEnvironment for my integration test. Thanks a lot!
-n
<dependency>
<groupId>org.apache.flink</groupId>
<artifactId>flink-streaming-core</artifactId>
<version>${flink.version}</version>
<type>test-jar</type>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.apache.flink</groupId>
<artifactId>flink-test-utils</artifactId>
<version>${flink.version}</version>
<scope>test</scope>
</dependency>
On Thu, Nov 5, 2015 at 12:47 PM, Robert Metzger <[email protected]> wrote:
> Hi Nick,
>
> we are usually publishing the test artifacts. Can you try and replace the
> <classifier> tag by <type>test-jar<type>:
>
> <dependency>
> <groupId>org.apache.flink</groupId>
> <artifactId>flink-streaming-core</artifactId>
> <version>${flink.version}</version>
> <type>test-jar</type>
> <scope>test</scope>
> </dependency>
>
>
> On Thu, Nov 5, 2015 at 8:18 PM, Nick Dimiduk <[email protected]> wrote:
>>
>> Hello,
>>
>> I'm attempting integration tests for my streaming flows. I'd like to
>> produce an input stream of java objects and sink the results into a
>> collection for verification via JUnit asserts.
>> StreamExecutionEnvironment provides methods for the former, however,
>> how to achieve the latter is not evident based on my internet
>> searching. I think I've found a solution in the TestStreamEnvironment
>> class, ie, as used by WindowingIntegrationTest. However, this class
>> appears to be packaged in the flink-streaming-core test artifact,
>> which is not published to maven.
>>
>> For reference, this is the maven dependency stanza I'm using. Please
>> let me know if I've got it wrong.
>>
>> Thanks,
>> Nick
>>
>> <dependency>
>> <groupId>org.apache.flink</groupId>
>> <artifactId>flink-streaming-core</artifactId>
>> <version>${flink.version}</version>
>> <classifier>test</classifier>
>> <scope>test</scope>
>> </dependency>
>
>
