: At this point, Solr-215 just looks like a solution to my problem... : My apologies for the clutter & waste of community resources.
Please, please, PLEASE don't feel that way ... a functioning patch and/or a productive discussion is *NEVER* a waste of resources. I think Doug Cutting is the first person that told me the mantra all open source projects should live by "a patch in the bug queue that never gets commited is still a useful patch because it's available to people that want it." ... but commiting a patch (especially a big one) requires taking on a lot of responsibility to stand behind the APIs/functionality it includes and commit to a "best effort" to support them in a backwards compatible way for as long as feasible. On a personal note: Please keep in mind that just because i make suggestions to people on how to achieve multiple indexes / schemas / doctypes that doesn't require your patch doesn't mean i think there's anything wrong with your patch ... i'm just trying to make sure people are aware of what's posisble "out of the box". I think the appraoch you've advoated in teh jira issue description makes a lot of sense, and i kind of wish Solr had been implemented that way in the begining -- it just wasn't anticipated. the real question in my mind is: can we get from here to there cleanly, and is your patch the way to do it? i don't know the answer to that question yet. but please don't be discouraged. -Hoss
