[Xapian-tickets] [Xapian] #195: Chert writable databases should take a parameter indicating flush threshold. (was: Flint writable databases should take a parameter indicating flush threshold.)

[Xapian]

#195: Chert writable databases should take a parameter indicating flush
threshold.
---------------------------+------------------------------------------------
 Reporter:  richard        |        Owner:  olly    
     Type:  defect         |       Status:  assigned
 Priority:  normal         |    Milestone:          
Component:  Backend-Chert  |      Version:  SVN HEAD
 Severity:  normal         |   Resolution:          
 Keywords:                 |    Blockedby:          
 Platform:  All            |     Blocking:          
---------------------------+------------------------------------------------
Changes (by richard):

  * component:  Backend-Flint => Backend-Chert


Old description:

> Possibly, this should be a global parameter (ie, applies to all
> databases), or
> maybe it should be a database specific parameter (ie, set as a parameter
> to the
> "open" method for flint writable databases).
>
> In any case, the current way of setting a flush threshold (ie, setting an
> environment variable) is unsatisfactory, due to being difficult to set in
> some
> circumstances (or on some OSes), and it being easy for users to forget to
> export
> the variable, resulting in bogus bug reports.  A parameter to a Xapian
> function
> would be a cleaner API for this.  However, we indend to improve the
> handling of
> automatic flushes in future, such that the count of added documents won't
> be the
> crucial factor; instead, amount of memory used will be.  We need to
> ensure we
> don't add a parameter to the API which will shortly become meaningless.

New description:

 Possibly, this should be a global parameter (ie, applies to all
 databases), or maybe it should be a database specific parameter (ie, set
 as a parameter to the "open" method for chert writable databases).

 In any case, the current way of setting a flush threshold (ie, setting an
 environment variable) is unsatisfactory, due to being difficult to set in
 some circumstances (or on some OSes), and it being easy for users to
 forget to export the variable, resulting in bogus bug reports.  A
 parameter to a Xapian function would be a cleaner API for this.  However,
 we intend to improve the handling of automatic flushes in future, such
 that the count of added documents won't be the crucial factor; instead,
 amount of memory used will be.  We need to ensure we don't add a parameter
 to the API which will shortly become meaningless.

--

Comment:

 Changed this bug to be about Chert - we want to put new features like this
 into Chert rather than Flint now.

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