hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <>
Subject [jira] [Work logged] (HIVE-21218) KafkaSerDe doesn't support topics created via Confluent Avro serializer
Date Sat, 07 Mar 2020 21:17:00 GMT


ASF GitHub Bot logged work on HIVE-21218:

                Author: ASF GitHub Bot
            Created on: 07/Mar/20 21:16
            Start Date: 07/Mar/20 21:16
    Worklog Time Spent: 10m 
      Work Description: davidov541 commented on issue #933: HIVE-21218: Adding support for
Confluent Kafka Avro message format
   Full system test passed identically to the one above, and I was able to use the name SimpleRecord
without any issues. Only thing we are left waiting on is any final comments, and for the build
system to finish its checks.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

Issue Time Tracking

    Worklog Id:     (was: 399752)
    Time Spent: 14h 40m  (was: 14.5h)

> KafkaSerDe doesn't support topics created via Confluent Avro serializer
> -----------------------------------------------------------------------
>                 Key: HIVE-21218
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: kafka integration, Serializers/Deserializers
>    Affects Versions: 3.1.1
>            Reporter: Milan Baran
>            Assignee: David McGinnis
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: HIVE-21218.2.patch, HIVE-21218.3.patch, HIVE-21218.4.patch, HIVE-21218.5.patch,
HIVE-21218.6.patch, HIVE-21218.7.patch, HIVE-21218.8.patch, HIVE-21218.9.patch, HIVE-21218.patch
>          Time Spent: 14h 40m
>  Remaining Estimate: 0h
> According to [Google groups|!topic/confluent-platform/JYhlXN0u9_A] the
Confluent avro serialzier uses propertiary format for kafka value - <magic_byte 0x00><4
bytes of schema ID><regular avro bytes for object that conforms to schema>. 
> This format does not cause any problem for Confluent kafka deserializer which respect
the format however for hive kafka handler its bit a problem to correctly deserialize kafka
value, because Hive uses custom deserializer from bytes to objects and ignores kafka consumer
ser/deser classes provided via table property.
> It would be nice to support Confluent format with magic byte.
> Also it would be great to support Schema registry as well.

This message was sent by Atlassian Jira

View raw message