I'm interested in knowing how people think SolrDocument is going to feature
in the 1.3 release, and wanted to make a few comments.
imho, SolrDocument's role is best kept as a kind of value object used only
for communications with remote clients. I don't think it should appear much
in the underlying codebase, where org.apache.lucene.Document is (i) already
used heavily, and (ii) does everything you need it to, including storing
arbitrary objects and permitting multivalued fields, albeit by different
means. SolrDocument can appear just at the edges, with utility methods for
converting to and from Document and other stuff needed to parse or generate
for remote clients.
Maybe I'm just being paranoid and this was always the intention - but I just
felt there was a danger the codebase could end up duplicating a lot of
Document-like processing in SolrDocument-speak, and thereby make it more
difficult to integrate with/develop for Solr at the Java level.
Jon
