GitHub user DarinJ opened a pull request:
https://github.com/apache/incubator-pirk/pull/119
Submodule Refactor Phase 1
This is going to have to be broken into chunks.
1. Pulled out mapreduce, storm and spark (sparkstreaming in spark)
responders.
2. Added methods to ResponderPlugin interface to setup a responder for a
test and return the decrypted response.
3. Refactored org.apache.pirk.test.DistributedTestSuite,
org.apache.pirk.test.Utils.BaseTests to handle submodules. This will likely
need more work as the unit tests in pirk-core depend on some of the code in
org.apache.pirk.test.Utils.BaseTests as a goal is to pull the distributed tests
into a submodule.
Tested on a local k8s cluster and AWS. With the caveat the test jar to use
is now pirk-mapreduce-0.2.0.jar or pirk-spark-0.2.0.jar.
There's several additional steps that need to happen, but I think that a
lot must first be address with configuration and commandline first so I'd like
to get this in and iterate the two in parallel.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/DarinJ/incubator-pirk submoduleRefactor
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-pirk/pull/119.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #119
----
commit add9096d1e8bddcfc3448c2495699f51bac4183c
Author: Darin Johnson <[email protected]>
Date: 2016-09-29T02:44:31Z
Submodule Refactor Phase
-1. Pulled out mapreduce, storm and spark responders,
-2. Refactored `org.apache.pirk.test.DistributedTestSuite` to handle
submodules.
Todo Pull out Querier, Responder Modules as mentioned on the mailing list.
This will be done separately as it involved decoupling several components.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
