Storm 0.7.0 changes #2

Merged
merged 8 commits into from Apr 3, 2012

2 participants

@markhamstra

Minimal changes to make ScalaStorm work with Storm 0.7

Causes an issue with slf4j -- one that can be dealt with fairly easily, but that isn't yet a part of a Storm SNAPSHOT or release:

markhamstra#2
nathanmarz/storm#167

@velvia
Owner

Thanks Mark. I've been busy, but will merge this today or tomorrow. I'll also have a look at hte slf4j issue.

@markhamstra

The slf4j issue is completely resolved with the change to Storm's project.clj that I requested Nathan to pull, but it didn't go into 0.7.1, so it'll be at least a while before it goes into any Storm release. I didn't really look at what it would take to get the ScalaStorm build to back off to slf4j 1.5.8, but that would be the other way to go.

@velvia velvia merged commit c70ab8d into velvia:master Apr 3, 2012
@velvia
Owner

Mark, I see a warning about slf4j, but was able to actually run the topologies (ok I only ran one) in local mode. Just curious if that is what you are seeing, what operational problems you see (submission to cluster?)

For now I'll see about backing off to 1.5.8, if that's easily doable.

@markhamstra

Yes, the topologies seem to run fine in local mode even with the slf4j mismatch error messages. I can't recall whether this worked with an actual storm cluster or not. My cluster is down at the moment, but I'll try to get it back running on 0.7.1 tonight to check on this.

@velvia
Owner
@markhamstra

The change from IRichSpout to BaseRichSpout already allows 0.7.1 to build and run, so I don't see it being a problem. Of course, neither the prior changes nor a change to 0.7.1 takes any advantage of the new functionality that is available, so there is work to be done to make use of TransactionalSpouts and other stuff, but I don't think moving to 0.7.1 breaks anything that is already working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment