lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shai Erera (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (LUCENE-3079) Facetiing module
Date Mon, 27 Jun 2011 13:25:48 GMT

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

Shai Erera edited comment on LUCENE-3079 at 6/27/11 1:24 PM:
-------------------------------------------------------------

We can put it in a branch for trunk, in case we plan to refactor the code right away (at first
I just thought to get it to compile against trunk). I thought that at first people would like
to get hands on experience with it, before we discuss changes and refactoring. I mean, this
code can really be released with Lucene's next 3x release. And since everything is @lucene.experimental,
and is in its own separate contrib/module, I don't think a branch will ease off the review
or refactoring process?

I guess what I'm aiming for is for our users to get this feature soon. And I'm afraid that
putting it in a branch will only delay it.

      was (Author: shaie):
    We can put it in a branch for trunk, in case we plan to refactor the code right away (at
first I just thought to get it to compile against trunk). I thought that at first people would
like to get hands on experience with it, before we discuss changes and refactoring. I mean,
this code can really be released with Lucene's next 3x release. And since everything is @lucene.experimental,
and is in its own separate contrib/module, I don't think a branch will ease off the review
or refactoring process?
  
> Facetiing module
> ----------------
>
>                 Key: LUCENE-3079
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3079
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Michael McCandless
>         Attachments: LUCENE-3079.patch, LUCENE-3079.patch
>
>
> Faceting is a hugely important feature, available in Solr today but
> not [easily] usable by Lucene-only apps.
> We should fix this, by creating a shared faceting module.
> Ideally, we factor out Solr's faceting impl, and maybe poach/merge
> from other impls (eg Bobo browse).
> Hoss describes some important challenges we'll face in doing this
> (http://markmail.org/message/5w35c2fr4zkiwsz6), copied here:
> {noformat}
> To look at "faceting" as a concrete example, there are big the reasons 
> faceting works so well in Solr: Solr has total control over the 
> index, knows exactly when the index has changed to rebuild caches, has a 
> strict schema so it can make sense of field types and 
> pick faceting algos accordingly, has multi-phase distributed search 
> approach to get exact counts efficiently across multiple shards, etc...
> (and there are still a lot of additional enhancements and improvements 
> that can be made to take even more advantage of knowledge solr has because 
> it "owns" the index that we no one has had time to tackle)
> {noformat}
> This is a great list of the things we face in refactoring.  It's also
> important because, if Solr needed to be so deeply intertwined with
> caching, schema, etc., other apps that want to facet will have the
> same "needs" and so we really have to address them in creating the
> shared module.
> I think we should get a basic faceting module started, but should not
> cut Solr over at first.  We should iterate on the module, fold in
> improvements, etc., and then, once we can fully verify that cutting
> over doesn't hurt Solr (ie lose functionality or performance) we can
> later cutover.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message