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 Tue, 26 Apr 2011 20:40:03 GMT


Greg Stein commented on SOLR-2272:

(stupid thing ended that comment early)

First: you should not be allowed to veto a feature addition. There is no *problem* with that.
If you don't like the location, then apply further patches t move it. But you don't stop it
a prior I.

Second: you never, NEVER revert somebody else's commit. You only do that if they drop off
the face of the earth. A veto on a commit is the beginning of a discussion, and a bkocker
for *release*. You have until then to reach consensus. The committee may realize his commit
was bad for the side, and revert it himself. Or the group will find a solution, and the right
(additional) patches will be applied. But you NEVER take matters into your own hands, unilaterally.
If somebody repeated that action, I would ask the PMC to remove their commit rights, and the
PMC damned well better recognize the anto-social and anti-project view of that committee and
remove the rights. As a Director, I would absolutely support such action.

> 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