[
https://issues.apache.org/jira/browse/BEAM-14452?focusedWorklogId=768620&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-768620
]
ASF GitHub Bot logged work on BEAM-14452:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 10/May/22 17:57
Start Date: 10/May/22 17:57
Worklog Time Spent: 10m
Work Description: chamikaramj commented on PR #17599:
URL: https://github.com/apache/beam/pull/17599#issuecomment-1122701323
Still unclear to me how this work. Do 4mc encoded text files written by
TextIO somehow end up being same as 4mc files ? If so, that sounds like by
accident for me and probably we should develop a 4mc source/sink instead.
Issue Time Tracking
-------------------
Worklog Id: (was: 768620)
Time Spent: 20m (was: 10m)
> Support Hadoop 4mc file format
> ------------------------------
>
> Key: BEAM-14452
> URL: https://issues.apache.org/jira/browse/BEAM-14452
> Project: Beam
> Issue Type: New Feature
> Components: sdk-java-core
> Reporter: Akhilesh Singh
> Priority: P2
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The 4MC (4 More Compression) is a library for hadoop providing a new
> splittable compressed file format (4mc) which lets you leverage the power of
> LZ4 and ZSTD algorithms.
> It differs from other compressed file formats in a way that the output files
> can be read using HIVE partitioning - thus queries can be fast and reads from
> client applications can be very pointed to small compressed files stored on
> GCS.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
