On Fri, Sep 5, 2008 at 8:26 PM, Yonik Seeley <[EMAIL PROTECTED]> wrote:
> > We all scratch our own itch in open-source... good, practical > scalability to high levels is an interest of mine :-) > Many will choose their solution based on it's ability to scale to > their most optimistic projections... so they may only use 10 or 20 > servers, but if it can't scale to 100 then they might start with > something that easily can. And I think this work would greatly > benefit those with smaller clusters also. > Yonik, I agree with you that reaching that scale is what we should be aiming for. What I'm really trying to say is that giving a real time search solution *now* to our *current* users is the path that may give the most value to Solr. We can start with that limited scope and proceed to manage thousands of nodes in subsequent iterations. I'm hopeful that this modest scope can be achieved with tweaks to the current system by Solr 1.5 in less than a year (sorry Hoss :-) ). Working towards a completely new architecture for the benefit of users that we don't even have right now may distract us from our current users' needs. I propose that we use the wiki to jot down all the goals that we want to achieve. Let us scope them such that each goal is achievable in a quarter of a year, re-architecting pieces as and when necessary to achieve each bit. Backwards compatibility will be useful but not compulsory. Trivial loss of compatibility may be OK -- if it becomes impossible to be backwards compatible in a major way, we can bump the release to a major version. I'm sure users won't mind doing a little work if we can give them compelling features. Thoughts? -- Regards, Shalin Shekhar Mangar.
