[
https://issues.apache.org/jira/browse/HIVE-19534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16475085#comment-16475085
]
Prasanth Jayachandran commented on HIVE-19534:
----------------------------------------------
This is just expanding scope of variables and methods so that custom record
writers can be implemented. This shouldn't affect any tests.
> Allow implementations to access member variables of AbstractRecordWriter
> ------------------------------------------------------------------------
>
> Key: HIVE-19534
> URL: https://issues.apache.org/jira/browse/HIVE-19534
> Project: Hive
> Issue Type: Improvement
> Components: Streaming
> Reporter: Matt Burgess
> Assignee: Prasanth Jayachandran
> Priority: Major
> Attachments: HIVE-19534.1.patch
>
>
> The AbstractRecordWriter class in the Hive 3 Streaming API (package
> org.apache.hive.streaming) provides common functionality for processing
> incoming records (each as a byte[]) where subclasses often need only to
> implement the encode() and createSerde() methods and let AbstractRecordWriter
> handle the rest.
> However for some custom RecordWriters, the records may not be available as a
> byte array, and thus the custom RecordWriter may need to handle the writes
> and the "paperwork" such as connection stats updates (number of records
> written, e.g.), basically the same code that is in the write(long, byte[])
> method. To do that, the subclass will need access to the member variables of
> AbstractRecordWriter, which are currently private. The same likely holds for
> the private methods.
> This Jira proposes to make the member variables and methods of
> AbstractRecordWriter protected (or package-protected) as prudent.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
