You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Navina Ramesh (JIRA)" <ji...@apache.org> on 2016/12/23 20:30:58 UTC

[jira] [Resolved] (SAMZA-1066) Update JavaStorageConfig after LISAMZA-1060

     [ https://issues.apache.org/jira/browse/SAMZA-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Navina Ramesh resolved SAMZA-1066.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 0.12.0

Issue resolved by pull request 36
[https://github.com/apache/samza/pull/36]

> Update JavaStorageConfig after LISAMZA-1060
> -------------------------------------------
>
>                 Key: SAMZA-1066
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1066
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Navina Ramesh
>            Assignee: Boris Shkolnik
>             Fix For: 0.12.0
>
>
> Changes made for LISAMZA-1060 affects any code path using JavaStorageConfig.java, instead of StorageConfig.scala. 
> Please fix getChangelogStream in JavaStorageConfig and make sure that there are no other inconsistencies between StorageConfig and JavaStorageConfig.
> Thanks!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)