GitHub user johanwitters opened a pull request:
https://github.com/apache/storm/pull/989
AvroGenericRecordBolt instead of SequenceFileBolt
Changing the **example code** and use **AvroGenericRecordBolt** instead of
**SequenceFileBolt**â¦
Section âSupport for Avro Filesâ starts by explained the use of
org.apache.storm.hdfs.bolt.AvroGenericRecordBolt for Avro files.
However, the example code uses SequenceFileBolt instead, and that
doesnât work, obviously because the method withSchemaAsString isnât
part of SequenceFileBolt, but part of
org.apache.storm.hdfs.bolt.AvroGenericRecordBolt instead. So, the
change is nothing but changing the name of class SequenceFileBolt and
replace it with the correct AvroGenericRecordBolt.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/johanwitters/storm master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/989.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #989
----
commit 51746991079dee7ac4ad4045eb3cfbadc78fc038
Author: johanwitters <[email protected]>
Date: 2016-01-05T16:16:04Z
AvroGenericRecordBolt instead of SequenceFileBolt
Changing the example code and use AvroGenericRecordBolt instead of
SequenceFileBoltâ¦
Section âSupport for Avro Filesâ starts by explained the use of
org.apache.storm.hdfs.bolt.AvroGenericRecordBolt for Avro files.
However, the example code uses SequenceFileBolt instead, and that
doesnât work, obviously because the method withSchemaAsString isnât
part of SequenceFileBolt, but part of
org.apache.storm.hdfs.bolt.AvroGenericRecordBolt instead. So, the
change is nothing but changing the name of class SequenceFileBolt and
replace it with the correct AvroGenericRecordBolt.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
