[jira] [Resolved] (STORM-2826) KafkaSpoutConfig.builder doesn't set key/value deserializer properties in storm-kafka-client
[ https://issues.apache.org/jira/browse/STORM-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stig Rohde Døssing resolved STORM-2826. --- Resolution: Fixed Fix Version/s: 1.2.0 > KafkaSpoutConfig.builder doesn't set key/value deserializer properties in > storm-kafka-client > > > Key: STORM-2826 > URL: https://issues.apache.org/jira/browse/STORM-2826 > Project: Apache Storm > Issue Type: Bug > Components: storm-kafka-client >Affects Versions: 1.2.0 >Reporter: Stig Rohde Døssing >Assignee: Stig Rohde Døssing >Priority: Blocker > Labels: pull-request-available > Fix For: 1.2.0 > > Time Spent: 3h > Remaining Estimate: 0h > > STORM-2548 replaced the KafkaSpoutConfig.builder() implementations with ones > that don't set the key/value deserializer fields in KafkaSpoutConfig, but > instead just sets the corresponding property in the kafkaProps map. This is a > breaking change for applications that assume those properties are set after > the builder is created. > Code like the following would break. > {quote} > this.keyDeserializer = config.getKeyDeserializer().getClass(); > this.valueDeserializer = config.getValueDeserializer().getClass(); > {quote} -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (STORM-2859) NormalizedResources is leaking static state in tests, and has some other bugs in special cases where 0 of a resource is available
[ https://issues.apache.org/jira/browse/STORM-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated STORM-2859: -- Labels: pull-request-available (was: ) > NormalizedResources is leaking static state in tests, and has some other bugs > in special cases where 0 of a resource is available > - > > Key: STORM-2859 > URL: https://issues.apache.org/jira/browse/STORM-2859 > Project: Apache Storm > Issue Type: Sub-task > Components: storm-server >Affects Versions: 2.0.0 >Reporter: Stig Rohde Døssing >Assignee: Stig Rohde Døssing > Labels: pull-request-available > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (STORM-2858) Fix worker-launcher build
[ https://issues.apache.org/jira/browse/STORM-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated STORM-2858: -- Labels: pull-request-available (was: ) > Fix worker-launcher build > - > > Key: STORM-2858 > URL: https://issues.apache.org/jira/browse/STORM-2858 > Project: Apache Storm > Issue Type: Sub-task > Components: storm-core >Affects Versions: 2.0.0, 1.2.0 >Reporter: Stig Rohde Døssing >Assignee: Stig Rohde Døssing > Labels: pull-request-available > > I got an error when building with -Pnative because GCC has marked asprintf as > a function where you shouldn't ignore the return value. I'm guessing it's the > same issue that's preventing Travis from building storm-core. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (STORM-2859) NormalizedResources is leaking static state in tests, and has some other bugs in special cases where 0 of a resource is available
Stig Rohde Døssing created STORM-2859: - Summary: NormalizedResources is leaking static state in tests, and has some other bugs in special cases where 0 of a resource is available Key: STORM-2859 URL: https://issues.apache.org/jira/browse/STORM-2859 Project: Apache Storm Issue Type: Sub-task Components: storm-server Affects Versions: 2.0.0 Reporter: Stig Rohde Døssing Assignee: Stig Rohde Døssing -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (STORM-2858) Fix worker-launcher build
Stig Rohde Døssing created STORM-2858: - Summary: Fix worker-launcher build Key: STORM-2858 URL: https://issues.apache.org/jira/browse/STORM-2858 Project: Apache Storm Issue Type: Sub-task Components: storm-core Affects Versions: 2.0.0, 1.2.0 Reporter: Stig Rohde Døssing Assignee: Stig Rohde Døssing I got an error when building with -Pnative because GCC has marked asprintf as a function where you shouldn't ignore the return value. I'm guessing it's the same issue that's preventing Travis from building storm-core. -- This message was sent by Atlassian JIRA (v6.4.14#64029)