Hi Iranga, As per offline discussion we had CEP will have its own topology. CEP won't work with any other topology since that topology won't understand Siddhi semantics. Our topology source is at [1] which has 2 bolts and 1 spout. Topology creation is happening here [2].
[1] https://github.com/wso2/carbon-event-processing/tree/master/components/event-processor/org.wso2.carbon.event.processor.common/src/main/java/org/wso2/carbon/event/processor/common/storm/component [2] https://github.com/wso2/carbon-event-processing/blob/master/components/event-processor/org.wso2.carbon.event.processor.core/src/main/java/org/wso2/carbon/event/processor/core/internal/storm/util/StormTopologyConstructor.java Thanks, Tishan On Mon, Apr 6, 2015 at 5:36 AM, Iranga Muthuthanthri <[email protected]> wrote: > Trying out the Storm Starter example [1] ,Could the source code for the > org.wso2.carbon.event.processor.storm.jar > be shared as an example to run cep on given topologies. > > Assume the execution steps are to change the "siddhi storm jar "value in > storm-deployment-config.xml" > only. Would there be any other steps , modifications required? > > [1] https://github.com/apache/storm/tree/master/examples/storm-starter > > On Wed, Apr 1, 2015 at 8:08 PM, Tishan Dahanayakage <[email protected]> > wrote: > >> Hi Iranga, >> >> This error states that storm receiver has not yet been registered. >> However this error will be go off after cluster is fully operational. >> >> Thanks, >> Tishan >> >> On Wed, Apr 1, 2015 at 4:46 AM, Iranga Muthuthanthri <[email protected]> >> wrote: >> >>> >>> Got the sample working on the Storm local node setup(Thanks Trishan), >>> noted the following exception during the start up of the receiver node. Is >>> it expected? >>> >>> [2015-04-01 16:57:21,523] ERROR - {AsyncEventPublisher} [CEP Receiver| >>> ExecPlan:PreprocessStats, TenantID:-1234]Error while trying retrieve >>> information from storm manager service >>> >>> EndpointNotFoundException(message:No Storm Receiver for >>> executionPlanName: PreprocessStats of tenantId:-1234 for CEP Receiver >>> form:10.100.0.19) >>> >>> at >>> org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$getStormReceiver_result.read(StormManagerService.java:3025) >>> >>> at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78) >>> >>> at >>> org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.recv_getStormReceiver(StormManagerService.java:129) >>> >>> at >>> org.wso2.carbon.event.processor.common.storm.manager.service.StormManagerService$Client.getStormReceiver(StormManagerService.java:114) >>> >>> at >>> org.wso2.carbon.event.processor.common.util.AsyncEventPublisher$EndpointConnectionCreator.getEndpointFromManagerService(AsyncEventPublisher.java:187) >>> >>> at >>> org.wso2.carbon.event.processor.common.util.AsyncEventPublisher$EndpointConnectionCreator.establishConnection(AsyncEventPublisher.java:276) >>> >>> at >>> org.wso2.carbon.event.processor.common.util.AsyncEventPublisher$EndpointConnectionCreator.run(AsyncEventPublisher.java:285) >>> >>> at java.lang.Thread.run(Thread.java:745) >>> >>> >>> >>> On Wed, Mar 25, 2015 at 10:17 PM, Sriskandarajah Suhothayan < >>> [email protected]> wrote: >>> >>>> Yes we can skip storm.yaml configuration for the single node >>>> >>>> Suho >>>> >>>> On Wed, Mar 25, 2015 at 10:01 PM, Tishan Dahanayakage <[email protected]> >>>> wrote: >>>> >>>>> Hi Iranga, >>>>> Documentation [2] is outdated as of the current implementation. We >>>>> need to change that appropriately. [3] explains how to set up a Storm >>>>> Cluster. But you can ignore storm.yaml configs if you are runinng in the >>>>> localhost as in the sample. You just need to bring up storm and zoo keeper >>>>> nodes. >>>>> @Suho >>>>> I could not find any simple official documentation on running Storm on >>>>> single node. We can either create new guide or point to [3] and say that >>>>> user can skip storm.yaml configurations. WDYT? >>>>> >>>>> Thanks, >>>>> Tishan >>>>> >>>>> >>>>> On Wed, Mar 25, 2015 at 5:46 AM, Praneesha Chandrasiri < >>>>> [email protected]> wrote: >>>>> >>>>>> Hi Iranga, >>>>>> >>>>>> Thanks for pointing this out! >>>>>> >>>>>> I will work on this. >>>>>> >>>>>> On Wed, Mar 25, 2015 at 6:11 PM, Iranga Muthuthanthri < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> I am trying out CEP Sample based on [1] in local mode. In the >>>>>>> perquisite section Step 2 mentions about the storm deployment which >>>>>>> points >>>>>>> to the apache storm page. >>>>>>> >>>>>>> Would like to know if this means, it is needed to setup and run a >>>>>>> storm topology locally as mentioned in [2] by running >>>>>>> >>>>>>> org.wso2.carbon.event.processor.storm.jar , if so what would be the >>>>>>> fully qualified class name? >>>>>>> >>>>>>> Suggest that the documentation could be made more descriptive. >>>>>>> >>>>>>> [1] >>>>>>> https://docs.wso2.com/display/CEP400/Sample+2001+-+Simple+filter+query+with+Apache+Storm+deployment >>>>>>> >>>>>>> [2] >>>>>>> https://docs.wso2.com/display/CEP400/Configuring+WSO2+CEP+to+Run+with+Apache+Storm >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Thanks & Regards >>>>>>> >>>>>>> Iranga Muthuthanthri >>>>>>> (M) -0777-255773 >>>>>>> Team Product Management >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Thanks & Best Regards, >>>>>> *Praneesha Chandrasiri* >>>>>> *Technical Writer* >>>>>> *WSO2 Inc. * >>>>>> *Mobile: +(94) 718156888 <%2B%2894%29%20718156888>* >>>>>> *E-mail: [email protected] <[email protected]>* >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Tishan Dahanayakage >>>>> Software Engineer >>>>> WSO2, Inc. >>>>> Mobile:+94 716481328 >>>>> >>>>> Disclaimer: This communication may contain privileged or other >>>>> confidential information and is intended exclusively for the addressee/s. >>>>> If you are not the intended recipient/s, or believe that you may have >>>>> received this communication in error, please reply to the sender >>>>> indicating >>>>> that fact and delete the copy you received and in addition, you should not >>>>> print, copy, re-transmit, disseminate, or otherwise use the information >>>>> contained in this communication. Internet communications cannot be >>>>> guaranteed to be timely, secure, error or virus-free. The sender does not >>>>> accept liability for any errors or omissions. >>>>> >>>> >>>> >>>> >>>> -- >>>> >>>> *S. Suhothayan* >>>> Technical Lead & Team Lead of WSO2 Complex Event Processor >>>> *WSO2 Inc. *http://wso2.com >>>> * <http://wso2.com/>* >>>> lean . enterprise . middleware >>>> >>>> >>>> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog: >>>> http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter: >>>> http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in: >>>> http://lk.linkedin.com/in/suhothayan >>>> <http://lk.linkedin.com/in/suhothayan>* >>>> >>> >>> >>> >>> -- >>> Thanks & Regards >>> >>> Iranga Muthuthanthri >>> (M) -0777-255773 >>> Team Product Management >>> >>> >> >> >> -- >> Tishan Dahanayakage >> Software Engineer >> WSO2, Inc. >> Mobile:+94 716481328 >> >> Disclaimer: This communication may contain privileged or other >> confidential information and is intended exclusively for the addressee/s. >> If you are not the intended recipient/s, or believe that you may have >> received this communication in error, please reply to the sender indicating >> that fact and delete the copy you received and in addition, you should not >> print, copy, re-transmit, disseminate, or otherwise use the information >> contained in this communication. Internet communications cannot be >> guaranteed to be timely, secure, error or virus-free. The sender does not >> accept liability for any errors or omissions. >> > > > > -- > Thanks & Regards > > Iranga Muthuthanthri > (M) -0777-255773 > Team Product Management > > -- Tishan Dahanayakage Software Engineer WSO2, Inc. Mobile:+94 716481328 Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, re-transmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions.
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
