hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Gates (JIRA)" <>
Subject [jira] [Commented] (HIVE-12443) Hive Streaming should expose encoding and serdes for testing
Date Wed, 18 Nov 2015 00:53:11 GMT


Alan Gates commented on HIVE-12443:

Sorry, I wasn't clear.  I don't want to intercept encode, I want to encode without writing.
 In both RecordWriter's today, the write method contains:
      Object encodedRow = encode(record);
      int bucket = getBucket(encodedRow);
      updaters.get(bucket).insert(transactionId, encodedRow);
Both encoding the record and writing of the record are done in this one method.  I want to
be able to encode the record without writing.  Thus I want to take encode, which is private
in both, elevate it to AbstractRecordWriter and make it public so I can call it from capybara
without writing data into an updater.  This will allow capybara to split the stream coming
into HiveEndPoint, sending one to Hive normal, and using the other to load data into a benchmark.

> Hive Streaming should expose encoding and serdes for testing
> ------------------------------------------------------------
>                 Key: HIVE-12443
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: Testing Infrastructure, Transactions
>    Affects Versions: 2.0.0
>            Reporter: Alan Gates
>            Assignee: Alan Gates
>         Attachments: HIVE-12443.patch
> Currently how records are passed into the hive streaming RecordWriter are converted from
the inbound format to Hive format is opaque.  The encoding and writing are done in a single
call to RecordWriter.write().  This is problematic for test tools that want to intercept the
record stream and write it to a benchmark in addition to Hive.
> All existing RecordWriters have an encode and getSerDe methods.  I propose to expose
these by making them public in AbstractRecordWriter, and making AbstractRecordWriter a public
class (it is currently package private).  This keeps the RecordWriter interface clean (stream
writers will not need to directly call these methods) and avoids any backwards incompatible
changes.  Having AbstractRecordWriter public is also desirable for anyone who wants to write
their own RecordWriter.

This message was sent by Atlassian JIRA

View raw message