[
https://issues.apache.org/jira/browse/SAMZA-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14062565#comment-14062565
]
Chris Riccomini commented on SAMZA-337:
---------------------------------------
My preference would be only 0.8. In an ideal world, 0.7.1 would have no commits
and never get released, so as close to that as possible is how I'd like to keep
it. This bug isn't fatal, except in extreme circumstances, so I'd say just 0.8.
Currently, we're still running on 0.7 here at LI. I'd prefer to have us move
back on to 0.8 as quickly as possible, so this will be good motivation. I think
[~jghoman] was espousing the same. It's going to be a bit more work for us
internally, but will benefit everyone since we'll discover more 0.8 bugs that
way.
> 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)
