Monday, February 02, 2009

MeTA Studio update: map-reduce, editor, bug fixes

New online update is available (version 2.0.03022009) [accessible via. Help->Check for Updates with in the IDE].

Before any thing,
Very Important:

After applying this update remove the following file from metastudio settings before restarting:
~/.meta2.0/launcherConfig.xml

Note that depending on the OS, ~ should be appropriately replaced. For Windows Vista this is in C:\Users\< user-name >, for earlier windows its C:\Documents and Settings\< users-name >, for UNIX/Linux this is usually /home/< user-name >, for OSX it is /Users/< user-name >.

This is required because the way MeTA Studio is launched has completely changed from this version to allow purely non-gui MeTA Studio demon (using --daemon command line switch) to be running, even on machines that do not have graphical environment.

Future additions to the current version:

- The Molecule option in IDE now provides and additional option to create a new molecule using in built (yet to be complete) MoleculeEditor. This is highly experimental and its functionality is going to change over time. Don't complain at this stage ;) but suggestions are welcome :)

- The mapreduce framework is now usable, but not yet complete. To test out this framework you can use the scripts from http://tovganesh.googlepages.com/mapreduce.zip, try running mapreduce.bsh from IDE [Tools -> Open Code Editor]. Every thing else, at this point, I guess is self explanatory ;)

The current mapreduce framework has a slow start and does not yet handle node failures. Note of security: mapreduce involves remote execution of BeanShell scripts. By default MeTA Studio prompts for any action relating to Federation framework (mapreduce is implemented over the Federation APIs). This can be appropriately configured as suited from with in IDE [Preference -> Federation Security Rules].

- Includes a usual list of bug fixes
- But does not include updated help for the new mapreduce APIs and no source update yet ... I plan to do this in the next iteration.

have fun!

No comments: