[
https://issues.apache.org/jira/browse/STORM-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15266074#comment-15266074
]
ASF GitHub Bot commented on STORM-1701:
---------------------------------------
Github user kristopherkane commented on the pull request:
https://github.com/apache/storm/pull/1327#issuecomment-216095877
You're right. There is no sense in replaying the same broken input. I'm
conflicted on what the right approach is to notify the topology owner of
corrupt JSON or a missing row key. I don't think it is worthy of a
collector.reportError() and am wondering if it should be INFO or WARN logging.
I've got the the changes you have suggested complete minus the desired
notification. How does this go with the GitHub integration? Squash on my fork
and this PR is automatically updated?
> Add simple JSON mapping to storm-hbase
> --------------------------------------
>
> Key: STORM-1701
> URL: https://issues.apache.org/jira/browse/STORM-1701
> Project: Apache Storm
> Issue Type: Improvement
> Components: storm-hbase
> Reporter: Kristopher Kane
> Priority: Trivial
> Fix For: 2.0.0
>
>
> storm-hbase includes a way to map Storm fields to HBase CQs. This adds a
> similar ability where a single field contains a flat JSON and the keys map to
> CQs. The flat JSON must contain the row key.
> No intention of reverse mapping from HBaseLookUp as the existing HBaseMapper
> works well for this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
