Hi Tishan, I'm suggesting import stream -> temporary stream -> export stream
Regards, Damith. On Wed, Jun 8, 2016 at 12:41 PM, Tishan Dahanayakage <[email protected]> wrote: > Damith, > > Are you suggesting following flow. > Create import stream -> Create temporary stream which consumes import > stream -> Create query which consumes temporary stream? > > Thanks > /Tishan > > On Wed, Jun 8, 2016 at 12:28 PM, Damith Wickramasinghe <[email protected]> > wrote: > >> Hi Tishan, >> >> When it comes to UI level we need a clear separation of import , export >> and temporary streams. Ideally in UI we can have separate color coding to >> these three streams but once this stream component dragged and dropped we >> need to select whether its a 'import/export/temporary and CEP stream ID can >> be either import or export and Siddhi Stream ID is the temporary one. I >> think having import/export/temporary (we can decide a better name for >> temporary) is much more understandable IMO . WDYT ? >> >> Regards, >> Damith. >> >> On Wed, Jun 8, 2016 at 12:11 PM, Tishan Dahanayakage <[email protected]> >> wrote: >> >>> Hi Nayantara, >>> >>> Where can I find the scope of this project? Are we planning on >>> decomposing queries in future or not? >>> >>> Also when handling stream as you may already know there are stream >>> definitions in databridge level and also Siddhi level. Inside a execution >>> plan we map a databridge definition to Siddhi definition and vise versa. I >>> suppose that is what you are trying to do with stream name and stream >>> definition attributes in properties window. If that is the case I suggest >>> we have the parameters as 'CEP Stream ID' and 'Siddhi Stream ID' apart from >>> 'Definition' and 'import/export/temporary'. If it isn't the case please >>> explain. >>> >>> Thanks, >>> /Tishan >>> >>> On Wed, Jun 8, 2016 at 11:39 AM, Malaka Silva <[email protected]> wrote: >>> >>>> Hi Nayantara >>>> , >>>> >>>> With this GUI can we create queries on demand or should be predefined? >>>> >>>> On Wed, Jun 8, 2016 at 11:01 AM, Nayantara Jeyaraj <[email protected]> >>>> wrote: >>>> >>>>> I am currently working on the Design and Implementation of the Siddhi >>>>> Visual Editor for WSO2's CEP. The tasks completed and on-going have been >>>>> listed out below. Your input will be appreciated. >>>>> >>>>> The interface will consist of a Toolbox/palette, a canvas and a >>>>> Properties panel that appears upon clicking the toolbar icon of each >>>>> element. >>>>> >>>>> *Tasks completed:* >>>>> >>>>> - >>>>> >>>>> Functionality that enables dragging an object from the palette and >>>>> dropping it onto the canvas. >>>>> - >>>>> >>>>> Permitting the Creation of multiple connections between anchors >>>>> from varied sources and storing data in an array regarding the >>>>> connections >>>>> for further utilization. >>>>> - >>>>> >>>>> Deleting Connections along with the parent element. >>>>> >>>>> *Currently working on:* >>>>> >>>>> - >>>>> >>>>> Changing the property attributes such as stream name and stream >>>>> definition of dropped elements (Stream name will be displayed on the >>>>> respective icon when saved). >>>>> >>>>> *Eg:* >>>>> >>>>> from TempStream >>>>> >>>>> select roomNo, temp >>>>> >>>>> insert into RoomTempStream; >>>>> >>>>> >>>>> *The toolbar will hold:* >>>>> >>>>> 1. A stream icon >>>>> >>>>> 2. A query icon >>>>> >>>>> Once a stream has been dragged on to the canvas, the >>>>> type(import/export/temporary) can be selected in the properties panel and >>>>> thereafter it will be validated against the available schema and >>>>> dropped(The validation part has not been done yet). Then a query can >>>>> consume one or more event streams and generate a new event stream from >>>>> them. >>>>> >>>>> *A Tempstream will be created with the following attributes:* >>>>> >>>>> define stream TempStream(deviceID long, roomNo int, temp double); >>>>> >>>>> So when the event stream icon is dropped onto the canvas, the >>>>> properties panel for that event stream appears permitting the set up of >>>>> the >>>>> event stream. >>>>> >>>>> *Requested Stream Property Data in the properties panel:* >>>>> >>>>> Event stream type: import/ export/ temporary >>>>> >>>>> Event stream Name: <user_input> >>>>> >>>>> Event stream definition: <user_input> Derived from an existing stream >>>>> >>>>> Following this, a query can consume this stream. The query will not be >>>>> decomposed into its minuscule details but will be merely considered as one >>>>> unit. >>>>> >>>>> From the above example, the query filters out only the temperature of >>>>> the respective room from the TempStream and generates a new >>>>> RoomTempStream. >>>>> >>>>> >>>>> The Visual Representation of the above ( Relevant icons will be used): >>>>> >>>>> tempStream -----> query -----> RoomTempStream >>>>> >>>>> >>>>> Th following query types can be chosen when dealing with the query >>>>> object >>>>> >>>>> 1. Pass-through (Prioritized at present) >>>>> >>>>> 2. Filters >>>>> >>>>> 3. Window >>>>> >>>>> 4. Joins >>>>> >>>>> >>>>> Fig1: BasicUI developed to date >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Architecture mailing list >>>>> [email protected] >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> Best Regards, >>>> >>>> Malaka Silva >>>> Senior Technical Lead >>>> M: +94 777 219 791 >>>> Tel : 94 11 214 5345 >>>> Fax :94 11 2145300 >>>> Skype : malaka.sampath.silva >>>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 >>>> Blog : http://mrmalakasilva.blogspot.com/ >>>> >>>> WSO2, Inc. >>>> lean . enterprise . middleware >>>> http://www.wso2.com/ >>>> http://www.wso2.com/about/team/malaka-silva/ >>>> <http://wso2.com/about/team/malaka-silva/> >>>> https://store.wso2.com/store/ >>>> >>>> Save a tree -Conserve nature & Save the world for your future. Print >>>> this email only if it is absolutely necessary. >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> 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. >>> >> >> >> >> -- >> Software Engineer >> WSO2 Inc.; http://wso2.com >> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> >> lean.enterprise.middleware >> >> mobile: *+94728671315 <%2B94728671315>* >> >> > > > -- > 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. > -- Software Engineer WSO2 Inc.; http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> lean.enterprise.middleware mobile: *+94728671315*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
