[Xapian-tickets] [Xapian] #439: Merge NumericRange code from matchspy branch to trunk (was: Merge NumericRange code from matchspy branch to trun)

[Xapian]

#439: Merge NumericRange code from matchspy branch to trunk
-------------------------+--------------------------------------------------
 Reporter:  richard      |       Owner:  richard  
     Type:  enhancement  |      Status:  new      
 Priority:  normal       |   Milestone:  1.2.x    
Component:  Library API  |     Version:  SVN trunk
 Severity:  normal       |    Keywords:           
Blockedby:               |    Platform:  All      
 Blocking:               |  
-------------------------+--------------------------------------------------

Old description:

> Issues to be addressed before doing this:
>
>  * Is the standard scheme useful?
>  * Should we be returning the ends of the buckets (so adjacent buckets
> meet up), or the maximum and minimum values in the buckets.  Or is
> returning both the most useful approach.
>  * What's the best API for implementing different bucketing schemes.  The
> current API is to make a new subclass of NumericRanges to implement a new
> bucketing scheme, and all the work is done in the constructor: this seems
> poor.  Really, we should have some kind of factory methods to create the
> ranges.
>  * We need support for logarithmic ranges, since they're very common.
>  * We need to document properly what the current scheme does.

New description:

 Issues to be addressed before doing this:

  * Is the standard scheme useful?
  * Should we be returning the ends of the buckets (so adjacent buckets
 meet up), or the maximum and minimum values in the buckets.  Or is
 returning both the most useful approach.
  * What's the best API for implementing different bucketing schemes.  The
 current API is to make a new subclass of !NumericRanges to implement a new
 bucketing scheme, and all the work is done in the constructor: this seems
 poor.  Really, we should have some kind of factory methods to create the
 ranges.
  * We need support for logarithmic ranges, since they're very common.
  * We need to document properly what the current scheme does.

--

Comment(by olly):

 Hmm, I thought you'd concluded that the bucketing stuff didn't really do
 what users actually wanted?

 Perhaps that's the first point, and our discussion of that happened after
 this ticket.

 If so, let's either close this ticket, or morph it into a place to track
 implementing something which produces such buckets but in a way which is
 actually useful!

-- 
Ticket URL: <http://trac.xapian.org/ticket/439#comment:1>
Xapian <http://xapian.org/>
Xapian