lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Stein (JIRA)" <>
Subject [jira] [Commented] (SOLR-2272) Join
Date Wed, 27 Apr 2011 03:01:05 GMT


Greg Stein commented on SOLR-2272:

The only technical reason to revert somebody else's commit is if it break's the build, and
there is no obvious fix to make it build again (ie. the revert re-enables the project to move
forward). There is absolutely NO possible technical reason to perform a revert of somebody's
commit which merely adds a feature. If you think there is, then I have serious concerns about
your idea of how things should operate here at the Foundation. (Robert may object to a change...
totally fine, especially if there are technical concerns, and he may work to see it backed
out or fixed or altered... but he should never unilaterally revert it himself just because
he disagrees or vetoes; the original committer should say "I see your veto, and I don't see
us reaching any compromise, so I'll back it out now")

> Join
> ----
>                 Key: SOLR-2272
>                 URL:
>             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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message