[
https://issues.apache.org/jira/browse/SAMZA-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14062602#comment-14062602
]
Chris Riccomini commented on SAMZA-337:
---------------------------------------
Also, there are several strategies for compression here. One would be to just
shrink the text size. [~jghoman] used to have a little tweak that didn't use
JSON, but instead used some custom simple encoding function to shrink the size.
Another alternative would be compression and mime64, or maybe a combination of
multiple strategies.
Given that I think our goal here is a temporary fix, I'd vote for what ever is
fastest and gets the job done.
> Compress Samza configuration passed to Yarn
> -------------------------------------------
>
> Key: SAMZA-337
> URL: https://issues.apache.org/jira/browse/SAMZA-337
> Project: Samza
> Issue Type: Bug
> Reporter: Naveen
> Assignee: Chinmay Soman
> Priority: Critical
>
> As a stop gap fix for SAMZA-333, we can compress the Samza specific
> configuration using gzip (or something similar) and extract it when the job
> needs them, this will reduce the size of the export variable and temporarily
> alleviate the situation.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
