Jason Rutherglen wrote:
I think it's best to implement Externalizable as long as someone is willing to maintain it. I commit to maintaining the Externalizable code.
We need to agree to maintain things as a community, not as individuals. We can't rely on any particular individual being around in the future.
This will insure forward compatability between serialized versions, make the serialized objects smaller, and make serialization faster.
If we want to promise compatibility we need to scope it and test it. We cannot in good faith promise that Query will be serially compatible forever, nor should we make any promises that we don't test. So if you choose to continue promoting this route, please specify the scope of compatibility and your plans to add tests for it.
Apparently it matters enough for Hadoop to implement Writeable in all over the wire classes.
I'm not sure what you're saying here. As I've said before, Hadoop is moving away from Writable because it is too fragile as classes change. As a part of the preparations for Hadoop 1.0 we are agreeing on serialization back-compatibility requirements and what technology we will use to support these. Hadoop is at its core a distributed system, while Lucene is not. Even then, Hadoop will continue to require that one update all nodes in a cluster in a coordinated manner, so only end-user protocols need be cross-version compatible, not internal protocols. I do not yet see a strong analogy here.
Doug --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
