lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan.S (JIRA)" <>
Subject [jira] Commented: (LUCENE-1439) Inconsistent API
Date Fri, 14 Nov 2008 09:00:50 GMT


Ivan.S commented on LUCENE-1439:

Can anyone open an umbrella bug for this?
I think we should first collect all inconsistencies, then someone (including me) start to
make patches.

BTW one more think I've noticed: some methods even start with uppercase.
Common, there are books written about Lucene, such things are just painful ;)
It needs a clear API.

I'm now using Lucene in a project, it helps, I like it. So I would like to contribute (my
time and) patches after
we've sorted out, what the inconsistencies are, sort them by priority, and collect their locations.

Umbrella bug or not?

> Inconsistent API 
> -----------------
>                 Key: LUCENE-1439
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>    Affects Versions: 3.0
>         Environment: any
>            Reporter: Ivan.S
>            Priority: Minor
> The API of Lucene is totally inconsistent:
> 1)
> There are a lot of containers which don't implement an interface which indicates this
> (for pre-java-1.5 Lucene it could be Collection, for post-ajva-1.5 Lucene it could be
more general Iterable)
> Example:
>  IndexSearcher: "int maxDoc()" and "doc(int i)"
> 2)
> There are a lot of classes having non-final public accessible fields.
> 3)
> Some methods which return values are named something() others are named getSomething()
> Best one is: Fieldable:
> without get: String stringValue(), Reader readerValue(), byte[] binaryValue(), ...
> with get: byte[] getBinaryValue(), int getBinaryLength(), ...

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

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

View raw message