Hi Yonik, I fully agree with "good for projects in the long term". I just figured it would be best if someone went ahead and built the things and they could be integrated later into other projects, that's why I checked them into Apache as patches. Sounds like a few folks like Shalin and Noble would like to build a SOLR specific realtime search. I think that's a good idea that I may be able to offer some help on. Realtime is relative anyways, for many projects database like updates are probably not necessary, neither is replication, or perhaps even 100% uptime and scalability. I just want the features, and if someone would like to work with me to get them into core Lucene and SOLR projects that would be cool. If not at least the code is out there to get ideas from. These discussions are a good starting point.
Cheers, Jason On Sat, Sep 6, 2008 at 11:21 AM, Yonik Seeley <[EMAIL PROTECTED]> wrote: > There's a good percent of the Solr community that is looking to add > everything you are (from a functional point of view). Some of the > other little things that we haven't considered (like a remote Java > API) sound cool... no reason not to add that also. We're also > planning on adding alternatives to some of the things you don't > currently like about Solr (HTTP, XML config, etc). > > Apache has always emphasized "community over code"... and it's a large > part of what open source is about here. It's not always easier and > faster to work in an open community, making compromises and trying to > reach general consensus, but it tends to be good for projects in the > long term. > > -Yonik > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
