Hi Adi, On Wed, Feb 25, 2015 at 12:34 AM, Aditya Dhulipala <[email protected]> wrote:
> Hi Lewis, > > I was going through the path you posted earlier. OODT- 658 > https://issues.apache.org/jira/browse/OODT-658 > > I think this is a substantial part of the project we're currently talking > about (XML-RPC overhaul). > Substantial may be a wee bit optimistic ;) But yes a significant portion of thinking in to the OODT data structures logic has been done. We DO need to implement Metadata in exactly the right way without loosing existing functionality so please begin to think about that. https://github.com/apache/oodt/blob/trunk/metadata/src/main/java/org/apache/oodt/cas/metadata/Metadata.java > My understanding is that this patch was implemented to make Apache Gora > communicate with OODT, so that's why you've implemented the schema > definitions for all the data structures used by OODT. > Correct > Gora generates some statically typed code from this schema > Using the GoraCompiler http://gora.apache.org/current/compiler.html, invoked via CompilerCLI > and the next step is to implement OODT logic to store the data in Gora (as > opposed to MySQL or Solr) > YES. This will tidy A LOT of the current configuration up. Will also have a unified and well documented manner for configuring the mappings and datastore specific configuration. All of the Gora datastores are documented here http://gora.apache.org/current/index.html I've been hacking away on documentation for Gora for about a year so it is now relatively OK. I hope you find it useful. > > So from the viewpoint of the project we're talking about i.e. Replacing > XML-RPC with Avro, > the schema definition part is pretty much done (or almost done? Need to > define it within OODT as well?). > Note, that NONE of the Avro RPC logic is implemented. So it is nowhere nearly done ;) The core project definition is still to be addressed and I am nearly 100% sure that we will have some trciky issues to address regarding 1) maintaining as close to backwards compatability as possible 2) documenting the entire Avro RPC communications within OODT, 3) Hooking up all services, 4) Testing the new implementation, 5) regression testing it against the existing XML-RPC layer, 6) setting a roadmap fro deprecation and eventual removal of the XML-RPC material > The next step would be to define RPC logic for the client server > communication within OODT itself i.e. within filemgr, workflowmgr etc. > Correct, this should make up the majority of your proposal OK. > > Am I correct in understanding this? > > > Yes and thank you for joining the dots, it is nice to see a student interpreting and investigating the problem this much prior to the project starting. I am really looking forward to this now. Thanks LEwis
