[ 
https://issues.apache.org/jira/browse/SOLR-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025425#comment-13025425
 ] 

Mark Miller commented on SOLR-2272:
-----------------------------------

Ah - i jumped the gun on you. That is useful advice (call me biased if you'd 
like).

Honestly, there is no way around this issue - of course we must discuss and 
come to some solution regarding Lucene/Solr at this point. This whole thing is 
very distressing to me. I think we all know it just sucks. In the past, I have 
enjoyed working with everyone here. My personal beef in this issue is not with 
that though - I simply am very offended by heavy handed reverts and such. I 
feel the same way about JIRA. Words before action in my book - many words - 
hard as that can be for all of us sometimes. This has been the history of 
Lucene and the thing about the project that I admired most - heavy hands where 
checked at the door. I'm no angel, and I'm not perfect about this myself. But I 
still try and police it because I think its important.

> 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]

Reply via email to