You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -46,13 +46,15 @@ NOTE: The change from 0.7.0 in which OutputCollector no longer assumes immutable
46
46
* Throw helpful error message if StormSubmitter used without using storm client script
47
47
* Add Values class as a default serialization
48
48
* Bug fix: give absolute piddir to subprocesses (so that relative paths can be used for storm local dir)
49
+
* Bug fix: Fixed critical bug in transactional topologies where a batch would be considered successful even if the batch didn't finish
49
50
* Bug fix: Fixed critical bug in opaque transactional topologies that would lead to duplicate messages when using pipelining
50
51
* Bug fix: Workers will now die properly if a ShellBolt subprocess dies (thanks tomo)
51
52
* Bug fix: Hide the BasicOutputCollector#getOutputter method, since it shouldn't be a publicly available method
52
53
* Bug fix: Zookeeper in local mode now always gets an unused port. This will eliminate conflicts with other local mode processes or other Zookeeper instances on a local machine. (thanks xumingming)
53
54
* Bug fix: Fixed NPE in CoordinatedBolt it tuples emitted, acked, or failed for a request id that has already timed out. (thanks xumingming)
54
55
* Bug fix: UI no longer errors for topologies with no assigned tasks (thanks xumingming)
55
56
* Bug fix: emitDirect on SpoutOutputCollector now works
57
+
* Bug fix: Fixed NPE when giving null parallelism hint for spout in TransactionalTopologyBuilder (thanks xumingming)
Copy file name to clipboardExpand all lines: README.markdown
+5-1Lines changed: 5 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
Storm is a distributed realtime computation system. Similar to how Hadoop provides a set of general primitives for doing batch processing, Storm provides a set of general primitives for doing realtime computation. Storm is simple, can be used with any programming language, and is a lot of fun to use!
1
+
Storm is a distributed realtime computation system. Similar to how Hadoop provides a set of general primitives for doing batch processing, Storm provides a set of general primitives for doing realtime computation. Storm is simple, can be used with any programming language, [is used by many companies](https://github.com/nathanmarz/storm/wiki/Powered-By), and is a lot of fun to use!
2
2
3
3
The [Rationale page](https://github.com/nathanmarz/storm/wiki/Rationale) on the wiki explains what Storm is and why it was built. The [video](http://www.infoq.com/presentations/Storm) and [slides](http://www.slideshare.net/nathanmarz/storm-distributed-and-faulttolerant-realtime-computation) of Storm's launch presentation are also good introductions to the project.
4
4
@@ -51,3 +51,7 @@ You must not remove this notice, or any other, from this software.
51
51
* Nicolas Yzet ([@nicoo](https://github.com/nicoo))
YourKit is kindly supporting open source projects with its full-featured Java Profiler. YourKit, LLC is the creator of innovative and intelligent tools for profiling Java and .NET applications. Take a look at YourKit's leading software products: [YourKit Java Profiler](http://www.yourkit.com/java/profiler/index.jsp) and [YourKit .NET Profiler](http://www.yourkit.com/.net/profiler/index.jsp).
0 commit comments