[
https://issues.apache.org/jira/browse/AVRO-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802910#action_12802910
]
Scott Carey commented on AVRO-135:
----------------------------------
bq. I'm hesitant to make that API public. It's fine for stream-based
compression, but I suspect that more awesome compression will come along that
will make that API not be reasonable. I'd rather cross the API bridge when
someone requests it, but I could be convinced.
I agree with the caution here for now. It would not surprise me if we came to
prefer a different API than Streams later. Streams are convenient but
constraining. I think the first step is to have a basic, common form of
compression that all languages should have access to. We can worry about the
API flexibility and customization points after we have more codec examples to
draw from in formulating the common requirements.
> add compression to data files
> -----------------------------
>
> Key: AVRO-135
> URL: https://issues.apache.org/jira/browse/AVRO-135
> Project: Avro
> Issue Type: New Feature
> Components: java, spec
> Reporter: Doug Cutting
> Assignee: Philip Zeyliger
> Priority: Blocker
> Fix For: 1.3.0
>
> Attachments: AVRO-135.patch.txt, AVRO-135.patch.txt,
> AVRO-135.patch.txt, AVRO-135.patch.txt
>
>
> We should add support for at least one compression codec to data files.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.