Wouldn't it be easier if you extend PigStorage by overriding
getLoadCaster() and let the user use that storage when they need to
interact the legacy data?
On Fri, Aug 16, 2013 at 1:40 PM, Sajid Raza <[EMAIL PROTECTED]> wrote:
> I have a legacy dataset that has its own unique representation null '\N'.
> I'd like to use the existing PigStorage loader functionality, but slightly
> adjust how it reads data. I would like to create a new LoadStoreCaster that
> would handle my special null value representation. I'd like to add another
> arg to PigStorage that would allow the end user to specify the name of the
> LoadStoreCaster class used to perform type conversions, with
> Utf8StorageConverter being the default value if nothing is specified.
> Would such a change make sense?