Github user dan-blanchard commented on the pull request:
https://github.com/apache/storm/pull/525#issuecomment-94003059
Ok, I tweaked things a bit more and I realized there were a couple little
issues with how I was building `sources->grouping`. As a result, I've had to
make that a bit more complex and turn it into `source->stream->grouping`,
because `GlobalStreamId` objects have both a component ID and a stream ID we
care about.
The new output looks like this for the bolt:
```python
{u'task->component':
{u'20': u'__acker',
u'21': u'__acker',
u'22': u'__acker',
u'1': u'1',
u'3': u'__acker',
u'2': u'2',
u'5': u'__acker',
u'4': u'__acker',
u'7': u'__acker',
u'6': u'__acker',
u'9': u'__acker',
u'8': u'__acker',
u'11': u'__acker',
u'10': u'__acker',
u'13': u'__acker',
u'12': u'__acker',
u'15': u'__acker',
u'14': u'__acker',
u'17': u'__acker',
u'16': u'__acker',
u'19': u'__acker',
u'18': u'__acker'},
u'stream->target->grouping': {},
u'streams': [u'default'],
u'stream->outputfields': {u'default': [u'word']},
u'taskid': 2,
u'source->stream->grouping': {u'1': {u'default': u'SHUFFLE'}},
u'componentid': u'2'}
```
Of course, there is one last strange part. Why is
`stream->target->grouping` empty for the bolt when `stream->outputfields` is
not? Is that to be expected for this test? Does the topology have a bolt that
emits but nothing consumes it?
---
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.
---
