[LUCENE-3777] trapping overloaded ctors/setters in Field/NumericField/DocValuesField

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 4.0-ALPHA
• Fix Version/s: 4.0-ALPHA
• Lucene Fields: New
• Assignee: Michael McCandless
• Reporter: Robert Muir
• Created: 14/Feb/12 03:46
• Updated: 28/Aug/22 13:07
• Resolved: 10/May/12 11:46

Description

In trunk, these apis let you easily create a field, but my concern is this:

public NumericField(String name, int value)
public NumericField(String name, long value)
..
public Field(String name, int value, FieldType type)
public Field(String name, long value, FieldType type)
..
public void setValue(int value)
public void setValue(long value)
..
public DocValuesField(String name, int value, DocValues.Type docValueType)
public DocValuesField(String name, long value, DocValues.Type docValueType)

I really don't like overloaded ctors/setters where the compiler can type-promote you,
I think it makes the apis hard to use.

Instead for the setters I think we sohuld have setIntValue, setLongValue, ...
For the ctors, I see two other options:

1. factories like DocValuesField.newIntField()
2. subclasses like IntField

I don't have any patch for this, but I think we should discuss and fix before these apis are released.