I'm actually looking at (I) now. I'm starting small with pirk-63. A WIP PR should be in late tonight. This will keep the driver from needing all framework dependencies, but we'll need to discuss passing framework specific options as well.
I could definitely see the use case for separate responder jars. Especially, given that some potential users may need to incorporate custom in-house (or commercial) frameworks that can't be part of pirk due to license issues. Is there an umbrella Jira for this? On Sep 14, 2016 8:16 AM, "Suneel Marthi" <[email protected]> wrote: > On Wed, Sep 14, 2016 at 2:06 PM, Tim Ellison <[email protected]> > wrote: > > > I'm reluctant to dive into more Pirk dev at the moment because > > > > (i) there was plenty of discussion around the release about > > restructuring the code base into a number of modules. I figure that > > will be a disruptive change best undertaken with most folks "out of the > > pool". > > > > This is a top priority IMO. We can start the discussions around how do we > wanna modularize Pirk. > > Would there be use cases wherein some application just needs the Responder > only as a jar. > > OR > > Responder on Storm jar, Responder on Flink jar .... > > Same thing with Query. > > the rest of the classes could probably be part of a "pirk-core" module (and > its own jar) > > > > > > (ii) I have failed to set up a reliable distributed testing system for > > myself, and wholeheartedly agree that distrib testing is important for > > all devs. Hopefully I can fix that as improved instructions come along, > > though perhaps we should be approaching infra to get a shared Pirk > > cluster available for testing? > > > > Does Apache Infra provide a hadoop/spark cluster? I didn't think they did > but I could be wrong. > > > > > > (iii) other stuff gets in the way :-) > > > > I realise that these are within my powers to address, and I'm still keen > > to participate in moving Pirk forward; so what is the next hill to > > conquer for the project? > > > > Regards, > > Tim > > > > I am presently in Berlin attending #FlinkForward and will be back home next > week. We can start discussions around the next steps and plan for the next > release. >
