2010Feb19
Progress report:
Chinua finished two basic search components and Zhimin will work on plugging backend data to them.
Repository Map:
Retain existing svn/FilteredPush project in repository as former project. Split out all major subprojects into svn/FP/FP- projects (using svn copy). Stop using svn/FilteredPush, and move all development work into the new svn/FP projects.
/FilteredPush
trunc_old/
trunk/
branches/
tags/
/FP/FP-Web/
trunk/fp-api.jar
trunk/fp-queuereader.jar
trunk/fp-mapper.jar
tags/
branches/
/FP/FP-IPT/
trunk/
tags/
branches/vendor-gbif
/FP/FP-Network/
trunk/
tags/
branches/
/FP/FP-GG/
trunk/
tags/
branches/vendor-goldengate
/FP/FP-WebUI/
trunk/
tags/
branches/
/FP/FP-specify/
trunk/
tags/
branches/vendor-specify
Discussed dependencies of components in deployment.
Data for demo
Discussed data needed for demo, and data locality in demo:
Clearly needed component is a minimal implementation of a mapper, driven by a configuration file.
Deployable components that can be used by clients are:
- fp-api.jar Message definitions and utility classes for composing messages.
- fp-queuereader.jar Client (excluding UI) for reading messages from queues
- fp-mapper.jar Two directional mapping between a local database and an exchange schema, provides API for analytical engine to pass through queries, provides API for clients to perform inserts and updates on local database.
Web Demo: 1.message queue cache in FP (need look at the functionality provided by ActiveMQ)
2.three datasets from Maureen (HUH, BBG, Arcadia, suitable for controled demo, but not for distribution)
