You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@storm.apache.org by "Huang, Zhipeng" <Zh...@mastercard.com> on 2017/11/10 22:56:41 UTC

storm flux API - emit to specific streamId

Hi Apache Storm Team,

May I have a quick question - how to configure the streamId in yaml file,
so in Bolt we can emit the tuple to specified stream? Thanks!


Currently the StreamDef don't have "streamId" available in V1.1.1, or even on Github.

public class StreamDef {

    private String name; // not used, placeholder for GUI, etc.
    private String from;
    private String to;
private GroupingDef grouping;


Regards,
Jude
CONFIDENTIALITY NOTICE This e-mail message and any attachments are only for the use of the intended recipient and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient, any disclosure, distribution or other use of this e-mail message or attachments is prohibited. If you have received this e-mail message in error, please delete and notify the sender immediately. Thank you.

RE: storm flux API - emit to specific streamId

Posted by "Huang, Zhipeng" <Zh...@mastercard.com>.

Thank you Priyank, appreciate it!

From: Priyank Shah [mailto:pshah@hortonworks.com]
Sent: Friday, November 10, 2017 5:53 PM
To: user@storm.apache.org
Subject: Re: storm flux API - emit to specific streamId

You can provide it under grouping. Check GroupingDef. Pasting an example below.

streams:
  - name: "kafka --> split" # name isn't used (placeholder for logging, UI, etc.)
    from: "kafka-spout"
    to: "splitsentence"
    grouping:
      type: SHUFFLE
      streamId: “mystream”

From: "Huang, Zhipeng" <Zh...@mastercard.com>>
Reply-To: "user@storm.apache.org<ma...@storm.apache.org>" <us...@storm.apache.org>>
Date: Friday, November 10, 2017 at 2:56 PM
To: "user@storm.apache.org<ma...@storm.apache.org>" <us...@storm.apache.org>>
Subject: storm flux API - emit to specific streamId

Hi Apache Storm Team,

May I have a quick question – how to configure the streamId in yaml file,
so in Bolt we can emit the tuple to specified stream? Thanks!

Currently the StreamDef don’t have “streamId” available in V1.1.1, or even on Github.

public class StreamDef {

    private String name; // not used, placeholder for GUI, etc.
    private String from;
    private String to;
private GroupingDef grouping;

Regards,
Jude
CONFIDENTIALITY NOTICE This e-mail message and any attachments are only for the use of the intended recipient and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient, any disclosure, distribution or other use of this e-mail message or attachments is prohibited. If you have received this e-mail message in error, please delete and notify the sender immediately. Thank you.

Re: storm flux API - emit to specific streamId

Posted by Priyank Shah <ps...@hortonworks.com>.

You can provide it under grouping. Check GroupingDef. Pasting an example below.

streams:
  - name: "kafka --> split" # name isn't used (placeholder for logging, UI, etc.)
    from: "kafka-spout"
    to: "splitsentence"
    grouping:
      type: SHUFFLE
      streamId: “mystream”


From: "Huang, Zhipeng" <Zh...@mastercard.com>
Reply-To: "user@storm.apache.org" <us...@storm.apache.org>
Date: Friday, November 10, 2017 at 2:56 PM
To: "user@storm.apache.org" <us...@storm.apache.org>
Subject: storm flux API - emit to specific streamId

Hi Apache Storm Team,

May I have a quick question – how to configure the streamId in yaml file,
so in Bolt we can emit the tuple to specified stream? Thanks!


Currently the StreamDef don’t have “streamId” available in V1.1.1, or even on Github.

public class StreamDef {

    private String name; // not used, placeholder for GUI, etc.
    private String from;
    private String to;
private GroupingDef grouping;


Regards,
Jude
CONFIDENTIALITY NOTICE This e-mail message and any attachments are only for the use of the intended recipient and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient, any disclosure, distribution or other use of this e-mail message or attachments is prohibited. If you have received this e-mail message in error, please delete and notify the sender immediately. Thank you.