In the light of of HSEARCH-436, it seems that just returning a list of field names is not enough. To be useful in the context of the metadata API we need the data for a whole FieldDescriptor (this includes Lucene field options like index, store, ...). An alternative could be to have:

public interface FieldReportingBridge {
	Set<FieldDescriptor> getGeneratedFields(FieldDescriptor baseDescriptor);
}

Built-in bridges and many custom bridges would just have to return the passed baseDescriptor to a set and return it. For bridges which actually generate new fields we can provide a FieldDescriptorFactory which helps creating new descriptors. The factory could be a static helper class or we could pass it as additional parameter to getGeneratedFields().

I am also wondering how useful this reporting still is? Obviously it would be nice from a metadata point of view, but do we still have any internal use for this information. Which ones?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira