Ya know, that is a good question. In theory, as long as the object is serializable, I wouldn't see a problem. The issue I have is that the underlying holder for the key/value pairs is an instance of a java.util.Properties class. Now, since Properties does subclass Hashtable, it should be able to hold any object. But, the contract with java.util.Property states that all keys and values are strings, though the interface describes something else. So, it's an odd use of the Properties class because it's (Configuration) calling Properties.put() (which is inherited from Hashtable). This is just another bad example of where sub-classing is not always a good thing. I don't understand why sun didn't encapsulate Hashtable within Properties. It also looks like Configuration.getObject() is just another direct call to Properties.get() which is just the hashtable again....
Anyway, it should work. Anyone else? On 5/30/07, Ilya Vishnevsky <[EMAIL PROTECTED]> wrote:
There is method Configuration.setObject(String name, Object value). I tried values of different classes and found that only Strings are passed normally. Other objects turn out to be null when Mapper or Reducer tries to get them using getConf().getObject(String name). Is there possibility to pass a Set for example?
-- "Conscious decisions by conscious minds are what make reality real"
