[
https://issues.apache.org/jira/browse/SOLR-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025430#comment-13025430
]
Greg Stein commented on SOLR-2272:
----------------------------------
Personally, without my Director's hat on, I would recommend the project
consider moving to Commit-Then-Review. Right now, you spend all this effort in
posting patches to JIRA, discussing it ad nauseum, and the project just sits
there. If... instead... you trust the committers to move the project forward,
then let them commit. WHEN a problem comes up then, you discuss it. RTC
implicitly says "we don't trust you", and I don't think it is a good model for
project development. I've seen lots of people say "but the code is really
tricky, so we need to review changes to ensure stability", but I think that is
just a sham for people wanting *control*. You can always review what has been
committed and apply further patches to fix stability -- it doesn't have to come
before the original commit with an updated patch. Release branches are
typically in RTC, and the stability over an open trunk can be regained before
release time. (of course, you would also hope test and regression suites will
everything stable during the open trunk)
> Join
> ----
>
> Key: SOLR-2272
> URL: https://issues.apache.org/jira/browse/SOLR-2272
> Project: Solr
> Issue Type: New Feature
> Components: search
> Reporter: Yonik Seeley
> Fix For: 4.0
>
> Attachments: SOLR-2272.patch, SOLR-2272.patch, SOLR-2272.patch
>
>
> Limited join functionality for Solr, mapping one set of IDs matching a query
> to another set of IDs, based on the indexed tokens of the fields.
> Example:
> fq={!join from=parent_ptr to:parent_id}child_doc:query
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
