[
https://issues.apache.org/jira/browse/LUCENE-3694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13186968#comment-13186968
]
Simon Willnauer edited comment on LUCENE-3694 at 1/16/12 3:28 PM:
------------------------------------------------------------------
I am talking about Field.java
{code}
public void setValue(BytesRef value) {
//....
}
public void setValue(int value) {
//....
}
public void setValue(long value) {
//....
}
public void setValue(float value) {
//....
}
public void setValue(double value) {
//....
}
{code}
was (Author: simonw):
I am talking about Field.java
{code}
public void setValue(BytesRef value) {
//....
}
public void setValue(int value) {
//....
}
public void setValue(long value) {
//....
}
public void setValue(float value) {
//....
}
public void setValue(double value) {
//....
}
> DocValuesField should not overload setInt/setFloat etc
> ------------------------------------------------------
>
> Key: LUCENE-3694
> URL: https://issues.apache.org/jira/browse/LUCENE-3694
> Project: Lucene - Java
> Issue Type: Bug
> Reporter: Robert Muir
> Assignee: Michael McCandless
> Fix For: 4.0
>
>
> See my description on LUCENE-3687. In general we should avoid this for
> primitive types and give them each unique names.
> So I think instead of setInt(byte), setInt(short), setInt(int), setInt(long),
> setFloat(float) and setFloat(double),
> we should have setByte(byte), setShort(short), setInt(int), setLong(long),
> setFloat(float) and setDouble(double).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
