Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial release features support for Hdfs #5

Open
6 tasks
silkentrance opened this issue Feb 22, 2018 · 0 comments
Open
6 tasks

Initial release features support for Hdfs #5

silkentrance opened this issue Feb 22, 2018 · 0 comments

Comments

@silkentrance
Copy link
Member

silkentrance commented Feb 22, 2018

As a test developer I need to have a working Hdfs instance. While I do not need direct access to that instance, it should be available for integration with other Hadoop components.

I want to be able to configure the Hdfs instance by means of annotating the test class.

When running tests in parallel, I want the system to not start multiple Hdfs instances for a specific test class or a suite of test classes that derive from a common super class which provides the Hdfs configuration. Instead, all of these threads must share the same instance. In effect, there is only one Hdfs instance that is shared across all threads.

Running the same tests on the same system from multiple processes must not lead to failing tests. Individual instances of Hdfs must have their own ports. The ports must be determined automatically.

In addition I want to be able to access the Filesystem by means of both parameter and field injection.

Acceptance criteria

  • Hdfs is provided
  • Hdfs instances can be configured via annotation on ElementType.TYPE level
  • There is only one Hdfs instance that is shared across multiple threads
  • The effective Hdfs instance configuration is used for configuring other provided components
  • Hdfs instances use dedicated free ports that have been determined automatically
  • Filesystem can be injected into both fields and parameters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant