Details
-
New Feature
-
Resolution: Won't Fix
-
Major
-
None
-
None
-
None
-
All
-
-
GreenHopper Ranking:0|i0zl5f:
-
9223372036854775807
-
Small
Description
Following API changes should be made (potentially breaking):
- T Reader.getCurrent() throws NoSuchElementException -> IndexedRecord Reader.getCurrent() throws NoSuchElementException
- void Writer.write(Object object) throws IOException -> void Writer.write(IndexedRecord record) throws IOException
Before we allowed any object for optimization reason in case of specific job design:
tSomeFamilyInput -> tSomeFamilyOutput (both from the same family)
It was found it wasn't used. Also we still may have such optimization if component extends IndexedRecord and put its native object there. Output component may try to cast incoming IndexedRecord to its specific type and retrieve native object
Attachments
Issue Links
- is child of
-
TCOMP-438 TCOMP API cleanup
- Rejected