lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] Updated: (LUCENE-621) Default lock timeouts should have static setter/getters
Date Fri, 30 Jun 2006 13:00:31 GMT
     [ ]

Michael McCandless updated LUCENE-621:


Small changes to to add default (static) getter/setters for COMMIT_LOCK_TIMEOUT

> Default lock timeouts should have static setter/getters
> -------------------------------------------------------
>          Key: LUCENE-621
>          URL:
>      Project: Lucene - Java
>         Type: Bug

>   Components: Index
>     Versions: 2.0.0
>     Reporter: Michael McCandless
>     Priority: Minor
>  Attachments:
> We recently stopped using Java system properties to derive defaults for things like the
write/commit lock timeout, and switched to getter/setter's across all classes.  See here:
> But, in the case at least of the write lock timeout, because it's marked "public final
static", a consumer of this API can no longer change this value before instantiating the IndexWriter.
 This is because the getter/setter for this is not static, which generally makes sense so
you can change the timeout for each instance of IndexWriter.  But because IndexWriter on construction
uses the timeout value, some uses cases need to change the value before getting an instance
of IndexWriter.
> This was actually a regression, in that Lucene users lost functionality they previously
had, on upgrading.
> I would propose that that we add getter/setter for the default value of this timeout,
which would be static.  I'll attach a patch file.
> See this thread for context that led to this issue:

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message