[
https://issues.apache.org/jira/browse/AVRO-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15278750#comment-15278750
]
ASF GitHub Bot commented on AVRO-1843:
--------------------------------------
GitHub user rehevkor5 opened a pull request:
https://github.com/apache/avro/pull/91
Clarify importance of writer's schema in documentation
See also: https://issues.apache.org/jira/browse/AVRO-1843
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rehevkor5/avro avro-1843
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/avro/pull/91.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #91
----
commit 1024216a68cdb7ec54ad3d126953755314966588
Author: Shannon Carey <sca...@expedia.com>
Date: 2016-05-10T19:47:13Z
Clarify importance of writer's schema in documentation
----
> Clarify importance of writer's schema in documentation
> ------------------------------------------------------
>
> Key: AVRO-1843
> URL: https://issues.apache.org/jira/browse/AVRO-1843
> Project: Avro
> Issue Type: Improvement
> Components: doc
> Reporter: Shannon Carey
> Priority: Minor
>
> I'll be submitting a PR with some improvements to the Java Getting Started
> page as well as the Specification which make it clearer that Avro must read
> all data with the writer's schema before converting it into the reader's
> schema and why, and explaining that's why the schema should be available next
> to serialized data. Currently, it's arguably too easy to misinterpret Avro as
> only requiring a single, reader's schema in order to read data while still
> following the resolution rules which make Avro seem similar to JSON
> (resolution by field name). For example, the Java API examples only appear to
> involve one schema, hiding the fact that it reads in the writer's schema
> implicitly. Also, the ability to serialize to JSON (where field names and
> some type info is present) makes this misconception easy to believe.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
