I'd like to think that the new config system takes care a lot of chores for you:
1. You client program should work as is if you just specify a config file as the second argument of the Client constructor. 2. Just using Config::init_with_policy<DefaultCommPolicy>(argc, argv) will take care of a lot of options including the --config option to read from. So all the config related code would just reduce to one line. 3. Config::init_with_* allow you to specify any config options on the command line. Type --help-file will show you the complete properties references including their default values. 4. The policies stuff allows us to compose different client programs without rewriting a lot of similar option/config related code (20+ lines -> 1 or 2 line) Perhaps the best way to show how it works is to rewrite the main function of one of your client programs. Just post it here or send it to me and I'll show you several ways how to take advantage of the new config system. __Luke On Dec 12, 4:38 am, Phoenix <[email protected]> wrote: > Hi Doug, > > Oh, sorry. Java6 was mentioned. I missed it. > > And now it seems that the config is a problem for me. Can you give > some instructions? And the apache example is out of date. Perhaps > it's time to update it. > > Thank you. :) > > Best wishes > > On Dec 12, 7:16 pm, Phoenix <[email protected]> wrote: > > > Hi Doug, > > > According to the src, now the config-options need something called > > Policy which makes it hard to write client program. > > > In older versions I can run a client program on another machine that > > just needs a config file. But now it seems hard to do so. The > > configurations is get from the Config namespace, I donnot know how to > > force it read from a local config file. I tried the Properties ::load > > but failed. A Properties constructor which accepts a config file as a > > parameter may help a lot. > > > Perhaps we need more and update examples. And also the Makefile now > > needs more libraries to link with. An example is helpful. > > > BTW, the DfsBroker is using java6 now. It would be better to mention > > this in the log. As the earlier version can be used with java5. > > > Best wishes. > > > On Dec 9, 5:07 am, "Doug Judd" <[email protected]> wrote: > > > > This latest version of Hypertable is incompatible with older versions. > > > Here > > > is a list of the incompatibilities: > > > > 1. All timeouts have changed from seconds to milliseconds > > > 2. Hyperspace data format has changed > > > 3. Network wire protocol has changed > > > > To use this release, you will have to start with a clean database. If you > > > have any pre-existing config files, you will have to modify them by > > > changing > > > all of the time properties from *seconds* to *milliseconds*. Also, there > > > are a few more build dependencies: > > > > SIGAR (http://sourceforge.net/projects/sigar/) > > > libevent (only required for optional ThriftBroker build) > > > thrift (only required for optional ThriftBroker build) > > > > - Doug --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hypertable Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hypertable-dev?hl=en -~----------~----~----~----~------~----~------~--~---
