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

Mark Miller edited comment on SOLR-236 at 12/18/09 4:12 PM:
------------------------------------------------------------

bq. I very much disagree with a policy blocking non-production-ready code from 
being in source control

Just to be clear, there is no such policy that I've seen - each decision just 
comes down to consensus. And as far as I know, our branch policy is pretty much 
"anything goes" - trunk is very different than svn. Anyone (anyone with access 
to svn that is) can play around with a branch for anything if they want.


I agree with your thoughts on a branch - if the argument is, we want it to be 
easier for devs to check out and work on this, or for users to checkout and 
build this without applying patches, why not just make a branch? Merging is 
annoying but not difficult - I've been doing plenty of branch merging lately, 
and while its not glorious work, modern tools make it more of a grind than a 
challenge.

      was (Author: markrmil...@gmail.com):
    bq. I very much disagree with a policy blocking non-production-ready code 
from being in source control

Just to be clear, there is no such policy that I've seen - each decision just 
comes down to consensus. And as far as I know, our branch policy is pretty much 
"anything goes" - trunk is very different than svn. Anyone can play around with 
a branch for anything if they want.


I agree with your thoughts on a branch - if the argument is, we want it to be 
easier for devs to check out and work on this, or for users to checkout and 
build this without applying patches, why not just make a branch? Merging is 
annoying but not difficult - I've been doing plenty of branch merging lately, 
and while its not glorious work, modern tools make it more of a grind than a 
challenge.
  
> Field collapsing
> ----------------
>
>                 Key: SOLR-236
>                 URL: https://issues.apache.org/jira/browse/SOLR-236
>             Project: Solr
>          Issue Type: New Feature
>          Components: search
>    Affects Versions: 1.3
>            Reporter: Emmanuel Keller
>            Assignee: Shalin Shekhar Mangar
>             Fix For: 1.5
>
>         Attachments: collapsing-patch-to-1.3.0-dieter.patch, 
> collapsing-patch-to-1.3.0-ivan.patch, collapsing-patch-to-1.3.0-ivan_2.patch, 
> collapsing-patch-to-1.3.0-ivan_3.patch, field-collapse-3.patch, 
> field-collapse-4-with-solrj.patch, field-collapse-5.patch, 
> field-collapse-5.patch, field-collapse-5.patch, field-collapse-5.patch, 
> field-collapse-5.patch, field-collapse-5.patch, field-collapse-5.patch, 
> field-collapse-5.patch, field-collapse-5.patch, field-collapse-5.patch, 
> field-collapse-5.patch, field-collapse-5.patch, field-collapse-5.patch, 
> field-collapse-5.patch, field-collapse-5.patch, 
> field-collapse-solr-236-2.patch, field-collapse-solr-236.patch, 
> field-collapsing-extended-592129.patch, field_collapsing_1.1.0.patch, 
> field_collapsing_1.3.patch, field_collapsing_dsteigerwald.diff, 
> field_collapsing_dsteigerwald.diff, field_collapsing_dsteigerwald.diff, 
> quasidistributed.additional.patch, SOLR-236-FieldCollapsing.patch, 
> SOLR-236-FieldCollapsing.patch, SOLR-236-FieldCollapsing.patch, 
> SOLR-236.patch, SOLR-236.patch, SOLR-236.patch, solr-236.patch, 
> SOLR-236_collapsing.patch, SOLR-236_collapsing.patch
>
>
> This patch include a new feature called "Field collapsing".
> "Used in order to collapse a group of results with similar value for a given 
> field to a single entry in the result set. Site collapsing is a special case 
> of this, where all results for a given web site is collapsed into one or two 
> entries in the result set, typically with an associated "more documents from 
> this site" link. See also Duplicate detection."
> http://www.fastsearch.com/glossary.aspx?m=48&amid=299
> The implementation add 3 new query parameters (SolrParams):
> "collapse.field" to choose the field used to group results
> "collapse.type" normal (default value) or adjacent
> "collapse.max" to select how many continuous results are allowed before 
> collapsing
> TODO (in progress):
> - More documentation (on source code)
> - Test cases
> Two patches:
> - "field_collapsing.patch" for current development version
> - "field_collapsing_1.1.0.patch" for Solr-1.1.0
> P.S.: Feedback and misspelling correction are welcome ;-)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to