You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@storm.apache.org by kn...@apache.org on 2015/12/11 05:51:42 UTC
[1/3] storm git commit: change kryo links from google code to github
Repository: storm
Updated Branches:
refs/heads/asf-site 01f3ec56a -> 27285ae7c
change kryo links from google code to github
Project: http://git-wip-us.apache.org/repos/asf/storm/repo
Commit: http://git-wip-us.apache.org/repos/asf/storm/commit/2b2de446
Tree: http://git-wip-us.apache.org/repos/asf/storm/tree/2b2de446
Diff: http://git-wip-us.apache.org/repos/asf/storm/diff/2b2de446
Branch: refs/heads/asf-site
Commit: 2b2de4460bcc6ac67afa1f31824304dddfb626e3
Parents: de722cb
Author: Xin Wang <be...@163.com>
Authored: Tue Dec 1 14:45:14 2015 +0800
Committer: Xin Wang <be...@163.com>
Committed: Tue Dec 1 14:45:14 2015 +0800
----------------------------------------------------------------------
documentation/Serialization.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/storm/blob/2b2de446/documentation/Serialization.md
----------------------------------------------------------------------
diff --git a/documentation/Serialization.md b/documentation/Serialization.md
index fb86161..2d3488e 100644
--- a/documentation/Serialization.md
+++ b/documentation/Serialization.md
@@ -7,7 +7,7 @@ This page is about how the serialization system in Storm works for versions 0.6.
Tuples can be comprised of objects of any types. Since Storm is a distributed system, it needs to know how to serialize and deserialize objects when they're passed between tasks.
-Storm uses [Kryo](http://code.google.com/p/kryo/) for serialization. Kryo is a flexible and fast serialization library that produces small serializations.
+Storm uses [Kryo](https://github.com/EsotericSoftware/kryo) for serialization. Kryo is a flexible and fast serialization library that produces small serializations.
By default, Storm can serialize primitive types, strings, byte arrays, ArrayList, HashMap, HashSet, and the Clojure collection types. If you want to use another type in your tuples, you'll need to register a custom serializer.
@@ -23,12 +23,12 @@ Finally, another reason for using dynamic typing is so Storm can be used in a st
### Custom serialization
-As mentioned, Storm uses Kryo for serialization. To implement custom serializers, you need to register new serializers with Kryo. It's highly recommended that you read over [Kryo's home page](http://code.google.com/p/kryo/) to understand how it handles custom serialization.
+As mentioned, Storm uses Kryo for serialization. To implement custom serializers, you need to register new serializers with Kryo. It's highly recommended that you read over [Kryo's home page](https://github.com/EsotericSoftware/kryo) to understand how it handles custom serialization.
Adding custom serializers is done through the "topology.kryo.register" property in your topology config. It takes a list of registrations, where each registration can take one of two forms:
1. The name of a class to register. In this case, Storm will use Kryo's `FieldsSerializer` to serialize the class. This may or may not be optimal for the class -- see the Kryo docs for more details.
-2. A map from the name of a class to register to an implementation of [com.esotericsoftware.kryo.Serializer](http://code.google.com/p/kryo/source/browse/trunk/src/com/esotericsoftware/kryo/Serializer.java).
+2. A map from the name of a class to register to an implementation of [com.esotericsoftware.kryo.Serializer](https://github.com/EsotericSoftware/kryo/blob/master/src/com/esotericsoftware/kryo/Serializer.java).
Let's look at an example.
@@ -59,4 +59,4 @@ Storm 0.7.0 lets you set component-specific configurations (read more about this
When a topology is submitted, a single set of serializations is chosen to be used by all components in the topology for sending messages. This is done by merging the component-specific serializer registrations with the regular set of serialization registrations. If two components define serializers for the same class, one of the serializers is chosen arbitrarily.
-To force a serializer for a particular class if there's a conflict between two component-specific registrations, just define the serializer you want to use in the topology-specific configuration. The topology-specific configuration has precedence over component-specific configurations for serialization registrations.
\ No newline at end of file
+To force a serializer for a particular class if there's a conflict between two component-specific registrations, just define the serializer you want to use in the topology-specific configuration. The topology-specific configuration has precedence over component-specific configurations for serialization registrations.
[2/3] storm git commit: change kryo link from google code to github
Posted by kn...@apache.org.
change kryo link from google code to github
Project: http://git-wip-us.apache.org/repos/asf/storm/repo
Commit: http://git-wip-us.apache.org/repos/asf/storm/commit/4a2119bd
Tree: http://git-wip-us.apache.org/repos/asf/storm/tree/4a2119bd
Diff: http://git-wip-us.apache.org/repos/asf/storm/diff/4a2119bd
Branch: refs/heads/asf-site
Commit: 4a2119bd9a00044bdee597fcc7a78a668f90ad83
Parents: 2b2de44
Author: Xin Wang <be...@163.com>
Authored: Wed Dec 2 09:25:14 2015 +0800
Committer: Xin Wang <be...@163.com>
Committed: Wed Dec 2 09:25:14 2015 +0800
----------------------------------------------------------------------
documentation/Structure-of-the-codebase.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/storm/blob/4a2119bd/documentation/Structure-of-the-codebase.md
----------------------------------------------------------------------
diff --git a/documentation/Structure-of-the-codebase.md b/documentation/Structure-of-the-codebase.md
index 5da6039..11adeeb 100644
--- a/documentation/Structure-of-the-codebase.md
+++ b/documentation/Structure-of-the-codebase.md
@@ -78,7 +78,7 @@ Here's a summary of the purpose of the main Java packages and Clojure namespace:
[backtype.storm.hooks](https://github.com/apache/storm/tree/master/storm-core/src/jvm/backtype/storm/hooks): Interfaces for hooking into various events in Storm, such as when tasks emit tuples, when tuples are acked, etc. User guide for hooks is [here](https://github.com/apache/storm/wiki/Hooks).
-[backtype.storm.serialization](https://github.com/apache/storm/tree/master/storm-core/src/jvm/backtype/storm/serialization): Implementation of how Storm serializes/deserializes tuples. Built on top of [Kryo](http://code.google.com/p/kryo/).
+[backtype.storm.serialization](https://github.com/apache/storm/tree/master/storm-core/src/jvm/backtype/storm/serialization): Implementation of how Storm serializes/deserializes tuples. Built on top of [Kryo](https://github.com/EsotericSoftware/kryo).
[backtype.storm.spout](https://github.com/apache/storm/tree/master/storm-core/src/jvm/backtype/storm/spout): Definition of spout and associated interfaces (like the `SpoutOutputCollector`). Also contains `ShellSpout` which implements the protocol for defining spouts in non-JVM languages.
@@ -139,4 +139,4 @@ Here's a summary of the purpose of the main Java packages and Clojure namespace:
[backtype.storm.util](https://github.com/apache/storm/blob/master/storm-core/src/clj/backtype/storm/util.clj): Contains generic utility functions used throughout the code base.
-[backtype.storm.zookeeper](https://github.com/apache/storm/blob/master/storm-core/src/clj/backtype/storm/zookeeper.clj): Clojure wrapper around the Zookeeper API and implements some "high-level" stuff like "mkdirs" and "delete-recursive".
\ No newline at end of file
+[backtype.storm.zookeeper](https://github.com/apache/storm/blob/master/storm-core/src/clj/backtype/storm/zookeeper.clj): Clojure wrapper around the Zookeeper API and implements some "high-level" stuff like "mkdirs" and "delete-recursive".
[3/3] storm git commit: Merge branch 'patch-9' of
github.com:vesense/storm into asf-site
Posted by kn...@apache.org.
Merge branch 'patch-9' of github.com:vesense/storm into asf-site
Project: http://git-wip-us.apache.org/repos/asf/storm/repo
Commit: http://git-wip-us.apache.org/repos/asf/storm/commit/27285ae7
Tree: http://git-wip-us.apache.org/repos/asf/storm/tree/27285ae7
Diff: http://git-wip-us.apache.org/repos/asf/storm/diff/27285ae7
Branch: refs/heads/asf-site
Commit: 27285ae7c1f35e636adc0c451e12cfa57f804b98
Parents: 01f3ec5 4a2119b
Author: Kyle Nusbaum <Ky...@gmail.com>
Authored: Thu Dec 10 22:50:31 2015 -0600
Committer: Kyle Nusbaum <Ky...@gmail.com>
Committed: Thu Dec 10 22:50:31 2015 -0600
----------------------------------------------------------------------
documentation/Serialization.md | 8 ++++----
documentation/Structure-of-the-codebase.md | 4 ++--
2 files changed, 6 insertions(+), 6 deletions(-)
----------------------------------------------------------------------