![]() ![]() The deployment API supports ordering modules according to their uses-relationship. At deployment time the engine checks the uses-dependenciesĪnd ensures that a module of that name is already deployed or will be deployed as part of the deployments. If a module file requires certain constructs that may be shared by other module files, such as named windows, tables, variables, event types, variant streams or inserted-into streams required by statements,Ī module file may specify zero to many dependent modules with the uses keyword. Serves to check uses-dependences of other modules. The module name declaration must be at the beginning of the file, comments and whitespace excluded. Use the module keyword followed a module_name identifier or a package (identifiers separated by dots) to declare the name of the module. A service provider instance keeps track of the known and/or deployed EPL modules and makes it easy to add, remove, deploy and undeploy EPL modules. It bundles EPL statements with optional deployment instructions. Note that the engine only evaluates select-clause expressions if either a listener or subscriber is attached to the statement or if used with insert-into.Īn EPL module file is a plain text file in which EPL statements appear separated by the semicolon ( ) character. INFO Statement All-Order-Events property price value 100.0Įach context partition allocation and de-allocation (only for statements that declare a context).Įach data flow source operator providing an event.Įach data flow operator processing an event.Įach data flow instance state transition.Įach expression declaration name and return value.Įach top-level expression and its return value.Įach expression including child or nested expressions and their return value.Įach pattern sub-expression and its change in truth-value.Įach pattern sub-expression and its count of active instances.Įach property name and the event's property value.Įach schedule modification and trigger received by a statement.Įach view name and its insert and remove stream. ![]() INFO Statement All-Order-Events stream OrderEvent inserted String epl = select price from OrderEvent" ĮpService.getEPAdministrator().createEPL(epl).addListener(listener) ĮpService.getEPRuntime().sendEvent(Collections.singletonMap("price", 100d), "OrderEvent") Here is a more complete example that uses the API to create the schema, create above statement and send an event:ĮpService.getEPAdministrator().createEPL("create schema OrderEvent(price double)") Category names are not case-sensitive.įor the next statement the engine produces detailed processing information (all categories) for the Order Events') select * from OrderEventįor the next statement the engine provides information about new events and also about event property values (2 categories are Order Events') select price from OrderEvent If no parameter is provided, the engine outputs information for all categories. The table below lists all available categories. You may provide a comma-separated list of category names to to output information related to specific categories only. You may define an output format for audit information via configuration. ![]() The engine reports, at INFO level, the information under log name. Use the annotation to have the engine output detailed information about statement processing. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |