[
https://issues.apache.org/jira/browse/AVRO-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12836003#action_12836003
]
Scott Carey commented on AVRO-414:
----------------------------------
bq. Scott, how critical is this for 1.3? This patch no longer applies cleanly.
I'll be using this in production either way -- 1.3 patched with this or 1.3
official.
If its not in 1.3 this is not critical but there is appeal to running without a
patch. If producing an RC today is important, and this can't make it, I'm ok
with that.
Unlike AVRO-392 which had wide scope and changed semantics, this change is
limited in scope. It just improves the file format code a bit, increases
testing coverage, and adds some extra functionality.
It may not be that quick to review, since it changed the file reader to have an
internal iterator over blocks so that classes in the same package can choose to
iterate either by block, or by record. That required some non-trivial changes.
The new TestDataFileConcat class adds additional coverage to the file format,
and during the process of adding these I discovered a couple corner case bugs
and fixed them (like AVRO-407).
> Binary File concatenate and block-based apppend / compress / uncompress
> -----------------------------------------------------------------------
>
> Key: AVRO-414
> URL: https://issues.apache.org/jira/browse/AVRO-414
> Project: Avro
> Issue Type: New Feature
> Components: java
> Reporter: Scott Carey
> Assignee: Scott Carey
> Fix For: 1.3.0
>
> Attachments: AVRO-414.patch, AVRO-414.patch, AVRO-414_plus_392.patch
>
>
> The block based format of the binary file allows for block-based operations
> that do not decode or encode data.
> Two such use cases are:
> * Change the compression codec or compression level of a file without
> decoding.
> * Concatenate two files with identical schemas together quickly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
