You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Thiruvalluvan M. G. (JIRA)" <ji...@apache.org> on 2018/12/30 05:40:00 UTC

[jira] [Updated] (AVRO-1911) for avro HTTP content type instead of avro/binary, application/octet-stream;fmt=avro might be more appropriate?

     [ https://issues.apache.org/jira/browse/AVRO-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thiruvalluvan M. G. updated AVRO-1911:
--------------------------------------
    Component/s: java

> for avro HTTP content type instead of avro/binary, application/octet-stream;fmt=avro might be more appropriate?
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: AVRO-1911
>                 URL: https://issues.apache.org/jira/browse/AVRO-1911
>             Project: Apache Avro
>          Issue Type: Improvement
>          Components: java
>            Reporter: Zoltan Farkas
>            Priority: Major
>
> the content type is defined in:
> {code}
> /** An HTTP-based {@link Transceiver} implementation. */
> public class HttpTransceiver extends Transceiver {
>   static final String CONTENT_TYPE = "avro/binary";
> {code}
> I suggest using for avro binary:
> application/octet-stream;fmt=avro
> and for avro json:
> application/json;fmt=avro
> this would take advantage of standard mime types...



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)